nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1j3vtkuurx77yzs33ufzzc08syhrqca8aawa5p4afnfqxrnzvugmqrmqxec nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 no u :laugh: why wouldn't it work? how would directing clients towards particular nodes that you had paid for a fast response be any different than what's being done with nostr here?

it's an interesting proof of concept and I think it's a good idea. nostr just seems like a distinctly inferior protocol when it comes to file hosting

Then prove it. I am doing my part and proving Nostr can be a good small file manager: the types of small files you see on websites. If you pay for relays then it gets even better. But it already works as is.

Try to do the same with IPFS or Torrents. A lot of people claim IPFS and torrents can solve it. Most people that make that claim never actually tried and have no idea how misfit those protocols are for the types of content we are using here.

I tried and I couldn't get either IPFS, or torrents, to be speedy enough for websites. You always need to relay on a centralized hack to make them work.

Reply to this note

Please Login to reply.

Discussion

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?

how about retroshare / turtle ? ( https://en.wikipedia.org/wiki/Turtle_F2F )