Keeping Mastodon non-toxic & benevolent requires total community buy-in when it comes to moderation.
Yes, we have mods + admins. But we must also habitually practice individual moderation using the robust safety tools at our disposal.
This means blocking clear-cut trashbags AND reporting them to admins
This means also reporting trashbags to the trashbag's own home instance admins.
It means calling out bad actors early and often & sharing information via #FediBlocks & boosts.
So many people are having a bad first experience with Mastodon because they're using the official app which is lacking features, doesn't allow image uploads randomly, has random slowness, and doesn't give you easy access to the two most active feeds where you can find people (Local and Federated).
Please switch to Metatext, Tusky, or Tooot for a better mobile experience (or even use a browser).
Out of the >15k users that joined this week, over 11k are on the official apps.
@Lady
- mobile accessibility issues: you’ve got the general issue of the sidebar taking up space which is then exacerbated on about more by the fact that everything has been put into boxes thus wasting further screen space eg, compare the amount of useable space in our current page vs .coffees (chosen at random bc it was an instance I’d viewed recently thats on 4+)
- the “server rules” section appears to be highly limited in a way that seems to flatten communication to a set of contextless checkboxes (I’d need to investigate more to be sure of this but I haven’t seen a single one so far with rules more than a couple sentences, no allowances for internal structure/subheadings etc)
- what cat said about not allowing html, if true, would fucking suck. see previous rants about importance of community culture & self definition
the overall effect seems to be to make instances more visually similar & discourage any kind of longform / nuanced communication through a variety of unwelcome changes
@Lady you’ve heard most of mine but to try to put them in one place:
- dislike home page defaulting to /explore instead of /about/more — I have never once wanted to see another instances federated timeline and I have only very rarely been interested in browsing their tags. On the other hand “whos the admin” or “how large is this instance” or “do they have a policy against [thing I’m considering reporting one of their users for]“ are questions I have more or less constantly. Also ideologically I think communities should be able to self define which about facilitates and explore does not
- also, strongly dislike the new /about/more design (these two are the biggest like, “please fix this ASAP” requests for me lol)
- no remote follow/reply 😭😭😭😭
- the sidebar is super irritating on mobile when you’re trying to just read a thread (or another long-form thing like /about/more) bc it takes up like half the fucking screen
- “get the app” link in footer — wtf???
- get rid of “publish”, post is fine or we can do some cute theming thing like mew
fediblock
archiving is complex, but it should always be opt-in. needs from the medium like representing longform content should be taken care of by modifying the medium so, again, people can opt-in (and opt-out if they aren't interested in longform content). I say this as someone invested in scraping as a practice (ethically, against corporations who conceal information in bulk, not aggregating personal information or using it contrary to people's wishes)
I'm helping people join Mastodon & the Fediverse this Saturday 1pm EST at @iffybooks, both in-person and virtually: https://iffybooks.net/event/mastodon-onboarding/
To help me teach newbies the basics, could you please share with me any questions you have, no matter how "stupid" the question may seem to you? Or, send me tips that helped you get your bearings in this new virtual neighborhood.
I've been on Mastodon since 2018 so I'm sure I'm forgetting some roadblocks, and some things have changed for onboarding people.
@bloodwrites @admin @fandom yeah groups (theoretically) solve the issue of hashtags not federating completely — downside is they can get *super* noisy if people start chatting back and forth without untagging the group (#1 reason why I’ve had to unfollow groups in the past)
#Ao3TagOfTheDay Sibling Bonding, well actually it's just sibling arguing
blorbo.social wants to be a welcoming place for marginalised people, including #BIPOC fans.
We know many areas of fandom have not been welcoming. We want to build a community where racists aren't welcome, and there's zero tolerance for microaggressions.
If you're interested in joining our moderation team, please contact me. We especially want to invite fans who are black, indigenous, or people of color.
(Boosts appreciated)
(Experimental?) New Features in Kibicat Mastodon
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!
@godtributes @stelepami that escalated quickly 😆
sleepy af
also https://satsuma.dreamwidth.org/
User Icon is a variegated purple and yellow highlights — made by flowerdeluce.dreamwidth.org