The NIP-36 specification requires that post be tagged with a content-warning tag (so that users can clearly identify the post as such when they post it). However, even if this is done, non-NIP-36 compliant clients still display tagged posts as usual.
As a result, although overall compliance with the specification is progressing, a non-negligible percentage of clients do not support NIP-36, leaving users with a psychological barrier that makes it difficult to post Sensitive Content.
Therefore, the purpose of the specification is to avoid users of non-NIP-36 compliant clients from unintentionally viewing content with content-warning tags, and to allow Nostr users to think that it is safe to post Sensitive Content if they specify content-warning tags.
The following service was developed to avoid unintentional viewing of content with content-warning tags and to make Nostr users feel it is safe to post sensitive content with specifing content-warning tag.
- You change the hostname of the image URL with i.ryogid.net from cdn.nostr.build before posting, which causes an error when acquiring the image and prevents viewing on clients that do not support NIP-36.
- Example of URL replacement
- If you access the original URL with a browser, you will see the image, but the replaced URL will return an error image
- access from a browser is not regarded as access from a NIP-36-compliant client.
- This service is only to assist the purpose of NIP-36, and is not a stand-alone feature. Therefore, be sure to specify the content warning at the time of posting!
- https://github.com/ryogrid/NostrNIP36ImageRedirector
- Pull requests are welcome!
- especially if you know more NIP-36 compliant clients
- If you have a short domain and are willing to host it on your own server, you are welcome to do so
- Pull requests are welcome!
- i.ryogrid.net
- (It doesn't matter if there are more)
- Amethyst
- Plebstr
- Snort
- Rabbit
- Nostter
- Astraea
- 井ラスト倉庫 (Illust Warehouse)