you may have those people blocked or silenced but does the originating server? or are you just creating more work for a moderator somewhere else along the line
if your ideology is that it is your moral responsibility to send people’s #introductions posts to servers where there are people who will harass them, maybe rethink that one for a sec
if you're on mastodon you probably possess the sicko urge to run janky community tools yourself, so i present for your consideration: our small-scale self-hosted streaming platform: https://gitlab.com/egirls/dios
« ‘Hey, Jessi, why do you draw the moon as full in nearly every instance regardless of the time that’s passed in the story?’
Thank you for noticing, it’s because circles are a great design element and I love the moon and she deserves it. »
from https://www.geeksout.org/2022/04/27/interview-with-graphic-novelist-jessi-zabarsky/
what i would like to see of mastodon dev is:
- instances finance themselves and make a determination based on their finances what labour they can offer. no central financing or donation mechanism for development.
- that means all developers are there on behalf of one or more instances, who form the stakeholders of the project.
- broad agreement across stakeholders on the purpose and immediate direction of the software (i.e., a single platform). ideally, multiple different forks with different platforms, but cohesion within any given project.
- initially, a very slow pace of development. very few new features. immediate focus on increasing maintainability of the software, improving documentation, and making onboarding easier. this is a hard sell; it's hard to get stakeholders (instances) to continue to finance development which does not give them anything new. in fact this work may introduce delays in acquiring upstream features. i’m not sure how to resolve this except with tangential personal incentives like: gaining a better understanding of rails, learning better development practices, personal satisfaction at making a complex software more easily understood…
- project longevity.
- good and active communication with users (of stakeholder instances).
Administrator / Public Relations for GlitchCat. Not actually glitchy, nor a cat. I wrote the rules for this instance.
“Constitutionally incapable of not going hard” — @aescling
“Fedi Cassandra” – @Satsuma
I HAVE EXPERIENCE IN THINGS. YOU CAN JUST @ ME.
I work for a library but I post about Zelda fanfiction.
For the time being, this is mostly a mirror of <https://status.ladys.computer/>. Want to get in touch? E·mail me!