I would like to give an update on "federation" on Bluesky
-
@mcc well, it's incremental implementation. Having their own client lets them make different blocking decisions from Bluesky, so is useful in its own right even though it doesn't get all the way there. The real value of the appview will kick in once it's got the equivalent of local-only posts.
@jdp23 "Having their own client lets them make different blocking decisions from Bluesky"
How?
-
@GroupNebula563 @mcc Would be nice! Won't happen though.
-
@alter_kaker @mcc hmm, apparently not that much knowledge is required, and the cost dropped significantly, I still don't trust any of it though
@esoteric_programmer so this is all within my ability. But what about the rest of the stack? To my understanding, the PDS and view? As @mcc says things have to change in a social level but the first step is more nodes...
-
I would like to give an update on "federation" on Bluesky.
My expectation was it was unlikely we'd ever see this happen because "federation" on ATProto means basically reproducing the entirety of the Bluesky software stack. In old Big Data terms, on ActivityPub your instance is a "horizontal shard" of the network; ATProto forces full DB replicas only.
Still, we're seeing movement on this front, which I'd split into two categories:
1. Your fault (you reading this)
2. Aaron Rodericks's faultI'm mainly surprised that the facade fell so early with Bluesky. I expected atleast another few years before something happened to expose the reality.
-
because #bluesky operates on the #cryptoBro credo (since bluesky is run by crypto bros)
in #crypto, the con is:
1. promise a lot
2. don't deliver
3. but nevertheless generate adoring devotion off of the promisethis works like gangbusters
because people want to believe. they even get defensive and angry when you point out promise vs reality
it's a hack of human psychology
-
I (me, mcc) never trusted Bluesky, so I've been self-hosting my own PDS from the start. I've been happily using blacksky.community for the last month (since Bluesky started gating access to their appview/web frontend on clicking to agree to a new TOS that seemed to me sketchy). Hypothetically, "Gertrude" could do the same. She can join Northsky PDS, make posts through Zeppelin, and Bluesky blocks her but Blacksky just fetches the posts from her PDS for me, and I get to read them.
Right? (2/3)
@mcc Which PDS implementation are you self hosting with?
-
I would like to give an update on "federation" on Bluesky.
My expectation was it was unlikely we'd ever see this happen because "federation" on ATProto means basically reproducing the entirety of the Bluesky software stack. In old Big Data terms, on ActivityPub your instance is a "horizontal shard" of the network; ATProto forces full DB replicas only.
Still, we're seeing movement on this front, which I'd split into two categories:
1. Your fault (you reading this)
2. Aaron Rodericks's fault@mcc There's also https://plc.directory/, the
did:plc:database, also run by Bluesky.("
plc" stands for "placeholder", because they aspire to figure out something blockchain decentralized later.)I think Bluesky can inconvenience people at best, or hijack their accounts at worst, especially if they were using a Bluesky PDS and Bluesky has all the keys. But I don't know/remember the exact implications.
-
@alter_kaker @mcc hmm, apparently not that much knowledge is required, and the cost dropped significantly, I still don't trust any of it though
@esoteric_programmer @alter_kaker @mcc This is curious to me, because it looks like he's running a relay as an actual relay, just passing along data, which would explain why it's relatively low-cost. But the Relay described by the Bluesky white paper was more than just a relay— it was a replacement (or rebrand) for the earlier Big Data Server that was supposed to not only pass data, but also store and index it all for the network. And I can't tell if those other, more expensive functions got offloaded to other services, or if there are two types of relays in the infrastructure, or something else.
-
If you sign up with https://blacksky.community you get:
- Blacksky's "appview"/web frontend
- Optionally, Blacksky's PDS
- Blacksky's moderation layer (and you can optionally enable Bluesky's too)Almost-complete independence! What I'm not clear on is to whether, or to what degree Blacksky relies on Bluesky's "relay":
@mcc (if this is too off topic just ignore!)
I noticed that Blacksky asks for a birth date when you make a new account.
Bluesky didn't use to ask. No idea what they do now, but I would not have made an account with them if they required a birth date.
I'm sure people make up dates but I was still surprised. I'm guessing this is related to age verification laws? I don't know much about them.
Have any Fediverse servers started to ask for a birth date when a new account is created?
-
@mcc Which PDS implementation are you self hosting with?
@fabrice the official one. It seems fine.
Is there a reason to pick another?
-
@mcc I don't know :) Maybe the Rust one from blacksky is less resource intensive?
-
@mcc (if this is too off topic just ignore!)
I noticed that Blacksky asks for a birth date when you make a new account.
Bluesky didn't use to ask. No idea what they do now, but I would not have made an account with them if they required a birth date.
I'm sure people make up dates but I was still surprised. I'm guessing this is related to age verification laws? I don't know much about them.
Have any Fediverse servers started to ask for a birth date when a new account is created?
@ahimsa_pdx I don't know. I didn't make an account, apparently.
-
@mcc There's also https://plc.directory/, the
did:plc:database, also run by Bluesky.("
plc" stands for "placeholder", because they aspire to figure out something blockchain decentralized later.)I think Bluesky can inconvenience people at best, or hijack their accounts at worst, especially if they were using a Bluesky PDS and Bluesky has all the keys. But I don't know/remember the exact implications.
@mnordhoff yes, the plc is another really frustrating thing
-
@mcc I don't know :) Maybe the Rust one from blacksky is less resource intensive?
@fabrice yeah, I dunno. I haven't noticed a load problem from the typescript implementation. I don't have a very data oriented operation over here tho
-
And that's why I say, TLDR:
- I am legitimately excited about the work being done by Blacksky Algorithms! I am using their frontend and happy with it.
- Northsky is an interesting development to watch
- If you're on a Bluesky PDS, I recommend migrating off with one of these tools https://bsky.app/profile/did:plc:ii5jchdzlmcojjw4dqczcgkh/post/3lyt6t6qfa22u
- Everything Sucks. A LOT of things would have to change at a social level for *any* entity other than Bluesky to have power or independence in the ATP ecosystem. I still don't trust Bluesky.
As an update since posting the above thread I have received replies from two people, one saying I am underestimating the level of stack coverage Blacksky has, another saying I am overestimating it. Also a "AppView" and "Client" are different. Sorry.
The stack is just so tall! There are *so many* layers in this protocol's model. And it seems like every single one of them is an opportunity to introduce censorship
-
I would like to give an update on "federation" on Bluesky.
My expectation was it was unlikely we'd ever see this happen because "federation" on ATProto means basically reproducing the entirety of the Bluesky software stack. In old Big Data terms, on ActivityPub your instance is a "horizontal shard" of the network; ATProto forces full DB replicas only.
Still, we're seeing movement on this front, which I'd split into two categories:
1. Your fault (you reading this)
2. Aaron Rodericks's fault@mcc Look, Bluesky has some nice advantages over the fediverse, mainly that it's not confusing at all because it gets to the point of just being old Twitter.
Federation is not their strong point and will never be, whether we like it or not, if you want federation and multiple communities, Activitypub is by far the best option.
-
-
@esoteric_programmer so this is all within my ability. But what about the rest of the stack? To my understanding, the PDS and view? As @mcc says things have to change in a social level but the first step is more nodes...
@mcc @alter_kaker @esoteric_programmer I think the key point is: "Every Bluesky replica is, probably without realizing it, making a bet that Bluesky has already plateaued." This is a worthwhile experiment, as long as you can pull the plug at a moment's notice and lose nothing. -
@esoteric_programmer @alter_kaker @mcc This is curious to me, because it looks like he's running a relay as an actual relay, just passing along data, which would explain why it's relatively low-cost. But the Relay described by the Bluesky white paper was more than just a relay— it was a replacement (or rebrand) for the earlier Big Data Server that was supposed to not only pass data, but also store and index it all for the network. And I can't tell if those other, more expensive functions got offloaded to other services, or if there are two types of relays in the infrastructure, or something else.
@lrhodes @mcc @alter_kaker @esoteric_programmer My understanding is that relays have a "replay since timestamp X" functionality, so that consumers that go down for a while can get back up and running. Originally relays by definition had to support any X back to the beginning of time, leading to absurd storage costs. Today they are allowed to have a much shorter window, meaning in effect the storage cost is insignificant and it's the network cost that dominates. Unless I'm mistaken, the canonical store of a user's posting history is and always was the PDS. -
@alter_kaker I'm not the person to ask. I would join the Bluesky API Touchers discord (yes, it's really named that) and ask there.
Blacksky has all their software on GitHub (they are using a mix of original Bluesky software and their own stuff) but not instructions on how to deploy it as a whole stack.
@mcc @alter_kaker "I would join the Bluesky API Touchers discord"
But... why are they not using... no OK never mind.
I'm so glad for this thread! I've had a bazillion questions about AT but nowhere to ask them. I really think there should be an "other protocols" channel on activitypub.space though. This is not "Technical discussion about ActivityPub-related topics" and sooner or later someone's gonna get angry at us.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@GustavinoBevilacqua almeno è un po’ meno impari 😉
-
Non credo ci saranno le moltitudini…
-
@GustavinoBevilacqua ah a braccio ? Usti…. Magari aperto a interventi live? Comunque sia credo che molti non conoscano Linux né il fediverso. Proporli come alternativa a Ms, ai software proprietari e ai social centralizzati secondo me apre un mondo. Non proponi solo un OS (tecnico), ma un ecosistema alternativo (tra l’altro già molto “costruito”, non serve partir da zero… ormai è facile da usare, molti usano il fediverso ecc.
-
Terrò presente per il mio intervento, per il quale non scrivo alcuna traccia: sarà una specie di dialogo platonico.
Ma Platone aveva il vantaggio di essere un ex-pugile…
-
La butto lì , magari l’idea (modesta) interessa a qualcuno : Linux , open-source e fediverso —> un’alternativa umana all’enshittification ? @GustavinoBevilacqua
-
@iftas hello, I am a blind Fediverse user and I could not fill in the survey about moderation because the form builder you used is not completely accessible -radio buttons aren't screen reader friendly-. It's a contraddiction, working to improve an open environment like Fediverse, cutting some people off. #11y #ccessibility #blind #disability #fediverse
-
mat@friendica.exon.name I am not opposed to a category discussing alternatives protocols.
-
@mcc @alter_kaker "I would join the Bluesky API Touchers discord"
But... why are they not using... no OK never mind.
I'm so glad for this thread! I've had a bazillion questions about AT but nowhere to ask them. I really think there should be an "other protocols" channel on activitypub.space though. This is not "Technical discussion about ActivityPub-related topics" and sooner or later someone's gonna get angry at us.
