I think we could build a HTTP CDN that sources blobs from NIP-95 relays. Maybe also one that automatically converts every NIP-95 to a magnet-uri.
It just makes little sense to transfer blobs over websocket. Aren't relays inefficient as they distribute the same copies of the same events?
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z when nostr nest integrations in apps? Is it even possible?
Nostr Nests need to be Decentralized first.
Hint: It's not.
Fantastic. GitHub is afterall not how Git was meant to be used.
Sandstorm.io self-hosted git actually worked well, but nobody cared then. Maybe revive the spirit of it?
Just curious.
Have anyone compare XMPP standards/extensions with Nostr standards/extensions?
Prior art can sometime help devs reason with each other.
Do any of the Nostr clients or NIPs today support single image file, with multiple sources? Just like you can have multiple completely independent seeders in torrent. And each BEP19 seeder can have its own domain and CDN.
https://github.com/webtorrent/webtorrent/blob/master/docs/bep_support.md#bep-support
NIP-95 sounds like a lot of legal liability, depending on your juridiction.
How to handle outright abuses?
Essentially, DID is just npubkey encoded in a different way.
Each app could have a page where users can upvote feature requests? 🙂
Well done with this backwards compatible update.
Can blurhash be also used to check if the image has been changed or modified?
It's hard to know what's going on without an outgoing queue in Damus.
Git is already decentralized. Just ask Linus.

