#asknostr #nostrdev is anyone working on decentralized media for #nostr ? hash addressing for media?
Discussion
Where would you store it?
can be stored anywhere, point is you can change storage and the note hash address for the media still works
Unless I misunderstand I think we already have that in nostr, saw some nips regarding signed/provable images and such.
is it in https://github.com/nostr-protocol/nips ?
not signing just hashing, it would need client and maybe relay implementation
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6's suggestion of webtorrent with web fall back seems good
my idea is have like nmjpg(hash) or nmedia(hash) addressing and the client has default url repos to look up on or can check on relays or relays can refer to other url repos
maybe we go p2p and relays act as trackers? point is #p2p becomes an obvious route to relieve server costs
#nostr #nostrdev
I was thinking bout this one since #amethyst seems to support it https://github.com/nostr-protocol/nips/blob/master/94.md
I don't think the problem is storing the hash/magnet rather gaining a consensus on which p2p protocol to use if any.
Web torrent is a torrent only in name - since webrtc was designed by centralized people. (Every single peer connection has to be brokered by a server.)
Ipfs is a cesspit of bloat/complexity. (Will never run on user devices)
Regular torrents, well cool but only makes sense for bigfiles and non-browser clients.
If we can somehow gather all "security experts", ship them off to an island and leave them to enjoy the great debate.
Then we might just have enough time to patch browsers with lowlevel DHT api's and let people figure out the rest 🙂
consensus will form like all nostr after one app successfully adopts then another
looking into magnets they dont seem right for smaller files as they are a hash to find more info on the files to distribute p2p, may as well make a note for that
idea is we address via hash so we avoid centralization and loss of media, which is already happening, same reason we hash address notes, this is nostr philosophy ffs
if we stick to using hash addressing then we can use relays or any server to lookup them and if we want later a dht
Here's a somewhat accessible DHT implementation if you wish to experiment
https://github.com/holepunchto/hyperdht
(Note to self: ooh so that's the layer they stashed the noise handshake)
Dht's traditionally don't use cryptography, but that one seems to support discovery by public key
thinking on this a npub dht might be smart to look up a relay to find more on any npub