Got it. I understand where "Blossom is the villain that allows others to distribute my content" comes from. IMO, this is Blossom’s main use case and strength; it’s built to do exactly this. So maybe it’s the wrong tool for the job if you have media that you, for whatever reason, want to make publicly available but don’t want others to distribute?
I mean, yeah, to soften my previous statement a bit, there are certain Blossom features around AUTH, paywalling, etc. Blossom is certainly less opinionated than I am. But honestly, if your use case requires making something publicly accessible without allowing folks to easily replicate or distribute it, there are better ways than Blossom to do this. We live in a world where DRM can be “the good guy” depending on who you ask.
If I was building, say, the next Internet Archive or tools for public distributed Git like nostr:nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7hycrvd, Blossom could be a great hammer. So my take here is: use Blossom where Blossom’s main strengths are a feature instead of a nuisance. Use NIP-96 or whatever else you want when that’s not the case.
As for clients allowing you to select where to initially upload things, this is slowly improving. Amethyst has allowed you to select your own Blossom server for ages. So does noStrudel, Nosotros, Primal, etc. If your favourite client doesn’t allow you to select your Blossom server, pester them to do it (or submit a PR 🤣).
