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...

23 reposts308 likes

See: bsky.app/profile/aend... Also, the history of journalism-focused instances on the Fediverse is... Not great! I write this as somebody who tried to start the first one!

ændra.@aendra.com

Possibly! But it's a much different moderation decision to block a whole PDS (even if single user) versus suspending an account that exists on a mushroom PDS. My suspicion is Bluesky would be much more reticent to censor users whose data they're not hosting, especially if they're press.

I've discussed it in a few talks but not written about it extensively, I should sometime... Ghost/WP Fediverse support is really exciting for small publishers (and overcomes one of the biggest problems of big tent journalism instances IMO), but I don't see it as very viable for larger orgs.

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

I’ve been meaning to make a PDS which is also its own app view. A “web site”, if you will, but with the reach of ATProto syndication and a built-in comments protocol.

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?

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

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.

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.

Wait so if we have another odd we are still subject to Bluesky’s moderation rules and not that particular pds’s only? If so what’s the point of switching if we disagree? Or find you “bad stewards” or whatnot, as you said once?

People who use Bluesky (the application) are subject to their moderation practices. So the answer to your question is: depends on where are people actually reading your posts from.

Bluesky in 2023: “lol, those Mastodon geeks and their circular firing squads about decentralized content moderation.” Bluesky in 2025: “we should decentralize because of content moderation decisions.”

Possibly! But it's a much different moderation decision to block a whole PDS (even if single user) versus suspending an account that exists on a mushroom PDS. My suspicion is Bluesky would be much more reticent to censor users whose data they're not hosting, especially if they're press.

I'm pretty sure that they will tend to censor individuals by their public key. It's an easier workflow and more politically safe than trying to discern if a whole PDS may need to be censored for a single infraction.

Yeah, it would be *really* good to even be able to understand how moderation works now, let alone how they intend to apply in a hypothetical massively-distributed future.

In addition to a micro-AppView. The missing atmosphere microblogging app is something small enough that can be run anywhere and is a single-user index that other people can log into to like / reply to posts. TBH kind of sounds like a standalone feed viewer.

That's close to the small-index appview @retr0.id said he considers making. Basically an appview only indexing stuff you follow, proxying all other requests to a bigger appview. That would be a good base for stuff like a near-full-stack self hosted atproto blog with comments

For the reasons others have mentioned, I think what we need is some sort of ultrathin frontend you run on the same server as your PDS that bypasses the entire Relay/AppView system and just fetches posts from your PDS and displays them. That way you can just direct people to your website.

I think that this might help in situations where a prominent account goes down in a visible way: it lets folks look at recent posts and check receipts themselves. it's also just cool/nice as a simple way to show recent content on a homepage (sans interaction metrics)

To be clear, when I say "I think we need…" I mean "I've sketched out an implementation in my head and intend to write this, hopefully before the end of the year".

…of course, at that point, it's not clear to me why you'd go with ATP/Bluesky at all instead of one of the ActivityPub/Fediverse solutions…

portable identity is the best part of atproto and the lack of it is the worst part about activitypub. having to change handles or instances shutting down / being too censorous makes living on the fediverse a pain. imo activitypub with dids would be better than atproto in its current state