I did say clearly and explicitly that Nostr shouldn't be used for DMs (I did it in the Nostr Telegram group at the time, that had like 20 people, of which maybe 5 were the only ones really interested in Nostr). Still @Ben Arc made the first Nostr client with DMs after I begged him not to. Will this clear fact make you reconsider your position? If that isn't enough you can also take into account my twtxt example. If I make an effort I can probably come up with many other things that I think Nostr shouldn't have but that now it has standardized just because not having a standard would be worse as people would do it anyway in less interoperable ways. I never said Nostr shouldn't have images, because that idea didn't occur to me and I don't think images hurt that much (you can always opt to not use them yourself, and not associate with people that do), but I'm sure Nostr would end up having images if it had grown to more than 40 users anyway.

Replies (3)

JOE2o's avatar
JOE2o 1 month ago
Images trigger CSAM obligations, CSAM obligations make it super hard for small players to scale. Also images lead to video, and video (especially bandwidth) means everything starts to cost a lot, hosting and CDN serving naturally starts to centralise. For text-only nostr, really anyone can join in on the infra side, it's so insanely cheap. Unrelated, but if you could go back in time would you still call it nostr? If not, what would you call it instead?