+00:00:00.060 --> 00:00:01.400 [Speaker 0]: All right, I've started the recording,
+00:00:01.400 --> 00:00:03.240 so Sasha, you don't need to worry about this.
+00:00:03.240 --> 00:00:04.500 Hi Jeremy, how are you doing?
+00:00:04.779 --> 00:00:07.160 [Speaker 1]: I'm doing great, how about you?
+00:00:08.039 --> 00:00:09.380 [Speaker 0]: I am also doing great,
+00:00:09.380 --> 00:00:11.780 I am feeling replenished after this lunch
+00:00:11.780 --> 00:00:14.179 break and I am happy to go back for 4 more
+00:00:15.900 --> 00:00:16.940 [Speaker 1]: Me too. Let me
+00:00:14.179 --> 00:00:17.303 [Speaker 0]: hours of conferences. just,
+00:00:17.303 --> 00:00:20.200 yeah great, Let me just put up the questions.
+00:00:20.660 --> 00:00:22.440 So Jeremy is going to read the questions and
+00:00:22.440 --> 00:00:24.380 answer them and I will be doing jazz hands in
+00:00:24.380 --> 00:00:26.599 the background or provide any bits of
+00:00:26.599 --> 00:00:28.860 information I may, considering that Orgrim
+00:00:28.860 --> 00:00:30.080 has been mentioned during the presentation
+00:00:30.080 --> 00:00:31.980 and everyone's going to want to ask me.
+00:00:35.640 --> 00:00:37.940 at... Show me? Yeah, go.
+00:00:35.080 --> 00:00:39.280 [Speaker 1]: So I'm looking I'm looking at the,
+00:00:39.280 --> 00:00:41.160 do you think the line numbers for writing
+00:00:41.160 --> 00:00:43.220 documents is kind of a distraction,
+00:00:43.260 --> 00:00:47.280 especially for notes? No,
+00:00:47.860 --> 00:00:50.300 I do software development and that left
+00:00:51.180 --> 00:00:53.160 fringe is kind of invisible,
+00:00:53.680 --> 00:00:56.260 but I do like to use jump to line.
+00:00:56.320 --> 00:00:59.580 So I just bind that to control L and it's
+00:00:59.580 --> 00:01:01.200 helpful to just see that.
+00:01:02.980 --> 00:01:04.900 So no, I haven't noticed that.
+00:01:05.500 --> 00:01:07.540 There are other ways to jump around in Emacs,
+00:01:07.540 --> 00:01:10.140 but I like to have many different ways.
+00:01:11.000 --> 00:01:17.120 So, yeah. Then how do you manage private and
+00:01:17.120 --> 00:01:18.840 public data with your Zettelkasten?
+00:01:20.820 --> 00:01:23.440 1 of my blockers on putting my Zettelkasten
+00:01:23.600 --> 00:01:26.240 on the web is I don't want everything to be
+00:01:26.240 --> 00:01:28.860 public, especially fleeting notes.
+00:01:31.360 --> 00:01:36.500 So 1 thing is I only explicitly export a file
+00:01:36.560 --> 00:01:39.380 to Hugo and I have that,
+00:01:39.380 --> 00:01:41.500 I can like, I can export this.
+00:01:41.520 --> 00:01:43.380 That doesn't show up very well.
+00:01:44.540 --> 00:01:50.280 So it's export probably export org to take on
+00:01:50.280 --> 00:01:52.860 rules and we'll export the buffer.
+00:01:53.760 --> 00:01:57.040 And then any that I referenced,
+00:01:57.080 --> 00:01:58.300 like these are all links,
+00:01:58.660 --> 00:02:04.380 any notes that are not public will be
+00:02:04.380 --> 00:02:06.480 exported as the text, but there won't be a
+00:02:06.480 --> 00:02:10.160 link to it. So it's having the very
+00:02:10.160 --> 00:02:12.140 deliberate, this is going up.
+00:02:13.040 --> 00:02:15.080 And so I send it over into Hugo,
+00:02:15.900 --> 00:02:17.200 which is its own repository,
+00:02:18.700 --> 00:02:21.300 and either massage it there or whatnot.
+00:02:22.800 --> 00:02:25.760 Is that any further questions on that 1?
+00:02:27.980 --> 00:02:30.200 [Speaker 0]: I don't think so.
+00:02:33.940 --> 00:02:36.940 [Speaker 1]: Is there anything special you're using from
+00:02:36.940 --> 00:02:38.960 org to Hugo markdown? This looks like a
+00:02:38.960 --> 00:02:41.520 really nice setup. I like to give it a try.
+00:02:43.840 --> 00:02:47.420 Yes, there I have a bespoke build process.
+00:02:48.900 --> 00:02:50.100 Having started in WordPress,
+00:02:50.280 --> 00:02:51.320 working through Jekyll,
+00:02:51.460 --> 00:02:54.200 going to Hugo, and then switching from
+00:02:54.200 --> 00:02:57.740 Markdown to org mode, I've backed into this
+00:02:57.740 --> 00:02:59.180 private public Zettelkasten,
+00:03:00.140 --> 00:03:04.840 which is really nice. And I have added quite
+00:03:04.840 --> 00:03:08.000 a bit of code. There's my dog.
[Speaker 0]: blogging.
+00:03:10.640 --> 00:03:20.720 [Speaker 1]: In my So I have, how do I export like side
+00:03:20.720 --> 00:03:22.800 notes because I want I have marginalia
+00:03:23.200 --> 00:03:24.780 instead of like the footnotes,
+00:03:24.940 --> 00:03:27.080 but I still use org mode footnotes.
+00:03:27.520 --> 00:03:29.700 And so I've got a bunch of these things and
+00:03:29.700 --> 00:03:32.800 this is all available up on GitHub And I'll
+00:03:32.800 --> 00:03:34.700 provide a link in the document.
+00:03:36.740 --> 00:03:42.280 Yeah, so there's quite a bit of making the
+00:03:42.280 --> 00:03:44.440 export work how I want it.
+00:03:45.040 --> 00:03:48.840 And I've been kind of fiddling with also
+00:03:48.840 --> 00:03:51.560 improving like LaTeX or PDF export.
+00:03:54.720 --> 00:03:59.080 So yeah, I have a long running to do item to
+00:03:59.480 --> 00:04:02.880 fully lay out my bespoke build process.
+00:04:02.920 --> 00:04:04.680 Because once it gets to Hugo,
+00:04:04.960 --> 00:04:07.440 there's also additional work that I do to
+00:04:07.440 --> 00:04:11.820 compile what is kind of a personal,
+00:04:12.340 --> 00:04:13.620 like a digital garden-ish,
+00:04:15.160 --> 00:04:16.940 it's really a blog focused 1.
+00:04:18.160 --> 00:04:28.080 So yeah, it's at Jeremy F on GitHub at dot
+00:04:28.080 --> 00:04:33.060 Emacs. And you'll be looking for JF
+00:04:33.200 --> 00:04:36.300 blogging.l that has some of this.
+00:04:37.360 --> 00:04:42.580 Also jforgmode.l will have some of that.
+00:04:45.400 --> 00:04:49.540 Yeah, I wanna circle back to that,
+00:04:49.540 --> 00:04:51.560 anything to prevent private links from
+00:04:51.560 --> 00:04:54.220 getting accidentally being made publicly
+00:04:54.560 --> 00:05:02.440 accessible. Yes. So previous to using denote,
+00:05:02.440 --> 00:05:06.480 I also used org-roam. So I have this idea of
+00:05:06.480 --> 00:05:12.560 a node in org-roam has roam refs.
+00:05:13.360 --> 00:05:15.660 And org-roam is much more robust about that.
+00:05:15.660 --> 00:05:17.880 So anytime you mention a ref,
+00:05:18.740 --> 00:05:20.300 it will count it as a backlink.
+00:05:20.820 --> 00:05:23.700 So for example, if my node was my blog,
+00:05:23.860 --> 00:05:25.700 take on rules, anytime,
+00:05:26.000 --> 00:05:30.420 anywhere in my org Rome repository,
+00:05:30.700 --> 00:05:32.120 I mentioned takeonrules.com,
+00:05:33.280 --> 00:05:34.980 it would treat it as a backlink.
+00:05:35.740 --> 00:05:37.980 So from that Rome refs,
+00:05:39.780 --> 00:05:45.640 I have a, I will interrogate,
+00:05:45.720 --> 00:05:47.800 and this is not the function for I will look
+00:05:47.800 --> 00:05:50.940 at the node to see does it have a Rome ref
+00:05:51.040 --> 00:05:53.760 and if it does I will treat it as a public
+00:05:53.760 --> 00:05:58.180 link. So I don't I haven't bled out any
+00:05:59.060 --> 00:06:01.620 private information because again going back
+00:06:01.620 --> 00:06:06.000 to I only publish a document and the document
+00:06:06.340 --> 00:06:09.060 I'm explicitly doing so and then my process
+00:06:09.220 --> 00:06:12.720 filters out any links that do not have public
+00:06:12.720 --> 00:06:17.140 URLs. It will just dump it in there as maybe
+00:06:17.140 --> 00:06:20.640 a span with a ref class of it so that I can
+00:06:20.640 --> 00:06:22.840 kind of know that that came from there.
+00:06:29.600 --> 00:06:33.740 Yes, So the font I am using is,
+00:06:36.820 --> 00:06:38.460 so this is another font.
+00:06:38.620 --> 00:06:41.140 What font were you using in EWW?
+00:06:42.940 --> 00:06:50.420 I think I'm using IOS Becca and ET Bembo.
+00:06:51.700 --> 00:06:53.180 [Speaker 0]: Okay, show me your EWW.
+00:06:53.560 --> 00:06:55.360 If we are doing full ricing setup,
+00:06:55.440 --> 00:06:58.440 I can recognize Yosefka just by looking at
it.
+00:06:50.640 --> 00:07:01.300 [Speaker 1]: So let's... Yeah, so yeah,
+00:07:01.300 --> 00:07:06.240 ET Bembo, I'm using these 2 fonts as kind of
+00:07:06.240 --> 00:07:09.260 my anchor. So the variable pitch is ETBembo.
+00:07:10.240 --> 00:07:13.640 My blog started off with a Tufta style CSS
+00:07:14.100 --> 00:07:16.360 and I really pared it down and got rid of any
+00:07:16.360 --> 00:07:19.940 of the additional fonts because they can be
+00:07:19.940 --> 00:07:21.580 used as trackers. And I'm like,
+00:07:21.580 --> 00:07:24.020 nope, you decide what font you want for your
+00:07:24.020 --> 00:07:26.420 browser. I don't need to tell you what looks
+00:07:26.420 --> 00:07:33.680 good for you. Yeah, so the story of Take On
+00:07:33.680 --> 00:07:37.480 Rules, I have to thank my partner and lovely
+00:07:37.480 --> 00:07:41.180 wife for that. She kind of nudged me to do
+00:07:41.180 --> 00:07:43.080 some blogging, and we spent some time
+00:07:43.080 --> 00:07:45.160 thinking about it. And originally,
+00:07:45.160 --> 00:07:48.220 it started off as writing about rules for
+00:07:48.700 --> 00:07:51.060 role-playing games or tabletop games.
+00:07:51.820 --> 00:07:54.860 And it has extended far beyond that.
+00:07:54.960 --> 00:07:56.760 The blog, as I've shifted,
+00:07:56.920 --> 00:07:58.660 as I think I mentioned in the presentation,
+00:07:59.060 --> 00:08:01.640 as I've shifted towards an everything and
+00:08:01.640 --> 00:08:05.180 nothing approach, the blog is anything I want
+00:08:05.180 --> 00:08:06.240 to write about anymore.
+00:08:06.980 --> 00:08:09.440 There's haikus up there with some regularity.
+00:08:10.080 --> 00:08:17.280 So the name is now a relic of a past.
+00:08:18.340 --> 00:08:21.680 So yeah, the thing and nothing is,
+00:08:22.360 --> 00:08:24.640 and I put that in the about on my blog.
+00:08:25.640 --> 00:08:29.440 So it's, I highly encourage like,
+00:08:29.440 --> 00:08:34.440 I feel great. Once I like said,
+00:08:34.440 --> 00:08:36.740 oh, I don't have to write this towards a
+00:08:36.740 --> 00:08:40.100 topical blog post or like what the topic is,
+00:08:40.380 --> 00:08:44.120 it freed it up. And I know that it comes at a
+00:08:44.800 --> 00:08:47.500 potential compromise because it's very much
+00:08:47.500 --> 00:08:51.960 me being a voice up there instead of
+00:08:51.960 --> 00:08:53.760 something that is curated and filtered
+00:08:53.760 --> 00:08:56.060 through a specific channel like I could have
+00:08:56.060 --> 00:08:59.340 a technical blog but I decided I'm just gonna
+00:08:59.340 --> 00:09:02.420 tag it as programming or emacs and let you
+00:09:02.420 --> 00:09:04.840 find it and you can subscribe to the rss
+00:09:04.920 --> 00:09:07.360 feeds of each tag that you find applicable
+00:09:10.120 --> 00:09:13.840 [Speaker 0]: right thank you so we are we are at the last
+00:09:13.840 --> 00:09:16.100 question on the pad but I see that some
+00:09:16.100 --> 00:09:18.480 people have joined us on the blue button.
+00:09:18.480 --> 00:09:22.420 So, hi everyone! We have about 6 minutes
+00:09:22.420 --> 00:09:24.220 until we need to go to the next talk,
+00:09:24.220 --> 00:09:26.460 but if anyone has a question on the blue
+00:09:26.460 --> 00:09:28.780 button, I'm thinking about James who's joined
+00:09:28.780 --> 00:09:32.780 us and who was kind enough to drop a thank
+00:09:32.780 --> 00:09:33.940 you line on the blue button.
+00:09:33.940 --> 00:09:35.460 Do you want to unmute yourself and ask a
+00:09:35.460 --> 00:09:39.520 question maybe? I'm not putting pressure by
+00:09:39.520 --> 00:09:41.680 the way, I don't feel like you need to but it
+00:09:41.870 --> 00:09:44.060 just... I speak all the time otherwise I'm
+00:09:44.060 --> 00:09:45.720 very happy to spend time with our speakers
+00:09:45.720 --> 00:09:48.700 you know but you know EmacsConf it's about,
+00:09:49.400 --> 00:09:51.300 as Sasha told you during the intro,
+00:09:51.540 --> 00:09:54.180 it's about making people take things,
+00:09:54.240 --> 00:09:56.100 brilliant things out of their mind and put
+00:09:56.100 --> 00:09:57.840 them outside in the public.
+00:09:57.940 --> 00:10:00.660 And for us, you know, we get to see the talk
+00:10:00.660 --> 00:10:01.720 evolve, we talk with people.
+00:10:01.720 --> 00:10:03.840 So for us we are already quite cognizant of
+00:10:03.840 --> 00:10:06.260 the topic and the point is not for us hosts
+00:10:06.360 --> 00:10:09.780 to ask questions, it's mostly for you to ask
+00:10:09.780 --> 00:10:11.580 questions and then we worry about all the
+00:10:11.580 --> 00:10:12.940 fancy stuff in the background.
+00:10:13.900 --> 00:10:16.080 Otherwise you damn well know I will ask
+00:10:16.080 --> 00:10:18.660 questions about org-roam,
+00:10:18.900 --> 00:10:20.460 about links, and nodes in general,
+00:10:20.460 --> 00:10:22.100 because that's my bread and butter.
+00:10:24.720 --> 00:10:27.440 [Speaker 1]: Yeah, I should add, like,
+00:10:27.440 --> 00:10:31.820 the process of migrating the data from a
+00:10:31.820 --> 00:10:35.220 WordPress export to markdown to org mode by
+00:10:35.220 --> 00:10:39.680 way of Pandoc was, it was really insightful
+00:10:39.720 --> 00:10:42.900 to help me understand how I want the data to
+00:10:42.900 --> 00:10:47.580 flow and how I could create a repository for
+00:10:47.580 --> 00:10:50.940 me of information and 1 that I could then
+00:10:50.940 --> 00:10:52.540 send out into the world,
+00:10:52.540 --> 00:10:53.600 the public information,
+00:10:54.240 --> 00:10:58.160 while not having to worry about the private
+00:10:58.460 --> 00:11:00.280 things that I might want to keep.
+00:11:01.620 --> 00:11:04.240 So it was that process of just working
+00:11:04.240 --> 00:11:08.940 through it to reflect on how I'm writing and
+00:11:08.940 --> 00:11:11.360 what I started using writing for.
+00:11:12.040 --> 00:11:14.040 I think Richard Feynman said,
+00:11:14.040 --> 00:11:15.680 no, writing is my thinking.
+00:11:15.680 --> 00:11:17.740 What I wrote is thinking.
+00:11:18.240 --> 00:11:21.480 So it has helped to really frame that.
+00:11:22.800 --> 00:11:24.440 [Speaker 0]: Yeah, I mean, there's an interesting
+00:11:27.200 --> 00:11:29.220 ambivalent relationship because it feels like
+00:11:29.220 --> 00:11:31.800 writing helps thinking and thinking helps
+00:11:31.800 --> 00:11:35.340 writing in a way and nowhere have I
+00:11:35.340 --> 00:11:37.920 personally been more aware of this than when
+00:11:38.000 --> 00:11:41.000 coming up with networks of notes because it
+00:11:41.000 --> 00:11:43.860 really I mean you use whichever word you want
+00:11:43.860 --> 00:11:45.900 you know a second brain a collection of notes
+00:11:45.900 --> 00:11:48.860 a slip box a repository of notes whichever
+00:11:48.860 --> 00:11:52.080 the tool you use the point at the end is to
+00:11:52.080 --> 00:11:54.000 resonate with you. It's kind of like
+00:11:54.000 --> 00:11:57.280 extending those moments of consciousness that
+00:11:57.280 --> 00:11:58.880 you have when you take your notes,
+00:11:59.440 --> 00:12:02.780 and you make the entire gradient available.
+00:12:04.260 --> 00:12:06.380 Sorry, I heard Sasha whispering in my ear
+00:12:06.380 --> 00:12:08.360 sometimes. It's pretty pleasant.
+00:12:09.520 --> 00:12:10.500 It's really shocking.
+00:12:12.660 --> 00:12:15.040 [Speaker 1]: Yeah, Aaron, you had a question.
+00:12:15.040 --> 00:12:17.440 Do I use denote just for my blogs or do I use
+00:12:17.440 --> 00:12:18.660 it for other purposes?
+00:12:19.940 --> 00:12:25.120 I use denote for all of my note taking and
+00:12:25.520 --> 00:12:28.660 almost, I think it's exclusively org mode
+00:12:28.920 --> 00:12:30.560 that I, that I use it in.
+00:12:30.600 --> 00:12:33.400 But what I really appreciated in the
+00:12:33.400 --> 00:12:37.500 consideration that Proc put forward was the
+00:12:37.500 --> 00:12:40.940 file name encodes the information that's
+00:12:40.940 --> 00:12:45.980 relevant. So it has helped me be able to
+00:12:46.080 --> 00:12:48.580 query by using things like ripgrep,
+00:12:49.220 --> 00:12:54.480 well not ripgrep, tree or I forget any more
+00:12:54.480 --> 00:13:00.140 what I use. But having that the file encodes
+00:13:00.300 --> 00:13:03.820 useful information. And it's so much more
+00:13:03.820 --> 00:13:06.960 relevant when I look at having worked at a
+00:13:06.960 --> 00:13:10.520 university that rolled out Google Drive to
+00:13:10.520 --> 00:13:12.840 everyone without any guidance on how to
+00:13:12.840 --> 00:13:16.120 organize stuff. And I worked at a library and
+00:13:16.120 --> 00:13:19.540 it was just a nightmare watching things show
+00:13:19.540 --> 00:13:22.840 up where you could never find it again.
+00:13:23.240 --> 00:13:28.060 So, file name, the file name having the date,
+00:13:28.380 --> 00:13:33.280 having the title and having tags just made so
+00:13:33.280 --> 00:13:34.780 much sense to be findable.
+00:13:36.820 --> 00:13:41.420 And yeah, I really do just use org.
+00:13:41.740 --> 00:13:47.220 But if I am going to make txt files or other
+00:13:47.220 --> 00:13:52.040 files, I have started adopting that structure
+00:13:52.120 --> 00:13:52.840 and format.
+00:13:56.840 --> 00:14:00.900 [Speaker 0]: Right. Well, Jeremy, we have about 1 minute
+00:14:00.900 --> 00:14:03.080 and 30 seconds left until we go on to the
+00:14:03.080 --> 00:14:05.140 next talk. Do you have any final words
+00:14:05.140 --> 00:14:06.740 regarding your presentation or maybe where
+00:14:06.740 --> 00:14:08.400 people can find you? I know you've already
+00:14:08.400 --> 00:14:09.240 mentioned this but...
+00:14:09.240 --> 00:14:13.160 [Speaker 1]: Yeah, take on rules. I'm also on dice camp
+00:14:13.440 --> 00:14:18.080 dice.campmastodon at take on rules and I've
+00:14:18.080 --> 00:14:22.080 thought about emacs.h but we federate well So
+00:14:22.340 --> 00:14:27.560 I appreciate that. And I can stay on and
+00:14:27.560 --> 00:14:29.680 answer any further questions if folks have
it.
+00:14:31.420 --> 00:14:34.860 [Speaker 0]: Sure. So sorry. Sorry,
+00:14:34.860 --> 00:14:36.820 I confused myself with the buttons talking to
+00:14:36.820 --> 00:14:38.960 production and all. Well then,
+00:14:38.960 --> 00:14:41.260 what I'm going to do is that the stream is
+00:14:41.260 --> 00:14:43.740 going to move on to the next talk in about 50
+00:14:43.740 --> 00:14:46.160 seconds. If people want to join and ask any
+00:14:46.160 --> 00:14:49.160 questions, feel free to join on the blue
+00:14:49.160 --> 00:14:51.380 button. The link is on the talk page or on
+00:14:51.380 --> 00:14:54.480 IRC. And feel free to hang out as long as you
+00:14:54.480 --> 00:14:56.160 want to ask as many questions as you want to
+00:14:56.160 --> 00:14:58.180 Jeremy. We are recording all of this and
+00:14:58.180 --> 00:15:00.540 we'll be publishing this later on once again.
+00:15:01.120 --> 00:15:03.080 And all that's left for me to do is to thank
+00:15:03.080 --> 00:15:05.580 you so much, Jeremy, for your presentation
+00:15:05.740 --> 00:15:08.200 and your answers. And I will see you another
time.
+00:15:12.700 --> 00:15:14.840 [Speaker 1]: So yeah, plasma strike.
+00:15:15.560 --> 00:15:18.500 I'm not able to grant speaking powers.
+00:15:20.340 --> 00:15:22.160 So if you wanted to type up something
question-wise.
+00:15:24.000 --> 00:15:26.000 [Speaker 0]: Oh, okay. I'll manage this in the background.
+00:15:26.000 --> 00:15:28.220 So we're moving on to the next talk.
+00:15:28.500 --> 00:15:30.240 We'll figure out the things about VBB,
+00:15:30.240 --> 00:15:32.940 But in the meantime, enjoy the next talk.
+00:15:34.140 --> 00:15:35.460 Bye. All right, Jeremy.
+00:15:35.460 --> 00:15:37.080 We are now on the next talk.
+00:15:37.080 --> 00:15:39.240 Sorry about having to mention multiple things
+00:15:39.240 --> 00:15:42.500 at the same time. Speaking rights.
+00:15:42.500 --> 00:15:44.440 I will try fixing this in the background.
+00:15:44.440 --> 00:15:46.120 I need to get moving for the next talk,
+00:15:46.120 --> 00:15:48.040 but I'll do it in the background and we'll
+00:15:48.040 --> 00:15:49.660 let you know as soon as it's ready.
+00:15:40.440 --> 00:15:50.360 [Speaker 1]: We're doing great. Okay.
+00:15:51.220 --> 00:15:52.320 [Speaker 0]: Alright, bye bye Jeremy. -- cgit v1.2.3