Discussion
@cwebber remember how Bluesky talked so much about their design goal of avoiding the confusing situation in fedi where you see different parts of the conversation and different like and follower accounts depending on what instance you're on?
hahahahaha ...
https://blacksky.community/profile/jdp23.thenexus.today/post/3mtzhlfafec22
@adriano @jdp23 @cwebber There is also the W Social AppView, which seems to be in maybe some kind of alpha state right now. They have made the statement that it "only serves W-verified users" (verified in this context which they mean people who have uploaded their ID to a "third party" which appears not not be a third party, but W itself) - but the main reason I bring that up is that one possible interpretation of this sentence is that only returns accounts, posts, etc. from people that have been verified, and the rest of the atproto network is invisible. If this is correct, well ... I'm just sort of speechless
W Social interacts by default with the rest of the ATmosphere, but aparently there's a browser extension from somebody there that lets you block everybody on a different PDS. 🤣 And there's also a blocklist of "W Social critics" (including @elena's ATmosphere account ... a badge of honor).
The ATmosphere really is a lot more like fedi than people in either ecosystem want to admit.
The Blacksky web app fetches all profiles from both it's own AppView and the Bluesky AppView, and uses the follower numbers from the Bluesky result, since the Blacksky one doesn't have a full network view.
@ricci wait, hold on.
So are you saying that the poster child project ATmosphere project that supposedly is proving there can be a completely independent BlueSky-compatible service turns out to require both their own infra *and* BlueSky to work in order to work at all, including for folks only on Blacksky?
"Require" is too strong there - the behavior I linked to is (a) mostly just cosmetic (b) can be turned off with little consequence (in fact they *might* have done so during the last multi hour Bluesky outage - I know if I were in their shoes I would have)
Maybe the best fedi analogy I can make here is: you know how we're all used to the fact that if you look at a remote account's profile on your own instance, it might be incomplete because your instance may have a stale cache, not have seen all their posts, that kind of thing? And we know (in part cause the Masto interface says so) that you might need to click through to the original server to see the whole thing? Well imagine Masto had a feature where, when you were viewing the profile locally, it quietly also fetched it from m.s and used that data as authoritative for stuff like follower counts. Yes it would mean you're hitting m.s constantly from your client, but it's not actually very important.
Install bonfire.cafe
Get the full app experience
