Lady @Lady@cat.family

recognizing that queer people were the reason Mastodon's featureset was (and is) what it is, we hoped to formalize power structures which had previously been informal so that Eugen couldn’t do shit like “get rid of unlisted privacy setting” without oversight

in the early months of development there was a SPECIAL DISCORD CHANNEL that if you paid enough on Eugen’s Patreon you could get access to in order to advocate new features. prior to April 2017 this channel was significantly queer. after April 2017 Eugen found other funding sources in the form of white techbros.

THAT’S WHAT IT’S ABOUT

it was a response to CHANGING MATERIAL ECONOMIC CONDITIONS REGARDING MASTODON DEVELOPMENT not simply about “culture shock” or whatever lmao

your five year reminder that MOURNING MASTODON was a response to techbros PAYING EUGEN MONEY so he wouldn't have to listen to queer people anymore

kitten has decided that it is the season for snuggling

i don't think it would even work anyway due to how emoji get federated lol

(i will not actually do this)

brb just uploading ROT13’d versions of all our emoji

neat

made it look good

lmao

i just want you to know that this is horrible

guess what i can do

god it doesn’t support `??` how outdated is this stack

arrow functions which have `this.props` in their body

how does this site… function

there is something really horrifying happening in the glitchsoc frontend codebase

maybe instead of doing a discord‐style ||spoiler|| i should just do a custom elements‐style <spoiler-text> as that would at least make stripping internal markup easier (and also be easier to support in html)

like it kinda sucks that your ||very important spoiler you *don’t* want people to see|| doesn’t actually get spoilered because you accidentally put an <em> tag in there

that’s unintuitive, but also i have no easy way of federating that <em> tag and it’s way easier to just only process text nodes