Skip to content

Comment on PieFed v1.9 is released - Shared Blocklists, Auto-bans and TOTP

You are viewing one comment and its replies. View all comments · View the comment above

Comments

  • Its a fork isn’t it? So like 95℅ of the codes the same.

    4
    • The fork split off 7 months ago, PyLova independently added these features weeks and months before PieFed ever did.

      And it has now been confirmed that Rimu has made it non-compatible.

      12
      • I’ll take a look later. It should have a tiny bit my code in there.

        EDIT: So I took a look. If this is the repo:

        https://codeberg.org/quokkau/PyLova

        Then im seeing piefed code pulled into pylova as soon as Nov 5th. Last week.

        It looks more like pylova is pulling from piefed rather than the other way around. I mean this is what open source is for. But it sure looks like rimu did most of the work when you look at: https://codeberg.org/quokkau/PyLova/activity/contributors

        By a HUGE factor.

        It also looks like piefed has much more active development. So this seems like a silly argument to have by a long shot.

        8
        • You can clearly see where the project forked and any upstream contributions from Rimu basically stopped existing except for some bug fixes being bought over, of which PyLova has also contributed to PieFed with bug fixes.

          image

          It does not seem a silly argument to call out a larger project from copying every idea introduced into a rival fork weeks after they introduce it. Why isn’t PieFed coming up with original ideas for what to offer its users? Is the project that devoid of trajectory that it has no idea what it wants to do next.

          image

          4
        • Thank you for having a look

          4
        • Pylova is built 50% on piefed, 50% on a complete misunderstanding of what open source software is.

          -2
      • Maybe it’s because the PyLova maintainers refuse to let their code be contributed back, loosing their shit and accusing Rimu of stealing instead of contributing their code back.

        -5
        • Rimu is welcome to bring over PyLova code, he only needs to attribute it instead of deliberately removing the author from the work as he did last time and has been well documented in his conversation with others admitting trying to do.

          9
          • Did he really though? For the main code including the patch file should have preserved the author for the commit, right? As is shown in the blog post. Honestly that is enough to meet the license requirements. I guess you could argue that he skipped it for the themes, but really? Do you still think that warrants the narrative that they’re stealing code? (Which is a fucking rich statement for a fork to accuse the source project of anyway)

            It would also have been nice to shoutout in the release notes as well, but we never got to see that because of the drama.

            -3
            • image

              He exported the code as a patch, while not knowing it would make her (correctly) the author. His intention very clearly looks to be as if to use her code without bringing over the authorship. And he did do exactly that later on with copying the themes and renaming it.

              So yes I believe that warrants calling out at the time he did steal the code.

              I am not saying he stole the code here, I am simply saying he is jacking the new features being introduced in an effort to harm PyLova by making it not be able to stand out with unique features. These are really the only big new user facing features he is adding and it’s conveniently shortly after we do.

              10
        • the PyLova maintainers refuse to let their code be contributed back

          as soon as the fork was made, were the PyLova devs not banned from all Piefed channels? was the first security patch authored by the PyLova devs not ignored by @rimu@piefed.social, despite attempts to reach out so that Piefed could take advantage? tell moth, how long should the PyLova devs continue reaching out, only to have Rimu push them away? why do you have this double-standard?

          6
    • @Die4Ever@retrolemmy.comOP· · edited

      Yeah that means PyLova copied a lot of features from PieFed lol, that’s how forking works.

      It does suck if it’s not all compatible though, I hope that gets figured out

      -3
      • all attempts to reach out to Rimu are shot down by Rimu and the persons blocked or banned from Piefed channels, so moth isn’t sure how things will get “figured out”.

        6
      • Yeah that means PyLova copied a lot of features from PieFed lol, that’s how forking works.

        Yes and forks give attribution. They essentially say, “this is a fork of this other program. It is made with a lot of the other program’s code. We wouldn’t exist in our current state without using the original codebase as a starting point.”

        Whereas Rimu has a history of behavior which shows his thoughts are more along the lines of: “This is mine. Someone else came up with the idea and wrote it, but their contributions aren’t contributions because I don’t like them and so they don’t deserve credit.”

        3
      • It wouldn’t be so bad if Rimu had actually copied the code, which would then be compatible. Or even implement his own code in a compatible way, if attributing PyLova’s devs is such a taboo for him. But he chose to implement a non compatible feature, fomenting fragmentation and a worse user experience. And for what?

        3

Sign in to comment. Sign in