The other day I was talking with some friends about the “old days” before Mastodon supported CWs, and how we used to EBG13 nyy bs bhe cbfgf because, guess what, if Mastodon didn’t have CWs we still wouldn’t throw nyy guvf fuvg out in the open. I realized that I actually kind of liked ROT13 better than the current system, because you could only ROT13 ⁜cneg⁜ bs n cbfg and the remainder would give the reader context as to how the problematic bit was being used.

Then I realized that our old ROT13 system was an effective plaintext fallback for pbagrzcbenel Qvfpbeq-fglyr fcbvyre gntf and that I could just implement that in Mastodon, so I did.

GlitchCat users! You can now create inline spoilers in your posts by using a <spoiler-text> HTML tag in either the Markdown or HTML content modes. Spoilers ⁜can⁜ include emoji but ⁜cannot⁜ include other markup like links, mentions, or hashtags.

Spoilers federate as ROT13 with special properties so that other servers can recognize them. If you are on another Mastodon instance which supports Markdown and HTML content modes, let me know and I can get you a patch!

(note: if you try to boost this toot it may break the app; like i said this is experimental)

@Lady oh that's neat! maybe i'll hack gotosocial to do it too

@KitRedgrave it’s super not difficult from a backend perspective; just a simple element replacement

@KitRedgrave here’s the mastodon implementation (L122–137)

https://gitlab.com/kibicat/mastodon/-/blob/trunk/app/lib/advanced_text_formatter.rb#L122-137

@Lady yeah i think the hard part for me will be figuring out how to build and push gotosocial to my microk8s "cluster" of one vps