add IRC

1 files changed, 25 insertions, 8 deletions

diff --git a/2024/talks/hyperdrive.md b/2024/talks/hyperdrive.md
index eb233094..d016c6ad 100644
--- a/2024/talks/hyperdrive.md
+++ b/2024/talks/hyperdrive.md
@@ -62,7 +62,7 @@ See also: [EmacsConf - 2023 - talks - hyperdrive.el: Peer-to-peer filesystem in
     -   [https://hypha.coop](https://hypha.coop) -
         hyper://zdouwaei9kc5zbk93w5dakbr8maayupojthf3eafo16s4d5pbsry/
 -   Q:One usecase for this is sharing and building upon second
-    brains/zettelkastens\"denote or org-roam\" but a blocker from me
+    brains/zettelkastens"denote or org-roam" but a blocker from me
     wanting to make one public is wanting to use a blocklist or
     whitelist so I can make them containing useful information for only
     my while also being useful with in a public sense
@@ -77,14 +77,14 @@ See also: [EmacsConf - 2023 - talks - hyperdrive.el: Peer-to-peer filesystem in
             formulated as a function
         -   E.g., with Karl Voit's filetags (or Prot's Denote
             filenaming scheme), you could share only those files which
-            are tagged as \"public\".
+            are tagged as "public".
 -   Q: idea: try hyperdrive to distribute WORG (and EmacsWiki)
     -   A: Great idea!
--   Q: Could you comment on the \"visualization\" thing, (org
+-   Q: Could you comment on the "visualization" thing, (org
     visualization), and your experience with this type of content in
     buffers and the various possibilities (svg, etc.)?
     -   A:  We submited a patch which was merged in Emacs 30 to make
-        image maps (the \"overlay\" which makes images clickable and
+        image maps (the "overlay" which makes images clickable and
         have hover-over help-echo descriptions) transform along with the
         image, e.g., if you zoom in on an image, the clickable map still
         matches the zoomed-in image.
@@ -110,10 +110,27 @@ See also: [EmacsConf - 2023 - talks - hyperdrive.el: Peer-to-peer filesystem in
 
 ## Notes
 
--   The \"sources, blockers, blocked\" idea was influenced by:
-    -   Alex Cobleigh :
-        [https://cblgh.org/trustnet](https://cblgh.org/trustnet)
-
+- The "sources, blockers, blocked" idea was influenced by:
+  - Alex Cobleigh :
+    [https://cblgh.org/trustnet](https://cblgh.org/trustnet)
+
+- the safe hyperdrive feature was designed in part based on org-safe-remote-resources.  I'd be curious to hear thoughts on how something like this could be improved or generalized.
+- ooo nice graph
+- Perhaps a function which accepts buffer-file-name and returns non-nil if it's safe to call set-auto-mode
+- also, there was off list discussion related to CVE: untrusted-content
+  - untrusted-content is a variable
+  - we also discussed generalization of this idea with trusted/untrusted files to define them based on file location
+  - in a way it is similar to code blocks inside Org files
+  - not sure if all this is relevant to hyperdrive
+  - It definitely could be.  It could be useful to enumerate the different potentially dangerous interactions we could have with files.
+  - (1) enabling a major mode (2) enabling file-local variables (3) including remote content (4) evaluating code blocks
+  - You might want a file to automatically set major mode but not evaluate code blocks, so more granular control would be useful.
+  - I think that allowing the user to set these safety settings based on buffer-file-name would benefit hyperdrive.el, eww, and any other remote protocol.
+- nice!
+- impressive!
+- idea: try hyperdrive to distribute WORG
+- better yet, those EmacsWiki "packages" that are getting rediscovered every decade or so, if they're not going to end up on a git host (as per its opinionated author's non-interest to do so if I'm not mistaken)
+- putting EmacsWiki on hyperdrive would be useful too!
 
 [[!inline pages="internal(2024/info/hyperdrive-after)" raw="yes"]]