I was not aware of this spec but it looks similar to what I've written for blossom in that it uses the sha256 for the id of the file.
however I think it has some issues
1. Its only focused on images and videos. if we want to solve the storage problem it needs to be generic
2. It relies on the "/.well-known/nostr.json" document for servers to describe themselves. this makes servers not interchangeable when it comes to retrieving files
3. It only focuses on uploading and retrieving the files. I think its also necessary for users to be able to list and delete the files they have on servers
Oh the beauty of a concise, knowledgeable answer ❤️
is your spec/protocol documented somewhere I can read it?
I think the issues you highlighted from the old spec are trivial… but that’s neither here nor there.
nostr:naddr1qqxkymr0wdek7mfdv3exjan9qgszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgrqsqqqa28e4v8zy
nothing happens when I click that link in damus 🤷
It's long form content, not sure how Damus handles that.
https://njump.me/naddr1qqxkymr0wdek7mfdv3exjan9qgszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgrqsqqqa28e4v8zy
The naddr works for me on Damus. Maybe your relay is missing it @ben ?
hmm the single relay my damus connects to just fans out there REQs to 5 or 6 big public relays. maybe something about the naddr link doesn’t work 🤔
I know. Sometimes long form content exceeds default size limitations (on strfry for example) so the note won’t be ingested. Not sure if that’s the case here.
not sure yet but thanks for the tip, that’s a great place to start debugging 🫂
Oddbean new post about login | logout