summaryrefslogtreecommitdiffstats
path: root/2023/talks
diff options
context:
space:
mode:
Diffstat (limited to '2023/talks')
-rw-r--r--2023/talks/emacsconf.md25
-rw-r--r--2023/talks/hyperdrive.md72
-rw-r--r--2023/talks/nabokov.md42
3 files changed, 139 insertions, 0 deletions
diff --git a/2023/talks/emacsconf.md b/2023/talks/emacsconf.md
new file mode 100644
index 00000000..c08bbe01
--- /dev/null
+++ b/2023/talks/emacsconf.md
@@ -0,0 +1,25 @@
+[[!meta title="EmacsConf.org: How we use Org Mode and TRAMP to organize and run a multi-track conference"]]
+[[!meta copyright="Copyright © 2023 Sacha Chua"]]
+[[!inline pages="internal(2023/info/emacsconf-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# EmacsConf.org: How we use Org Mode and TRAMP to organize and run a multi-track conference
+Sacha Chua (she/her) - IRC: sachac, <https://sachachua.com>, Mastodon: @sachac@emacs.ch, <mailto:sacha@sachachua.com>
+
+[[!inline pages="internal(2023/info/emacsconf-before)" raw="yes"]]
+
+Go on a whirlwind tour behind the scenes to see how we've been using
+large Org Mode files and a bunch of Emacs Lisp functions to organize
+and run EmacsConf. You might be able to pick up some ideas about Org
+Mode navigation, image and video manipulation, captioning, publishing,
+and remote command execution, and then check out the notes to find out
+more.
+
+[[!inline pages="internal(2023/info/emacsconf-after)" raw="yes"]]
+
+[[!inline pages="internal(2023/info/emacsconf-nav)" raw="yes"]]
+
+
diff --git a/2023/talks/hyperdrive.md b/2023/talks/hyperdrive.md
new file mode 100644
index 00000000..1a092fa4
--- /dev/null
+++ b/2023/talks/hyperdrive.md
@@ -0,0 +1,72 @@
+[[!meta title="hyperdrive.el: Peer-to-peer filesystem in Emacs"]]
+[[!meta copyright="Copyright &copy; 2023 ${speakers}"]]
+[[!inline pages="internal(2023/info/hyperdrive-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# hyperdrive.el: Peer-to-peer filesystem in Emacs
+Joseph Turner, <https://ushin.org> xmpp:discuss@conference.ushin.org (XMPP MUC for USHIN discussion), <mailto:joseph@ushin.org>
+
+[[!inline pages="internal(2023/info/hyperdrive-before)" raw="yes"]]
+
+This talk explores [hyperdrive.el](https://ushin.org/hyperdrive/hyperdrive-manual.html), an Emacs interface to [hyperdrive](https://docs.holepunch.to/building-blocks/hyperdrive), a
+peer-to-peer shared filesystem.
+
+Peer-to-peer networks give you the freedom to choose your sources of
+information and to communicate directly with them. Emacs is a
+[freedom-respecting](https://www.gnu.org/philosophy/free-software-even-more-important.html) text editor/operating system that puts you in the
+driver's seat. By bringing these two worlds together, hyperdrive.el
+aims to inspire deliberation about digital communication freedom.
+
+Hyperdrives are peer-to-peer shared folders, well-suited for data that
+changes over time, like personal blogs. It complements Bittorrent and
+IPFS, which work best with unchanging data, like journal archives.
+
+Here's a scenario: Alice creates a new hyperdrive and adds some files.
+Her computer returns a public key URL that uniquely identifies the
+hyperdrive. Alice shares that URL with Bob, who can then download
+Alice's files directly from her computer. No third-party servers are
+required to route the connection.
+
+Data is distributed among peers; once Bob has loaded Alice's files,
+Carol can get them from Bob (or anyone else who has a copy) even when
+Alice is offline. Drives are mutable; when Alice adds/removes/changes
+files in the drive, Bob can refresh her drive on his machine to get
+the latest changes. Drives are versioned; anyone with the URL can
+"check out" prior versions of Alice's drive to see what her files used
+to look like.
+
+Currently supported features in hyperdrive.el include:
+
+- [directly edit hyperdrive files](https://ushin.org/hyperdrive/hyperdrive-manual.html#Write-to-a-hyperdrive)
+- [dired-like directory view](https://ushin.org/hyperdrive/hyperdrive-manual.html#Directory-view)
+- [org-mode link support](https://ushin.org/hyperdrive/hyperdrive-manual.html#Org-mode-links)
+- [version history navigation/diffing](https://ushin.org/hyperdrive/hyperdrive-manual.html#View-the-hyperdrive-version-history)
+- [built-in bookmark.el integration](https://ushin.org/hyperdrive/hyperdrive-manual.html#Bookmark-a-hyperdrive)
+- [local directory mirroring](https://ushin.org/hyperdrive/hyperdrive-manual.html#Mirror-a-whole-directory)
+- [audio/video streaming](https://ushin.org/hyperdrive/hyperdrive-manual.html#Stream-audio-and-video)
+
+Planned features include:
+
+- peer discovery (swarming)
+- diffing directories between versions
+
+Check out [the manual](https://ushin.org/hyperdrive/hyperdrive-manual.html#Installation) for installation instructions!
+
+You're welcome to join our public XMPP chat room!
+
+- xmpp:discuss@conference.ushin.org ([Join anonymously from your browser](https://anonymous.cheogram.com/discuss@conference.ushin.org))
+- \#\_bifrost\_discuss\_conference.ushin.org:aria-net.org (Matrix bridge)
+
+Bugs can be submitted to the [ushin issue tracker](https://todo.sr.ht/~ushin/ushin). Patches, comments or
+questions can be submitted to the [ushin public inbox](https://lists.sr.ht/~ushin/ushin).
+
+
+
+[[!inline pages="internal(2023/info/hyperdrive-after)" raw="yes"]]
+
+[[!inline pages="internal(2023/info/hyperdrive-nav)" raw="yes"]]
+
+
diff --git a/2023/talks/nabokov.md b/2023/talks/nabokov.md
new file mode 100644
index 00000000..1832fd3d
--- /dev/null
+++ b/2023/talks/nabokov.md
@@ -0,0 +1,42 @@
+[[!meta title="Why Nabokov would use Org-Mode if he were writing today"]]
+[[!meta copyright="Copyright &copy; 2023 Edmund Jorgensen"]]
+[[!inline pages="internal(2023/info/nabokov-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# Why Nabokov would use Org-Mode if he were writing today
+Edmund Jorgensen (he/him) - <https://tomheon.com>, <mailto:ewj@inkwellandoften.com>
+
+[[!inline pages="internal(2023/info/nabokov-before)" raw="yes"]]
+
+I've written several novels in Emacs. One of them grew into a monster with a
+baker's dozen twisty, interconnected subplots.
+
+When I started to revise that novel, I had to use an outline to keep all the
+subplots straight, but I found it nearly impossible to keep that external
+outline consistent with the prose.
+
+Finally I landed on a workflow using org-mode to keep the outline and the
+prose together, which significantly reduced the burden of keeping the two
+consistent as I moved and modified sections. I also found a way to use tags
+and sparse views over them to enable quick read-throughs of subsets of the
+book for continuity checks (which I plan to demo).
+
+Later--long after finishing the book--I realized this process was essentially
+the Emacs update to the writing process that Nabokov used: he wrote on index
+cards that served as both prose and outline, so that he could move them around
+(which he did incessantly).
+
+There's something deeply beautiful about org-mode's refusal to treat structure
+and prose as different things in a piece of writing--something I think Nabokov
+would have appreciated, and something I definitely appreciate, because it
+saved my novel.
+
+
+[[!inline pages="internal(2023/info/nabokov-after)" raw="yes"]]
+
+[[!inline pages="internal(2023/info/nabokov-nav)" raw="yes"]]
+
+