Post

So hear me out: managed single-user PDS hosting for journalists

Aftermath@aftermath.site

Bluesky really doesn't want people to say "rest in piss" about Charlie Kirk aftermath.site/bluesky-char...

Applications still have discretion to remove individual accounts from the application. Self hosting your data is great but for moderation independence you want an alternate application

To be clear, are you saying here that even if Bluesky PBC wasn't hosting the data of the journalists who posted "rest in piss", Bluesky PBC would still censor those journalists at the appview level?

3 reposts110 likes

Traveling back in time to when I started getting interested in open source software to show younger me this tweet, shaking the poor guy and asking frantically “you see how none of these words make sense to you? That’s a very good thing. Do you really want to just understand these sentences?”

wait, can you say more "at the AppView level"? I had assumed that it was you do takedowns when the account is on a bskypbc PDS, and then the bskypbc moderation labeler also always issues a takedown label on the same content/account

so in my mind, "at the appview level" i assumed thats actually the moderation layer? using your own pds and the type of client that still uses the bsky appview api but allows unsubscribing from the bskypbc moderation labeler (like deer) would be a way around it right?

Yeah, that's also what I heard before: Which, I agree, is also not how I expected composable moderation to work, I thought AppView takedowns would be used only for like, illegal stuff, and most would happen on the labeller only - because you *can't* go around that just using a different client… 😕

bryan newbold@bnewbold.net

today, in practice, most "takedowns" apply at the appview, and also at PDS if we host the account. we don't have much precedent or process specific to indie PDS instances (both accounts and entire instances), but that will probably become more of a thing over time.

Kind of suprised people are suprised at this since its been widely shared multiple times that the AppView level is where moderation action happens and that the PDS is interesting but not the keys to the kingdom.

there's this interesting pattern where architectural details get communicated but don't propagate into mental models. people hear "PDS lets you self-host" and construct "therefore immune to platform moderation" without integrating the AppView layer. technical literacy vs. systems thinking gap

Yep. Yes, greater decentralization requires further decoupling Bluesky the company from the social network(s) that run on the protocol, but that’s not something Bluesky the company can do beyond providing the software.

Robin Riley@riley.pub

Moderation of massive flagship servers – ie the first server, used to ease adoption and breathe life into an open protocol – is INEVITABLY fraught. It can and should improve, but those are bandaids. The structural solution looks like this: MORE COMMUNITY OWNED SERVERS.

The other piece is "monolith" vs "decouple systems". Mastodon, for instance can be self-hosted, but it's data+app+distribution in one deployment. ATProto is more like Legos, where each piece of the puzzle can be connected in different/multiple ways. Folks aren't used to that architecture yet.

I think it's a bit more nuanced, and I really need to publish something about the overall design, and where things are today. as one example, you might use multiple distinct apps; an appview takedown only impacts one. see also google+apple accounts with so many eggs in one basket

is it always intended for each app to run an AppView? I feel like an AppView is just a context pool of one set of lexicons and should be a objective as possible while still being slightly opinionated. otherwise the only apps for bsky that can exist are ones that can afford $300/mo. + moderation

by design there is a lever to do "label takedowns" using !takedown that would only impact clients/users using bsky mod service; separate from appview infra-layer takedown. but we have that in our actual policies/process today.

I remember when I first learned about this a long while ago and it's when I lost most of my interest in the protocol itself. It kinda defeats the point of what I was looking for in a system like this

I’m curious as well. As for me, future proofing means being able to be on bluesky or some alternative of it even if bluesky servers don’t work or the devs ban people for idk, criticizing them. Or something. And being able to circumvent potential bad moderation attend by bluesky and stuff

i honestly don’t know right now. am i understanding this right? we can migrate to different hosting but bluesky still ultimately determines if we get seen or not unless we create an entirely different app?

P(aul) Frazee@pfrazee.com

The action happens at the AppView level. And the rest in piss actions got reversed

I think they're only censoring it at the appview level. The data is still in the PDS - Bluesky just isn't letting anyone see it. I believe what you're looking for is journalist self-hosted PDS + self-hosted appview.

This is interesting from operational risk, monetisation and product management perspectives. If more permissive apps become more popular they attract more eyeballs: both users and regulators. BTW, in the UK there is no law covering defamation of the dead, so this moderation is a matter of taste.