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

  • You have to admit, deliberately breaking compatibility with Pylova’s identical blocklist feature isn’t the best look though.

    6
    • lol nothing Rimu does is “a good look”

      6
    • This is a different question. The comment above is advocating for “Piefed to stop copying Pylova features”, you are speaking about compatibility, which I guess would also be criticized for “copying the feature”.

      2
      • I’m only pointing out the optics of it aren’t great. I do agree Pylova doesn’t have a monopoly on a feature just because it implemented it first.

        2
        • Yeah, it’s definitely not great. At the beginning of this thread, I was hoping some dialog could be established to agree on comparability for the blocklist, but seeing how it went, I don’t think it will happen.

          I’m trying to stay neutral on the whole thing. I like both Piefed and Pylova, and it feels a bit like having two friends who don’t talk to each other.

          Anyway, I’ll get back to subscribing some communities to cozyver.se

          3
      • 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
    • deliberately breaking compatibility

      Source?

      -2
      • You won’t acknowledge it but for everyone else here’s rimu saying well it’s just unfortunate and their fault totally nothing I did

        https://lemmy.world/comment/26882650

        2
      • {
          "@context": "...",
          "id": "https://example.org/blocklist/general",
          "type": "OrderedCollection",
          "name": "General Blocklist",
          "summary": "Description of the list",
          "attributedTo": "https://example.org/u/admin",
          "published": "...",
          "updated": "...",
          "totalItems": 2,
          "first": "https://example.org/blocklist/general/entries?page=1",
          "inbox": "https://example.org/inbox",
          "visibility": "public",
          "subscriberCount": 10
        }
        

        The feature is nothing more than shared basic JSON data. If your thrust is that Rimu is too incompetent to handle that, I don’t really think so, but I can accept that too.

        -1
        • Are you going to share your source for your claim of “deliberately breaking compatibility”? Pretty strong claim…

          -4
          • There are 3 possibilities:

            1. By accident. That would mean Rimu didn’t know about the existence of Pylova’s blocklist feature. Lets not go down there.
            2. Forced / without choice. Because he wasn’t capable of doing it, or somebody held a gun to his head.
            3. Deliberate. He made a conscious choice to do so. Whether because he felt another approach was preferable, easier, w/e.

            You seem to be conflating ‘deliberate’ with ‘malicious’. Those are 2 separate things. Read my original statement again without projecting any of your assumptions onto it.

            0
            • I notice you have once again failed to provide any source for your strong claim. I think at this point we can assume you made it up.

              Gee, who could have predicted the exact crybullies rimu was talking about who show up to tell lies about him any time PieFed is mentioned would show up and tell lies about him!

              -4
              Continue this thread 15 more replies

Sign in to comment. Sign in