Basically zero-cost pseudo-decentralized images with WebTorrent and WebSeeds: https://user-images.githubusercontent.com/1653275/222025570-6f893106-9c35-4862-bea6-10e518c91b92.mp4
Discussion
🤔
Interesting, but that torrent has to be hosted somewhere.
sort of. torrents are split up and held all over the place in fragments sometimes
not loading yet. very2 slow here. just loading circle
WebTorrent works great, I used it a lot here at home before using Plex.
Web host + torrent + nostr is more decentralized than Ethereum NFTs.
ot just stick the image in a data url and post as the content of an event. ref it by using the note id.
#[0]
Lots of potential with WebTorrent for image hosting. Iris actually supports WebTorrent already! #[2]
The idea is that if image hosts want they can host the image + a torrent file and hand out a magnet that can be used independently both by clients that implement magnets and clients that don't.
In the worst case we get what we have today already: just images hosted by a server. In the wonderful p2p decentralized case we get people seeding content to each other and hashes being verified.
Now I am thinking that it might be a good idea to come up with a new URL scheme that is backwards-compatible.
Instead of magnet:
This sounds very cool. ⚡⚡⚡
It's a great solution, I also think there is room for a NIP that includes the ability of a key owner to update media locations in the future, e.g. if you move from one server to another. To reduce the link length, it should be path-based and not rely on hashes. It would require a new event that contains path-mappings for an identity and I could have many, sending content to different servers.
Example image link:
"nostr:media:17e2889fba01021d048a13fd0ba108ad31c38326295460c21e69c43fa8fbe515/home/memes/onehourlater.gif"
"nostr:media:17e2889fba01021d048a13fd0ba108ad31c38326295460c21e69c43fa8fbe515/work/memes/onehourlater.gif"
If a link to video/image starts with "nostr:media", then retrieve kind X of the pubkey, which can have multiple different route-mappings that replaces the root (or other parts) of the path.
"home" could map to mypersonaldomain dot com, while "work" coupld map to myworkdomain dot com slash images.
Maybe using ipfs?
With this suggestion of mine, the underlaying storage can be any infrastructure. It can support redirect for regular web hosting (which I think is an absolute requirement for adoption), but it can also do IPFS or anything else really. And the good thing, it allows individual users to migrate their storage when they need to, without destroying all historical events published on Nostr.
ignore all the junk and just use the hash, let the client decide how it delivers
That's stupid. The "junk" is important because the client must know where to find the content. Content-addressability is a scam.