Leo Wandersleb @LeoWandersleb - 8d
So I'm staring at the plans of nostr:npub1nxy4qpqnld6kmpphjykvx2lqwvxmuxluddwjamm4nc29ds3elyzsm5avr7 and wonder how much of a vendor lock-in I'm subscribing to here. Media is not content-addressable. To my understanding, blossom is being used in nostr to have content-addressable media where migration to new blossom servers avoids vendor lock-in, right? Is nostr.build not offering this? What are the trade-offs as a user? Should I renew? Should I opt for blossom instead, going forward? Even if I bite the bullet and pay $60, how much will it cost next year? I really don't like vendor lock-in. https://i.nostr.build/Eq7BZeoJo2oYktly.png nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w
Gigi and 21 others @Gigi and 21 others - 8d
nostr:nevent1qqs8g5g6q2f0xt8c3hejgeup63lkpc7xg3tegkw97n8xfyqjjgfcmgcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygye39gqgylmw4kcgdu39npjhcrnpklphlrtt5hw7av7z3tvyw0eq5psgqqqqqqsux64km
I know and I love you took on this challenge! I find it a bit pricey but I was happy to pay it to get this going. By over-paying for a service, others get the signal that there is demand and hopefully competition will drive the price down. Long term, I just realized that I was putting my media files on an irreplaceable server while relays are replaceable as they should be. I like the integration with noStrudel. Just take a screenshot and paste it in the new note but it should be blossom such that once my media files are deleted from your servers, clients can find them on my new blossom server(s). Now I'm confused as to why you don't push me to use your blossom.band server as nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc pointed out. Isn't that exactly what I was asking for?
The Fishcake🐶🐾 & 763 others @The Fishcake🐶🐾 - 8d
Blossom.band is the same as nostr build, and you can use it if Blossom is your choice. The content uploaded onto blossom.band ends up in your account on Nostr.build. So for the practical purposes they are the same.
Well, content addressability and the nips around blossom allow me to delete a39f24d2c4372c2d6654f1a0272b8ef6a8f4042718051b68cc65b08ef0d2fd45 from your blossom server and put it on mine and my followers will find it. This is not true when my events reference nostr.build urls. So ... for the very practical purpose of switching hosting provider they are not at all the same.
If this isn't a thing yet, I assume there will be a market for blossom servers where providers offer me to copy over all my media from other blossom servers.
nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr may know more, but from my understanding the URL in itself is not so relevant for blossom. And we do have the full list of what is supported and not on blossom.band with all the link and details
