Skip Navigation
25 comments
  • Maybe a stupid question, couldn't someone just fork it and remove this?

    • Yep, lots of people have been wanting to fork.

      Especially since the excuse for lemmy.ml is the two developers need a "test instance" because there's so many bugs when they release.

      The large instances are usually a couple versions behind because they give volunteers time to fix the code first.

      There's no benefit tying the future of all instances to lemmy.ml

      • Yep, lots of people have been wanting to fork.

        Hm? You make it sound like the devs are blocking that from happening, and that there's all this chatter about it, but people cant decide -- But that's not how forking works. There's no "people want to fork, but they just cant decide how to proceed, or they're being blocked from doing it, or there's been all this talk about forking, whatever whatever." Like usually it's not an all or nothing, it's not a thing everyone has to discuss, "we gotta fork and every instance migrate over to this other codebase." Anyone can just fork it and self host it. I know you didn't say exactly those words, but it kinda sounds like you don't really know much about what you're saying, sorry to say :/ Feel free to correct me if I'm wrong, I'm not an open source dev, just an admin. But idk dude, it sounds like you have a misunderstanding about the big picture of open-source development.

        The problem is maintenance, as mentioned below, but I guess I'm more curious about the federative implications of forking lemmy and running your own fork -- is it feasible? Maybe someone else could answer

      • Fork it, it's free.

        I'd love to see you try to maintain the codebase. That's not free.

25 comments