(I personally don't think Bluesky is a bad idea and I'm glad for more things in the ecosystem. But the point of decentralizing isn't just to protect against editorial constraint by the service owner; it's to protect against government pressure too. Mississippi could go after Mastodon service providers, but it'll cost them a lot more to find and chase 'em all).
Like I run one and I'm in Louisiana and I sure do not have the funds to mount a legal defense.
They could try, but not even China could build an impregnable firewall.
> Luckily, we don’t have to imagine the scene because the High Court judgment details the last government’s reaction when it discovered this potentially rather large flaw. First, we are told, the relevant secretary of state (Michelle Donelan) expressed “concern” that the legislation might whack sites such as Amazon instead of Pornhub. In response, officials explained that the regulation in question was “not primarily aimed at … the protection of children”, but was about regulating “services that have a significant influence over public discourse”, a phrase that rather gives away the political thinking behind the act. They suggested asking Ofcom to think again and the minister agreed.
https://www.thetimes.com/comment/columnists/article/online-s...
Or, conversely, I'm unsure if other decentralized platforms would be unable to implement a similar block.
And the "block" is a single clientside geo-location call that can be intercepted/blocked by adblock, etc.
And the "block" doesn't apply to any third party clients. So that includes:
- https://deer.social (forked client)
- https://zeppelin.social (forked client + independent appview)
- https://blacksky.community (forked client + independent appview + custom rust impl of PDS + custom rust impl of relay)
And a bunch of others like:
And I could keep going. But point being there are a thousand alternative frontends and every other bit or piece to interface with the same bluesky without censorship.
And the only user facing components are the frontend and the PDS. The appview can't even see the user's IP, only the PDS it proxies through. So if you move to an independent PDS and use any third party frontend, even if you use the bluesky PBC appview, there is no direct contact/exposure to the company that could be exploited.
The client/frontend calls out to a set of XRPC endpoints on the user's PDS. The user can use any PDS they want but yes most users are on the bluesky "mushroom" PDSes. There are plenty of open enrollment PDS nowadays if you care to look around and want to switch away.
The appview have no ability to interact with the user directly so if you use any non bluesky PDS and non-bluesky client/frontend (both relatively trivial to do), then the appview is basically a (near) stateless view of the network which you can substitute with any appview you want (the client can choose the appview to proxy to with an http header) without ever touching bluesky the company.
And of course there are multiple appview hosts. As well as relay hosts (which the appviews depend on but not the user/client).
There are plenty of ways to go about using bluesky without yourself or the services you use ever touching bluesky the company's infrastructure.
sherburt3•4h ago
sojournerc•4h ago
ronsor•4h ago
none_to_remain•4h ago
LexiMax•2h ago
Unless you're from Mississippi, then you hate on Alabama.
RajT88•16m ago
My own personal metrics: Everyone's got that once racist uncle. Mine moved gleefully to Alabama. I have never known anyone who moved to Mississippi. Or from there!
I bet MS has some amazing old homes out in the swamp with great fishing.