summaryrefslogtreecommitdiffstats
path: root/2024/talks/hyperdrive.md
diff options
context:
space:
mode:
Diffstat (limited to '2024/talks/hyperdrive.md')
-rw-r--r--2024/talks/hyperdrive.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/2024/talks/hyperdrive.md b/2024/talks/hyperdrive.md
index 83843130..e0247b50 100644
--- a/2024/talks/hyperdrive.md
+++ b/2024/talks/hyperdrive.md
@@ -101,12 +101,14 @@ See also: [EmacsConf - 2023 - talks - hyperdrive.el: Peer-to-peer filesystem in
Adam Porter (github alphapapa).
- Q:What is something surprising about how you or somebody else that
you didn't expect from using the hyperdrive network?
- - A: 
+ - A: Don't quite understand the question. I think the surprising use case for it is to be able to share say a bunch of Org files, link between those Org files... You could use transclusion to to have a discussion and then you could collaborate on on projects using this sort of asynchronous communication using hyperdrive files. If there's a more specific question, I'm happy to answer it better.
+
- Q: You mentioned streaming audio and video - could you confirm that
this is in reference to consumption of media, and not broadcasting
of it - right?
- A: Since the network is peer-to-peer, audio and video is
streamed between peers.
+ - So this is all shared on a peer-to-peer network. So if I have a file on my machine that's a video or audio and I'm advertising on the network that people can download it from me, then if you want to download that video and I have a copy of it, when you click on that video in your hyperdrive, not only does it download it from me, but also you can stream it so you don't have to download the whole thing before watching it. So it is both in terms of serving the file and downloading the file.
## Notes