Yep, but the happy path doesn't solve anything. It is still centralized media database. Nobody wins if devs stay in the happy path. It's like saying custodial bitcoin is an innovation vs fiat systems. No, it's not. It's just an illusion.

Reply to this note

Please Login to reply.

Discussion

😅 Maybe… it's time to send base64 image event.

Some clients are putting `data:image/jpeg;base64, ` uris right into the .content of kind1 because we don't really have a better solution right now.

this is a great way to disincentivize people from running relays. thanks client devs!

If relay operators are surprised by base64 images, I got news. There are worse things being transfered in broad daylight through regular events.

I just open source a relay who run at cloudflare with workers. It was designed to help people run their relays with the cf's free plan.

With this relay, people can hold their events. and It has one GB for people to hold their base64 image event.

Maybe there also should be many relays are welcome people to send image event with payment.

https://github.com/haorendashu/cfrelay

Like what?

Child porn.

List of npubs for shaming derision and public humiliation pls

nah, the happy path being optimized and working-by-default is fundamental

that's what nostr gets right, the happy path works just as well as the centralized stuff, but if you get censored or infra just disappears you have a very very very easy path to recover which is so simple as to be basically invisible to users

"Works as well" because it is centralized. Blossom is very similar to NIP96 in that regard. Just different api calls. Since nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 raised this initial thread, I don't think it is "very very very easy" to figure it out.