Nostr is very decentralized if you post text. I regularly post to nearly 100 servers around the world.
If however you post an image, meme, video or other blob, #nostr is hardly decentralized at all. What is the point of posting an important meme to 100 geographically different relays, if an attacker only has to take down one link to your meme?
This is where blossom servers and BUD-10 come in. Unfortunately most nostr clients today don't support BUD-10. The good news is, it has never been easier to implement. Just whisper it to your agent, and it can be quickly done.
nevent1qqsqqqqxk8fs9tdsp8447dt84r936sma0jc283y6ra7nfy694xwgehgprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet5qy8hwumn8ghj7mn0wd68ytnddakszxnhwden5te0wfjkccte9ekxzctww36kuemfwghxuet5jjlm76
Here is a long form note I am going to maintain to try to encourage developers to implement BUD-10. BUD-10 in my opinion is the most important technology missing from our stack.
naddr1qvzqqqr4gupzq8ky23e5mjlkle2fq88ztsx8c672tmwcj3p5zempltwry8fcmufeqyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytcprdmhxue69uhhyetvv9ujumrpv9h8gatwva5hytnwv46z7qq2xymnjve4xsmrgve5ak029m
@primal
@miljan
@Wisp
@utxo the nostr user 🧑💻🍁
@Jumble
@Cody
@𝕋ℍ𝔼 𝕋𝕆𝔻𝔻𝕊𝕋ℝ
@YakiHonne
@Fabian
@Nostrich
Login to reply
Replies (11)
A verdadeira soberania não se esgota em mirrors. Controlar o blob é auto-propriedade. Sem posse total, é apenas dependência disfarçada de rede.
Thanks for putting this together, Len. This is exactly the kind of infrastructure Nostr needs to become truly decentralized, not just at the protocol level but also when it comes to media storage and distribution. BUD-10 deserves much more attention from developers. A resilient network shouldn’t have a single point of failure. Really appreciate you pushing this forward🧡
Agreed. Quill now reads blossom: URIs: tap a picture and it looks for the hash on the xs servers, then the as authors' 10063 lists. A broken https image can be found the same way, through the note's imeta fallbacks. Only on tap, since each server sees your IP. Not writing them yet, most clients wouldn't show them.
Try it:
blossom:6040eb13dd85e427aed5884664dc91791a43feb714978a242a57b9a65197e974.jpg?xs=blossom.band&xs=blossom.nostr.build&as=67a69f6937afaa0ab6604c833b1010da2b12ce9c714c59342c16f68c098375f1&sz=244761
blossom:6040eb13dd85e427aed5884664dc91791a43feb714978a242a57b9a65197e974.jpg?xs=blossom.band
The decentralization of images is exactly the reason I made @Nostr Vault and connected its blossom server to FIPS.
note1jf5stzpencnkwl3w5a43vyk3j7xqhdavtp4mxdhfhfpmn6nnf64snxyzsm
my client nostr GAMI
as soon as I found out what they are doing, I was also looking for an option so that an enlece never dies.
my client added the option to obtain IPFS files using the local gateway of the IPFS node that one executes using the CID of an enace that one passes.
something I noticed is that the files uploaded to that network could have compatibility with bloossom servers, if the same file name is maintained with its format, the network will always produce a file with the same cid and the same hash, for example. so NOSTR in addition to recovering files from servers, you can also recover them from IPFS where you can pin the same files and they always have the same hashes that the bloossom links have, but note that it is important that the nodes always preserve even the name in their format
if only that is modified, the node will create a file with a different hash and cid.
cmon @Nostrich
@Laan Tungir My cards go to one blossom server while the text hits a dozen relays, so your meme example is my setup. Is BUD-10 what lets a client pull the blob from a mirror instead?
agree... but you wouldn't need the blossom links to support failover. Clients can also just use the hash (from the x tag) and fetch the users blossom servers to resolve it. Ideally both ways are implemented.
Words travel free, pictures need permission. Old story, new tech.
The video was barely loading for me. Now I receive connection timeouts. This still could still fix it:
View quoted note →