nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1j3vtkuurx77yzs33ufzzc08syhrqca8aawa5p4afnfqxrnzvugmqrmqxec nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6

> You always need to relay on a centralized hack to make them work.

how is relying on nostr relays (centralized) any different?

my point here is that if this were to actually take off the current arrangement wouldn't scale. right now you're free loading on donated bandwidth. in a sustainable scenario you'd have to pay specific relays to host your stuff for you (ie serve as a low latency CDN) and hint clients to query those first

at that point I have to wonder, why not just do exactly the same thing but with something like IPFS?

Reply to this note

Please Login to reply.

Discussion

You can have multiple relays bozo, your ability to communicate is not centralised.

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.