Notices by Synkr3tyk (synkr3tyk@mastodon.social)

Earlier today I was being chased by an aggressive driver in a CyBeRtRuCk, but I lost him in a car wash.

@Gargron Because viewers will generally tolerate or enjoy the familiar, and the people who bankroll new shows are generally too cowardly to bet on new stories

@dansup This is great to see. There's a small open source project I was thinking of forking, and I've been worried about the community response. You've given me a little cause for optimism.

@griotspeak scaling moderation and culture, which is *far* harder, because you can’t just throw money at it.

So far, I see a lot of paranoid chatter about OMG THEY COMIN FER MAH DATAZ, and very little mature thinking along the lines of, “wtf are we going to do when we see multiple order-of-magnitude traffic spikes, consisting of people who have never heard of the Mastodon Covenant?”

This thinking is not entirely absent, but it is dismayingly rare. 2/

@griotspeak And here’s the thing: Meta doesn’t need those lessons about scale. They’re the teacher here, and it’s going to be an adversarial process, driven by the difference in prerogatives between a huge, centralized entity focused on growth at all costs, and a heterogeneous, decentralized band of server admins and community leaders who (IMO) don’t understand the real issues at play. 3/

@griotspeak Subscribe to the Meta domains blocklist or whatever; if you share your content/data outside your own server, over an open protocol, you’ve lost control over what happens to it. Do you think it’s really feasible to gatekeep?

To be clear: I’m not saying Meta coming in is a Good Thing - just that it’s an inevitable thing in an open ecosystem. Openness cuts both ways, and all of us in the Fediverse are going to have to figure out how to live with that.

Or, you know, not.

@griotspeak I see it boiling down to two cases: One can restrict distribution to people/servers they know and trust - that is, aggressive whitelisting and walling off one’s patch of the garden, creating a small, closed, and (putatively) safe ecosystem - or one can grant any degree of openness at all, and deal with the consequences of openness. A Fediverse or a Fediarchipelago are the poisons from which we may pick.

@griotspeak I’m not saying other ways are impossible, but I’m not entirely clueless about the technical and practical issues here, and I have difficulty seeing how any solution doesn’t collapse to one of these two cases.

@griotspeak There are people who know more than me, and it would be good to listen to them. But here’s my thing: IMO, the success (or failure) of the Fediverse is going to be directly attributable to how well people here - including and especially the smaller communities, which is where I see the value - understand, prepare for, and cope with the real threat, which is *scale* - not just in the purely technical sense involving network traffic and server load, but also 1/

@feditips I see that it *does* show up in my timeline when someone I follow boosts it. Is this the intended behavior?

@Gargron Par for course since Cook took over

@Gargron Ever watched a user encounter one of your bugs during testing? 😬