Comment on The fediverse has a bullying problem

• scrubbles@poptalk.scrubbles.tech ⁨1⁩ ⁨week⁩ ago

  A great example is his handling of Laravel, scaling, and Docker. It’s pretty clear that he doesn’t have a huge understanding of Docker - or at least hasn’t managed docker images at scale. A huge thing there that I ran into constantly is that the Pixelfed containers both are 1) Stateful and worse than that 2) depend on each other’s volumes. This means that the Pixelfed containers must share the same host as it’s workers. He put a lot of time and effort into building scripts that would simplify the setup for a docker compose file, but never thought horizontally - scaling these containers out on a cluster or separating workers off away from the web-api nodes at all.

  I spent 3 weeks trying to de-tangle that all and got nowhere. I’ve been watching the guys over at glitch-fed ( a fork of pixelfed ), and from what I see they’re trying to do the same thing. I wish them godspeed. Until then, I can’t recommend Pixelfed as it just can’t horizontally scale. Sure you can throw a more expensive machine at the problem, but that’s not a fix.

  As for the last, I don’t have any examples - and I think that’s because no one else has gone on a press junket like he has. The owners of Mastodon started a foundation a while back, I think that’s the most official news I’ve heard out of them. I think that’s what bothered me - for the vast majority of people that was their first chance to hear about the open web. Instead of saying “We have a thing called the fediverse. I’ll spare you the details but you can choose Pixelfed, Mastodon, even Wordpress or many others, and they all work together”. Instead all I heard anywhere was Pixelfed. Feel free to call BS there, maybe he did somewhere and I just missed it.

  source

  • PhilipTheBucket@ponder.cat ⁨1⁩ ⁨week⁩ ago

    “Doesn’t scale because the containers are set up wrong” is different from “unmaintainable code” though. What of the code was bad? I’ve looked at a bunch of fedi projects and Pixelfed didn’t strike me as either particularly good or particularly bad.

    As for the last, I don’t have any examples

    ?

    I mean, that is sort of what I expected. Mastodon doesn’t publicize Wordpress. Lemmy doesn’t publicize mbin. They all, mostly, mention a little bit of the context that they can interoperate with other federated services, but it doesn’t strike me as weird or malicious that someone would write a project and then promote that project. That sounds normal.

    Actually, both Mastodon and Lemmy chose to implement sort of their own versions of ActivityPub, and that actually does strike me as selfish behavior. It means that mostly they are their own independent platforms that run “on top of” ActivityPub instead of enabling full interoperation with the other stuff. Doing it that way was hard to avoid, because the design of ActivityPub to me isn’t great, but this situation is actually a perfect example of that: Mastodon implemented a new feature in a way that would break (in a really jarring privacy-violating-to-some-extent way) until everyone else copied their implementation exactly. I’m not aware of Pixelfed doing anything like that. Mastodon and Lemmy can both get away with presenting themselves as “the fediverse” and forcing everyone else into copying one implementation or the other if they want things to actually work, and they both show very little interest in making it easy. If you want to pick out sins of various fedi projects to start to point out that are disrespecting the other projects in the space, something like that is where I would start.

    source

    • Microw@lemm.ee ⁨1⁩ ⁨week⁩ ago

      Everyone I ever talked to told me “well yes we have to implement our own version of ActivityPub because AP is under-defined”. In most cases it is defined what AP does, but not how. Therefore individual programers go in and figure out on their own how a certain thing they are building for their platform should be structured in AP.

      Now, every project could simply go “I will copy the way Pixelfed implements it”. But why should PF have that priviledge?

      source

      • PhilipTheBucket@ponder.cat ⁨1⁩ ⁨week⁩ ago

        Agreed. It’s not completely their fault. But also, they’ve run further than they needed to with the “I’m in charge of what protocol I’m going to speak to other instances running my own software” than they needed to. Case in point, this exact issue with “private” posts. A lot of things had to be fleshed out more so than they are in the AP spec. This feature needed to be handled more carefully than that.

        source
      • rikudou@lemmings.world ⁨6⁩ ⁨days⁩ ago

        I shared a bit about exactly this here: lemmyverse.link/lemmings.world/comment/14476151

        source
    • ThorrJo@lemmy.sdf.org ⁨6⁩ ⁨days⁩ ago

      Mastodon implemented a new feature in a way that would break (in a really jarring privacy-violating-to-some-extent way) until everyone else copied their implementation exactly.

      You ever notice how Gargron refers to the fediverse as “the Mastodon network?”

      He’s been doing things this way since 2017 at least. At this point, any longtime observer really has no other choice but to consider the behavior deliberate.

      source
  • rikudou@lemmings.world ⁨6⁩ ⁨days⁩ ago

    Using Laravel as a framework should be the first red flag, I yet have to meet a Laravel dev who understands architecture (and I interviewed quite a bit of them). That framework is several anti-patterns bundled into a nice package.

    source

    • scrubbles@poptalk.scrubbles.tech ⁨6⁩ ⁨days⁩ ago

      I mean, I completely agree but last time I said that people flamed me over it. If it was still 2013 then I’d look more into it, but today it’s such a monolithic architecture

      source