Back

@dysfun @TechConnectify @JustinH what is being asked for (I think) is to first recognise the problem. This thread shows that this is far from happening.
Second you need some tools and policies to filter the poor behaviour. Less than a ban, but more than "don't look at messages that are addressed to you, that might upset you"
At least I think that's what is being asked for.

@cbehopkins @dysfun @JustinH exactly. One thing that I've just realized is that, when we compare this platform to email, subject lines are effectively content warnings. I don't go to my inbox and see every email that's been sent to me, I see a list of content warnings.

Here, though, it's as if I open my inbox and am reading every single email.

Social media is a different beast from email. A feed full of content warnings is tedious and boring. But there has to be filtering.

@TechConnectify @cbehopkins @dysfun @JustinH I want this platform to work for folks like you, so I'm trying to wrap my head around this. I assume that the volume of block requests you would have to submit is unworkably high, not that your instance is ignoring your block requests? For instance, we're quick to block accounts that are aggressively annoying our users, but we're only like 5 users with the most followed having under 5k followers, so we only get about 1 request/wk.

@holly @cbehopkins @dysfun @JustinH On the bird site, this sort of stuff was just... not a thing I ever had to do.

I blocked maybe half a dozen people and muted perhaps a dozen.

The sort of behavior that's bothering me here simply didn't cross my feed on twitter /because they had automated systems to detect it/ and it was hidden.

I'm really asking for a jerkwad detector - not for a means of recourse when I encounter jerkwads. Because, frankly, not much of what they do merits real moderation.

@holly @cbehopkins @dysfun @JustinH There is absolutely no means of filtering signal to noise here. And the common response to complaints of noise is to play whack-a-mole and stomp it out, or else move instances because they'll have more thorough instance blocking.

But that's not the problem - it's not individuals. It's behavioral norms in aggregate. Some really shitty behavior is tolerated here in no small part because there's no means for the crowd to signal it's bad behavior.

@TechConnectify @holly @cbehopkins @dysfun Not trying to deny your lived experience or anything but "some really shitty behavior is tolerated here" more aptly describes my experience with Twitter than anything on my Mastodon instance.

@holly @JustinH @cbehopkins @dysfun @TechConnectify the thing is Mastodon is like an unregulated pipe. You get everything anyone says, period. Twitter had methods that would pre-filter that for you to make it manageable.

With a smaller following that might be like opening the tap and taking a drink. With a large following I’m imaging it’s more like the UHF scene sitting in front of the firehose.

@TechConnectify @holly @cbehopkins @dysfun @JustinH I already deleted my account so I can’t check, but I also vaguely recall the filter being tied to “chronological timeline” and seeing posts like “if you just want the old tweets in chronological order flip this setting off” so anyone who just wanted tweets in order they happened may have turned it off even if it was turned on at some point for everyone.

I’m almost certain I personally turned it off for that exact reason, but I’m also a rando with sub 100 followers, and the only time it got crazy was when a giant account like LeagueOfLegends retweeted some funny shitpost I made.

@sleeplessone @TechConnectify @cbehopkins @dysfun @JustinH yeah, I think I closed my Twitter account around 2017, and I was frequently hitting the chronological order button (it used to switch back on its own a lot) so I either left before those tools came into being, or I could have been inadvertently turning them off.