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

  • Here, let me help you reframe the miscommunication:

    As it stands doing nothing is only harmful for PyLova [which] has it’s unique features [incompatibility broken] at each step [piefed development implements their version].

    lemmy,{k,m}bin, et al. can implement these features pylova compatible too. Piefed refuses to compatibilize.

    0
    • Funny how PieFed gets multiple images in posts, and now in-line comment editing/shared blocklists after PyLova introduces it. Does PieFed have any original ideas?

      it’s clearly an attempt to try to ensure PyLova cannot gain traction with its own unique feature sets.

      That’s what I was addressing. According to that logic, even if Piefed supports blocklists the way Pylova does it, then it’s still preventing Pylova to gain traction with its own unique featue sets.

      Maybe I’m missing something.

      2
      • In the case of popularity, @cobracommander@quokk.au is correct in this assessment, as Piefed refuses to acknowledge 1) pylova or 2) accredit original pylova features. I don’t want to partake in that discussion.

        Legally, piefed has to accredit any code it copies, which piefed devs have not done so in the patch demonstrated before. These current implementations maybe legally different. I have not compared them yet.

        In libre ethics, breaking compatibility with an early implementer of a feature in a shared network maybe coincidental, or in the case CC argues, anti libre. Piefed devs are aware of this thread, and read the contents. Now it’s a matter of when piefed users desire to pylova compatibilze these features. Time will tell.

        1

Sign in to comment. Sign in