Same as any relay. So my point stands. This doesn’t lead to more centralization, it’s the same level as before or greater decentralization if you think further and deeper. Nostr is still WIP so don’t judge based on what you see today, instead write a sustainable and efficient proposal and make a NIP. It’s easy to judge from the sidelines, and I am guilty of that sometimes too 🐶🐾🫡

Reply to this note

Please Login to reply.

Discussion

not the same as any relay as the content on relays is not tied to them, we dont and shouldn't address notes as http://relay.com/noteetc inside notes

Copy image to multiple hosts, host your own, many options 🐶🐾🫡

the problem is notes use static addressing for media

Just my two sats:

- Regarding authentication of images, all notes show who wrote the note anyway, nip98 just uses the data to authenticate.

- Notes, links, etc. can still be censored by an app, service, anything, based on the writer, content, link, etc. look at the previous censor dramas with Amethyst and Primal, no nip98 needed! Twitter censors and you have nowhere else to go…

- Regarding the static address, that is true of any html link. Any image server, news outlet, website, can change the content of that link. Including other social media platforms.. The solution would be to use a trusted link, or something with specific html link authentication.

- Supporting nip98 allows for nostr.build and other clients to interact better with each other, more reliably, openly. True it can open to more censorship, but it will open even more openness! For every image or note someone wants to censor, there is someone that wants to see it.

Great work!

the solution to static addresses is not trusted links but hash ids like ipfs does CID but it will start with nmjpg or nmedia etc