Lady @Lady@cat.family

@KitRedgrave wonder how hard it would be to get frontend support into pinafore lol

surely easier than it was for mastodon

@KitRedgrave i guess i can just link the commit for a full picture of what backend support looks like

https://gitlab.com/kibicat/mastodon/-/merge_requests/23/diffs?commit_id=578e1e58c23194ce9ed66ac3fd8e027244f84e2e

the frontend is the more tricky bit; i don’t know what the current state of gotosocial frontends are or if any of them even support HTML/Markdown posts

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

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

and live

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

in

MR is in for fixing this; should be fixed soon

okay so where is that fucking boost modal lmao so i can give it the handler it needs

“kibi are you trying to E·E·E upstream mastodon” no

znlor

culture jamming is when lbh vagebqhpr n arj srngher vagb gur srqrengvba juvpu vf grpuavpnyyl fbzrjung pebff‐pbzcngvoyr jvgu bgure freiref, ohg nyfb ⁜whfg⁜ naablvat rabhtu gung vg sbeprf gurz gb cnl nggragvba gb jung lbh’er qbvat

@alyssa if that wasn’t the case i definitely would have looked into it

@alyssa i’m ambivalent since the current public view will disappear in 4.0 (it’s all going to use the frontend JS; see mastodon.social which is running this code now)

(here is what this post looks like in the frontend for those of you on different servers btw)

(specifically the confirmation popup is broken; sorry local users we’ll fix that lmao)

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

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!