Notices by Jon (jdp23@indieweb.social)

thanks much ... @tchambers and @rolle ... problem solved!

@tchambers ah ok, thanks. yeah, code mods and hosted installations aren't a great combo.

@TangerineUI

Me too! Great point @darnell and encouraging to hear that BuddyPress is looking at it.

@tchambers @pfefferle @wordpressdotcom

@tchambers yes. it's working now, so either you fixed it or it fixed itself!

@tchambers you're probably thinking of CounterSocial @stefan

@tchambers that;s great to hear -- and thanks for doing it! I'm pretty sure @jerry turned on authorized fetch for infosec.exchange as well, and I also didn't hear about any perf problems

Thanks for the link, useful info. Agreed that it's a work in progress so wait-and-see mode makes sense. @tchambers @kissane @jonny

@tchambers Fair enough! That's why I say "Evan's description of the "big fedi" view". I don't really like the big/small fedi framing-- I think a fedi that more actively tries to keep Nazis / terfs / harassers off will be *bigger* long-term than one that says "More people is good" -- and a lot of stuff like "fedi will be different five years from now" applies to everybody. But it's certainly a useful (albeit imperfect) description of the "big fedi" viewpoint.

@tchambers Agreed that it's more explicit in the Bluesky model, but Evan really did say that in the "big fedi" view "the account server may set some parameters around content or software usage, but otherwise it’s mostly a dumb pipe".

@kissane @jonny

@tchambers i'm not sure how many people are seeing spam in various places so set up a poll at https://infosec.exchange/@thenexusofprivacy/111959802210233290

@tchambers I haven't seen it myself but I'm told it's the case. I've even expressed my befuddlement: I thought stuff only showed up on the federated timeline if somebody was following them or somebody who boosted it, or if somebody local boosted it. But apparently I'm wrong about that?

@tchambers what's somewhat alarming here is that apparently the spam is winding up on federated timelines even on instances where nobody's following the spammers. So that means that when threads accounts that nobody's following makes transphobic-but-acceptable-to-threads posts they can wind on federated timelines. Of course they can then get reported, and mods can remove them ... but still, there are so many threads accounts that it sounds like a recipe for mod burnout.

@tchambers @cafou yeah. It's just as relevant for the regions of the fedvierse that aren't federating with Threads. If Threads provides a spam-free environment, and the fedierse provides an environment that's consistenly overrun by spam, that's a recipe for most people choosing Thresda -- and for burnout with fediverse admins and mods.

@tchambers thanks much!

@caseynewton indeed, good call!

@tchambers

The fediverse admin came down like the wolf on the fold,
And his cohorts were gleaming in purple and gold;
And the boosting of toots was like stars on the sea,
When the moderation rolls lightly, federting o'er AP

@thisismissem @tchambers

@tchambers They restored it, so it's not particularly good news.

@tchambers It's interesting data, it shows how complex the analysis is!

@marcelcosta @maegul @fediversereport @spla @fediverse @fediversenews

@tchambers Yes.

@tchambers Interesting data, thanks! But ...

Measured in terms of monthly active users, though .social has gone from about 17.5% of Mastodon's total MAU in May to 27% today.

Of course that's not the only measure of centralization but still it's an important one. So I don't think the concern I expressed back then turned out to be imagined or hypothetical.

@michael @mike @IPEdmonton @chad