Kuba Suder • @mackuba.eu on 🦋

@Kirk Sigh, I’m not evading… I don’t know what else I can tell you.

You said you thought it was open source. I showed you links to GitHub. I said they aren’t censoring the entire network, just the official client. You said you wanted proof and to show you how you can view a Bluesky post in Mississippi. I showed you two custom clients that you can access from MS and one of those you can sign up through.

@Kirk Are you talking about reading posts or making posts or what? You said “produce a BlueSky post that is available in Mississippi”, you can view that link in Mississippi.

@Kirk Ok, how about this here: https://deer.social/profile/bsky.app/post/3lwzadikbrc2u

@Kirk Are you there or do you have a VPN there? I have no way of checking how things are looking from those IPs (ProtonVPN has some US addresses, but none in that state)

@Kirk they aren’t censoring the entire network, just their official client app for it

@Kirk @thenexusofprivacy What’s this then?

https://github.com/bluesky-social/pds
https://github.com/bluesky-social/indigo
https://github.com/bluesky-social/atproto
https://github.com/bluesky-social/social-app

@skullgiver @haui_lemmy @fediverse As for banning, they haven’t written an explicit documentation on this yet, but generally it can be done on a few layers depending on the offence:

- labelling you via Bluesky official moderation service, in a way that can be ignored
- giving you a “force hide” label that can’t be ignored
- suspending your account on a Bsky-hosted PDS
- preventing their AppView from indexing you
- preventing their Relay from indexing your account or whole PDS

@skullgiver @haui_lemmy @fediverse Yeah, I think that’s a pretty good overview, with the caveat that a lot of this is currently theoretical since nobody runs alternative AppViews and relays yet. (I’m planning to build a proof-of-concept in the coming months, though I don’t really intend to run a public one.)

@hoshikarakitaridia @Blaze @fediverse I think the main reason is that this solves a lot of UX problems that Fedi has because of its architecture, things like:

- thread comments, like counts, follower lists not being consistent between instances
- not being able to easily interact with content that’s not already cached on your instance
- user/post search not working globally, for the same reason

On Bluesky, the AppView indexes all that, and you load threads, feeds and do search through there.

@Blaze @ada @fediverse There is a small number of personal PDSes, plus Bridgy’s one: https://blue.mackuba.eu/directory/pdses, but right now there aren’t really any public open-signup ones, because they’re limiting them to 10 users per PDS in this phase (I mean you can create more, but they won’t be seen by the Bluesky relay). They implied that the network/software is not yet ready for this yet at this point, because a lot of things are still in flux (e.g. they’re adding OAuth now).

@BeAware @xnx @fediverse I’m with you on this one, I think it’s important to eventually have non-Bluesky-owned infrastructure alternatives even if a lot of people don’t care about it… I hope we’ll get there

@xnx @ccoremapd @fediverse It was an unofficial term until recently, but they seem to be adopting it a bit more officially right now, see e.g. here https://atproto.com and in the “Glossary” section. But I think this will stay a developer-targeted term, I don’t think they’ll use it in such context as “Sign in with your ATmosphere account” (but they don’t really dictate to third parties right now how they should phrase this on their side).

@BeAware @Blaze @fediverse There’s a small number of self-hosted personal PDSes (https://blue.mackuba.eu/directory/pdses), but the system isn’t really open yet to running larger ones with open signup. The Bluesky Relay doesn’t currently accept more than 10 users on one PDS (with exceptions like Bridgy).

Technically anyone can run a parallel Relay and/or AppView, and hopefully that will happen, but nobody has done it yet so far (Whitewind/Frontpage are kind of different services on the same protocol).

@BeAware @Blaze @fediverse Yeah, so it’s not a bad explanation, maybe a bit biased ;)

The key is that the architecture is very different, and there isn’t a direct equivalent of instances. There are PDSes, but they do much less than Fedi instances, and they also don’t directly talk to (federate with) each other. The data flows from PDSes to relay(s) to AppView(s) and to clients.