yup, the bluesky servers discover, connect to, and crawl from this PDS instance.
-
yup, the bluesky servers discover, connect to, and crawl from this PDS instance. the analogy for atproto is that PDS servers are blog hosts, and "appviews" discover, crawl, and aggregate the RSS feeds of all these blogs in to a global view. unlike AP, public content is public w/o permission
-
beaware@social.beaware.livereplied to bnewbold.net@bsky.brid.gy last edited by
@bnewbold.net but...you contradict yourself...
https://fed.brid.gy/r/https://bsky.app/profile/did:plc:44ybard66vv44zksje25o7dz/post/3l2dcseax3j2e
-
exerra@daedric.worldreplied to beaware@social.beaware.live last edited by
@BeAware@social.beaware.live @bnewbold.net@bsky.brid.gy To me it seems like they're right. Whilst (at a quick glance) you can't host your own UI, the PDS acts as a backend that you can connect to through clients (something like Akkoma), and I remember that iOS had alternative bluesky clients.
So yeah, it doesn't go through bsky servers to log in and do stuff (apart from the client itself), but since most users are on the Bluesky server, it has to interact with it for content (similar to a self hosted instance with mastodon.social).
Maybe it's not like that though, idk, I don't have any PDS's to test it on. -
beaware@social.beaware.livereplied to exerra@daedric.world last edited by
@exerra @bnewbold.net but...their PDS still connects to BlueSky servers in some way.
That's the disconnect. There's no way to *not* have that happen.
I have my own front and backend of Mastodon here, but I can completely cut off mastodon.social and connect to everyone else. They cannot do that.
Until that happens, I am uninterested.
️
