Screencap from the Simpsons in the Kwik-E-Mart with a shop clerk with words 'JK Rowling' overlaid and an robber pointing a gun at them with the words 'wished ill' overlaid. Apu, with the text 'Bluesky, for some reason' overlaid, jumping between them to take the bullet.
you are viewing a single comment's thread
view the rest of the comments
[+] 34 points 1 year ago (29 children)
  • [+] 6 points 1 year ago (28 children)
  • [–] 14 points 1 year ago (21 children)

    Isn't their federation really fucking weird though? Like you can't run a federated server unless you're capable of handling 100% of all the posts on the entire platform? That's a pretty huge barrier, and one could argue it's less "federation" and more "mirroring".

  • source
  • parent
  • hideshow 21 child comments
  • [–] 6 points 1 year ago* (last edited 1 year ago) (15 children)

    Personally, its as simple as the ATProtocol is hard connected to Bluesky full stop. If Bluesky goes under, then AT will definitely suffer or fail.

    The fediverse (AKA ActivityPub) is not reliant on just one entity, its many many entities implementing the same protocol. So its MUCH more resilient than AT.

    But the good news is that we don't need to choose, as long as AP and AT both exist and keep going its going to be fine. The only issue becomes if services start only using AT over AP. Then we get a Microsoft situation where embrace extend extinguish occurs and we all become reliant on one not so benevolent corporation.

    Im still going to root for the more open source protocol for the above reasons.

  • source
  • parent
  • hideshow 15 child comments
  • [–] 1 point 1 year ago

    Do you mean it's reliant in some sort of technical way, or just that it is currently so dominated by BS that it's hard to meaningfully separate the protocol from the platform in practice? Kinda like if ML was 90% of the Lemmy market share?

  • source
  • parent
  • [+] 1 point 1 year ago (13 children)
  • [–] 4 points 1 year ago* (12 children)

    Lets agree to disagree.

    Ive seen many times where the company behind a tech goes under and the tech suffers because of it. And AT seems to be hard connected to Bluesky given the wikipedia article and the codebase that I have seen. But having competing services is not necessarily a bad thing. It can mean they can both learn from one another (like yarn and npm did a long time ago) and we get a better service. I dont necessarily want AT to fail, but I do want them to become MUCH more distant to Bluesky.

    And they have the most risk to become Enshittied given the crypto/investors/millionaires involved with BlueSky.

    Ill still be supporting AP with my development time since its easier for me to stand up and work with.

  • source
  • parent
  • hideshow 12 child comments
  • [+] 2 points 1 year ago (11 children)
  • [–] 1 point 1 year ago (10 children)

    Again as a Dev, I have to disagree.

    How can mastodon disappear? By definition, its on open platforms and self hosted solutions. It cant. And we are using the spec to talk right now.

    And as a Dev AT really isn't easier to work with. I've tried hooking it up multiple times and while I can do it, its such a pain. And debug is pretty terrible experience. But its a an opinion on both sides.

    You seem very invested in the protocol. Why if I may ask?

  • source
  • parent
  • hideshow 10 child comments
  • [+] 2 points 1 year ago (9 children)
  • [–] 1 point 1 year ago* (8 children)

    Yep! Your using it now ;) at least a very little bit if your URL is correct.

  • source
  • parent
  • hideshow 8 child comments
  • [+] 1 point 1 year ago (7 children)
  • [–] 1 point 1 year ago (6 children)
  • [+] 1 point 1 year ago (5 children)
  • [–] 2 points 1 year ago (4 children)

    Yep, I like piefed a bit more. Much easier to work with and code is very well done. But I helped a bit on Lemmy back in the day. And some other fedi services. A very very small amount. Other devs are much more impressive.

    I also tried creating a couple of AT services and helped a tiny bit of doc work. Didn't work out because of a variety of things. Mostly the pipes/thoughput you need, but also the setup. At the time there was no generic docker setup.

    Anyways more than anyone wanted to know about all that. Now I just fart around on here.

  • source
  • parent
  • hideshow 4 child comments
  • [+] 1 point 1 year ago (3 children)
  • [+] 6 points 1 year ago (4 children)
  • [–] [S] 6 points 1 year ago (3 children)

    Is this federation, though? I've always thought of federation as a technical description of a platform's network topology, that it is several nodes communicating with one another to provide an overall platform.

    Like, an AppViewLite is basically analogous to a Nostr replay and no one describes Nostr as federated.

    A more interesting conversation is whether grafting federation onto Bluesky is worth the effort. If indexing the network can be done for a reasonable price, which it seems to be, then I don't see why people would put in the effort. If an app view/relay goes bad then you can just switch and get mostly the same experience.

    I still believe that the ActivityPub solution of the multi stakeholder platform is a better direction, but I don't think the Bluesky idea of super easy migration should be dismissed out of hand like it so often is on this side of the conversation.

  • source
  • parent
  • hideshow 3 child comments
  • [+] 3 points 1 year ago (2 children)
  • load more comments (6 replies)