• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: July 23rd, 2023

help-circle








  • Plopp@lemmy.worldtoFediverse@lemmy.worldWhat's your take on Bluesky?
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    3 months ago

    It’s been quite a while since I read about the inefficiency. I think it had something to do with CPU load, and that it’s unnecessarily “chatty” in some ways that causes servers to use unnecessarily large amounts of data. And the extensions had to do with different types of services, where the AP spec is best suited for one type of service (like maybe micro-blogs iirc), and others have to use the spec in weird ways or add things on top of it to implement other features that are important for those other types of services, like more forum-esque type things like Lemmy. Don’t remember exactly what they were, but one thing I read last week was that guy who had to shut his AP project down because he used a method of fetching data, that Mastodon (or whichever service it was) uses but isn’t part of the AP spec, and poorly documented, so he implemented it wrong which had horrendous consequences for him, but that’s a different story.


  • Plopp@lemmy.worldtoFediverse@lemmy.worldWhat's your take on Bluesky?
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    5
    ·
    3 months ago

    Well, there are many different aspects to take into account. I was thinking more of how inefficient AP is when it comes to system resources and network usage, and some other things I can’t remember that made me go “yikes” when I read it. Also how it’s used for things the protocol doesn’t really have support for, so devs make their own solutions that are now part of the AP Fediverse even though the protocol itself, that is the backbone of the thing in question, doesn’t support the things that is a part of the thing. It seems a big mess in many ways, and I believe that Bluesky doesn’t have those issues.



  • Plopp@lemmy.worldtoFediverse@lemmy.worldWhat's your take on Bluesky?
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    2
    ·
    3 months ago

    Yup. PBC is just a slightly different flavor of a standard corporation. Bluesky have investors, they’re burning investor money right now, they don’t know how to monetize the platform yet, and when those investors come knocking for their ROI it’s the same ol enshittification process all over again. No thanks. I don’t care if the backend is FOSS as long as it all revolves around a corporation, especially one with the roots of Bluesky. If there grows a viable and open community and ecosystem out of that, completely self-sustaining without the need for the corporation, using the FOSS code (or perhaps preferably a fork of it), then that’s a different story and that could be interesting.






  • Defederation is an absolutely necessary tool. There are instances out there you don’t want any part of, with CSAM etc. But with that said I think defederation should mostly be used for such things. Block lists (containing instances, users, hashtags) that users can subscribe to would be a better way to handle the rest, and instances could recommend and/or curate lists for their users and maybe activate them by default.

    Instances defederating from another instance because that second instance hasn’t defederated from a third instance is a good way to ruin the future of the Fediverse I think. It’s just an immature and destructive behavior leading to fragmentation.