Nostr Web Client

Nostr and IPFS are similar in that they both use content IDs. I think the network layout is different tho. IPFS does hops or something. Files take 10 minutes to load or not at all. When you host a file, nobody copies it.

Nostr works a lot better for sharing content, as long as the events are small enough and can be represented as text. It will get replicated and served relatively quickly.

I don't think it should ever be a general purpose "drive". But it might make sense to store some types of text files on it, and there are probably interesting ways it could be used we haven't discovered.

creator of #fediblock :verified::makemeneko: 2y ago

nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 nostr:npub1j3vtkuurx77yzs33ufzzc08syhrqca8aawa5p4afnfqxrnzvugmqrmqxec nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z so my point here is that for nostr to gain the abilities of ipfs would be quite a leap. whereas for ipfs to gain an additional low latency ability for content selected by the node operator seems quite trivial. you literally just give a hint to the client about where to look first (list of nodes that you paid)

if you pay a node to host content for you then queries to it don't need to do a bunch of hops, indirections, block lookups, etc. you just ask the specified address (ie centralized server) for the object and it sends it back to you immediately because it has the entire thing sitting there because that's what you paid them for

you could literally reuse existing ipfs http relays for this. set one up that only fulfills queries for stuff it has pinned locally and then charge to pin stuff on it. I'm not saying that's a particularly elegant solution but it would work at which point I'm really wondering what the point of nostr is in this scenario

Reply to this note

Please Login to reply.

Discussion

Coyote 2y ago

nostr:npub1u83gudwdfwjngz5eqxkrnpvsuydvqwjxwz0majvehqrh62804hfq8yr2s5 nostr:npub1j3vtkuurx77yzs33ufzzc08syhrqca8aawa5p4afnfqxrnzvugmqrmqxec nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z As an example of IPFS being used in web hosting, The Permanent Booru (github) uses IPFS as its media store and doesn’t have latency issues on its production server. It accomplishes this by running its own gateway that has all the media pinned locally and will only serve those files (it isn’t a general purpose gateway). You can even get reasonable response times using other gateways, too. cloudflare-ipfs.com seems to be peering with the master gateway right now, for it doesn’t take much more time to fetch an image from it than from the master one.