Replying to Avatar kamakura (en)

I'd like to share with you a service that has impressed me recently.

Japanese users of Nostr like to use NIP-36 (CW) to post NSFW images, but do not actually use it because major clients like Damus do not support NIP-36.

So, Japanese developer nostr:npub1avgeydxyv7kf6tl75kmjsne6wj7sg2r6zt8atz3z6xtzvs6vmheqssyucl has implemented a simple reverse proxy for nostr.build.

https://github.com/ryogrid/NostrNIP36ImageRedirector

This proxy switches the display of images depending on the User-Agent; when an access comes from a client that does not support NIP-36, such as Damus, an image is displayed in order to the original image, prompting the user to view it from a NIP-36-supported client.

To use this, simply rewrite an image URL https://cdn.nostr.build/i/:id to https://i.ryogrid.net/i/:id .

nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s FYI

nostr:nevent1qqsfxwaj90autnfkpgj2g500gwahjh2x0raent24y8ehr2n6tz2ed3qpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qgs9y93m5k86ag6sgzyaa0calwha0h6s97azv5mw8v38v8dp2sv6fkqrqsqqqqqprdrgm9

Reply to this note

Please Login to reply.

Discussion

i think it would be simpler to just PR nip36 in damus but alrighty

Eliza says hi

Not sure whether there's any Swift/iOS dev - mostly web, Go & Rust devs I've seen on Japanese timeline.

Plus NIP-36 will involve UI changes -- it's kinda too forward to PR that 🤔