Hummm.. I will investigate more tomorrow.
nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 nostr:npub1u83gudwdfwjngz5eqxkrnpvsuydvqwjxwz0majvehqrh62804hfq8yr2s5 nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z >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.
nostr has implicit time expiration. if I were running a relay I'd purge 3m old or greater posts. if it were under load I'd clear every week, day, or even hours if it were bad. that's *terrible* for a file transfer protocol. it's good for social media where there's no concern about whether content actually reaches their destination.
I think you are just speculating. If you had a relay, you would know that behavior would just drive people away and your relay would not be used that much anymore. It's better to offer options to pay for longer storage if it gets to that point.
The proof is that every event in Nostr is still fully recoverable, even the ones from 2 years ago. Even large ones.
On top of that, people that want to put up a website are more than happy to pay for the storage. All they want is to not be held hostage by the provider. And Nostr gives them that. They can pay for 5-10 relays in different countries for a cheaper amount than they would pay for CDNs today.
Either way, we will see what will happen.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z any idea why my Global New Threads feed would be empty?
#asknostr #amethyst
If i go to conversations it's fine
Check to see if you have relays active for the global feed. There was a PR to only show posts from relays that are active for global.
Because proposing is 100x harder than reacting.
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.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1j3vtkuurx77yzs33ufzzc08syhrqca8aawa5p4afnfqxrnzvugmqrmqxec nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6
1. reinvent redundant CDN service except NOSTR!!!11
2. it's free
3. wait that's not sustainable. relays start charging
4. oh look it's back to being a paid CDN
seems like the only upside here is that migrating between vendors is transparent because it's the equivalent of paying someone to seed a torrent for you. of course the obvious downside is that anyone can jump in and host your stuff and in so doing sample your traffic
I don't see why a solution where you pay for speed couldn't be implemented on top of ipfs. but then http relays for ipfs already exist and could be paid to serve your content quickly. and that protocol seems better suited to the task
> I don't see why a solution where you pay for speed couldn't be implemented on top of ipfs
Then do it. Let's see if it actually works.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 that's becuase nostr relies on good will of relays to host your content........... try uploading a 1TB file and see how that goes. torrent/ipfs can handle it fine because it's decentralized.
Websites are not 1TB files, man... Most of them are in the kb range and most relays take in up to 100Kb events like nothing (I tested :) ).
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 no it's really just stupidity, bittorrent/ipfs exists for this exact reason
Again, it doesn't matter if it's stupidity or not.
But to your claim, I tried IPFS and torrents. They don't work for websites. They are way too slow.
But Nostr does.
That's the beauty of this. It doesn't matter what you think. People can do whatever they want in Nostr.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 oh my god people are really using nostr as a transport for files
We have been doing this for months now. :)
Imagine shipping new JS libraries into Nostr and every version is immediately available to everyone else. Just update your event ID and boom, a new version of a dependent website is up.
nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z why would you want to do this though
Redundancy. You can broadcast the html or js code to any relay you want.
In the future, browsers will load the event directly from relays. When that happens the little server I put up won't be needed anymore.
You would download entire websites from your favorite relays.
Hello World hosted on Relays: https://nostr-webserver-3c29f7957ffe.herokuapp.com/e/1efc13c6ffbaf60c0347baf89f6ecaad22f74abf82165fcdb55ef7e8cca8a597
Nostryfied hosted on Relays https://nostr-webserver-3c29f7957ffe.herokuapp.com/e/7b8a47b1c97b449e842bc0186e89102874ea801b041c822fdecac50f2f3d91b2
My server's code: https://github.com/vitorpamplona/nostr-web-server that simply exposes the `.content` data of images (kind 1065 and 1064), css (kind 5393), javascript (kind 5394) and html (kind 5392) events.
FYI, my server is not very stable :)
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z Hey do you have a link to that Nostr-hosted static HTML site? It was importing .js and .css files from Nostr relays through an http proxy.
Hello World hosted on Relays: https://nostr-webserver-3c29f7957ffe.herokuapp.com/e/1efc13c6ffbaf60c0347baf89f6ecaad22f74abf82165fcdb55ef7e8cca8a597
Nostryfied hosted on Relays https://nostr-webserver-3c29f7957ffe.herokuapp.com/e/7b8a47b1c97b449e842bc0186e89102874ea801b041c822fdecac50f2f3d91b2
My server's code: https://github.com/vitorpamplona/nostr-web-server that simply exposes the `.content` data of images (kind 1065 and 1064), css (kind 5393), javascript (kind 5394) and html (kind 5392) events.
It has always been like that. It's now just more uniform across the app.
Sorry, I forgot that part. Fix coming in the next version
https://satellite.earth/ has a "subscription" feature for communities, so I wonder if the same would apply here too? (I definitely don't understand enough of details here)
We do the same for communities. But it feels like we are cramming too much into the contact list