cross-posted from: https://piefed.social/c/piefed_meta@piefed.social/p/2603915/piefed-v1-9-is-released-shared-blocklists-auto-bans-and-totp

New features

  • Shared blocklists - these are like feeds except instead of listing communities to join it lists people to block. To to Account -> Blocklists to find this feature. Changes by the blocklist author effect all the people who subscribe to the list, causing them to block the list members. They federate, so you can subscribe to blocklists on other instances.
  • Edit comments inline, without loading a separate page - wjs018
  • Fediverse statistics at https://piefed.social/statistics
  • 2-factor authentication (TOTP) - can be added to your account in the ‘Security’ page in your settings.

For admins

  • Auto-ban based on the bans that instances you choose, with keyword matching on the ban reason. Go to /admin/users/auto_ban. Try putting ‘piefed.social’ in as the instance and ‘spam’ as the keyword filter. It’ll cut down on the work involved in running your instance SO much.
  • Voting pattern graph on user profiles to help spot automated voting.
  • Reset the password of any user.
  • Lots of inauthentic behaviour reports for finding bots and serial downvoters, see /admin/votes and PM me for an instructional video. It’s a lot to take in but the video will explain it all.

API

  • edit matrix user id when saving user profile data.
  • scheduled post endpoints - wjs018

Plus a lot more bits and pieces, browse the list of recent releases in the 1.8.x line at https://codeberg.org/rimu/pyfedi/releases for details.


To upgrade from 1.8.x or earlier

git pull  
git checkout v1.9.x  

Then,

./deploy.sh or ./deploy-docker2.sh


Donations

PieFed is free and open-source software while operating without any advertising, monetization, or reliance on venture capital. Your donations are vital in supporting the PieFed development effort, allowing us to expand and enhance PieFed with new features.

Donations can be made via Patreon, Liberapay or Ko-fi.

    • null@piefed.nullspace.lol
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      2
      ·
      edit-2
      1 day ago

      That comment doesn’t demonstrate whatsoever that rimu “deliberately broke compatibility with pylova”.

      Do you understand the meaning of the word deliberate?

      Of course I do. Do you? How about the word “break”?

      Edit: Do you think deliberate means “not intentional”?

      • Awesome Lowlander@cozyver.se
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        1 day ago

        Oh it only took 5 comments for you to narrow down what your actual issue with my statement is. So your objection is to my usage of the word ‘break’, then? Nothing else? Why didn’t you say so 4 comments ago? And not after you conclusively lost the argument on deliberate?

        Rimu deliberately chosing to not be compatible with Pylova’s identical blocklist feature isn’t the best look though.

        Better?

        • null@piefed.nullspace.lol
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          2
          ·
          edit-2
          1 day ago

          Oh it only took 5 comments for you to narrow down what your actual issue with my statement is. So your objection is to my usage of the word ‘break’, then?

          No, I just thought you might also not know what that meant. Looks like I was right.

          Rimu deliberately chosing to not be compatible with Pylova’s identical blocklist feature isn’t the best look though.

          Source for rimu “deliberately chosing to not be compatible with Pylova”? Your previous source was about rimu not intentionally choosing to be incompatible with Pylova. Which is, of course, the exact opposite of your claim.

            • null@piefed.nullspace.lol
              link
              fedilink
              English
              arrow-up
              1
              arrow-down
              2
              ·
              edit-2
              12 hours ago

              No no, I’m done.

              And it’s extremely obvious why.

              Thank you for providing a good show for everybody else.

              Thank you for demonstrating in real time how you guys lie to push a narrative.

              Edit: I’ll say for anyone reading – these guys never say things like “it’s a shame rimu didn’t make this compatible with pylova” or “rimu should have done his due diligence to make sure this was compatible with pylova”.

              They just go straight for boldfaced lies. They link to the same comments to push the same narratives. There’s a reason they do this. Keep an eye out for it. You’ll see the same names a lot.

              Another one of the usual suspects. Can you imagine how much they would kick and scream if someone mocked them for expressing trauma. They have no standards:

              UjES6jcZd3VTNxd.png

              • Tao of Fremont@lemmy.world
                link
                fedilink
                English
                arrow-up
                1
                arrow-down
                1
                ·
                9 hours ago

                “it’s a shame rimu didn’t make this compatible with pylova”

                After reading this thread (like an idiot, holy shit) I gotta say: Not making it compatible when he knew the other code existed was a choice. A deliberate and intentional one.

                “rimu should have done his due diligence to make sure this was compatible with pylova”

                Choosing not to do due diligence to make it compatible was also a choice, especially when they already know the feature exists on the other site. Was it a malicious choice? A lazy choice? I don’t care and only they know. It was still a choice though and choices are deliberate.

                The way I build PieFed is not intentionally incompatible with Pylova - that happens as a side-effect of me not talking to them and me never looking at their code.

                Willful ignorance is always a choice. He claims it is not “intentionally incompatible” and then goes on to say that he intentionally makes no attempts to make it compatible which to me sounds a lot like doublespeak.

                I won’t be replying because everything I’ve seen from you is in bad faith. You argue like a republican.

                • null@piefed.nullspace.lol
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  9 hours ago

                  After reading this thread (like an idiot, holy shit) I gotta say: Not making it compatible when he knew the other code existed was a choice. A deliberate and intentional one.

                  Intentionally choosing to disengage from Pylova and its developments? Sure. That’s also a fair thing for him to do.

                  Choosing not to do due diligence to make it compatible was also a choice

                  Easy there, Geddy Lee.

                  I won’t be replying because everything I’ve seen from you is in bad faith. You argue like a republican.

                  No, you won’t be replying to me because you’ve seen how good-faith I am and how I expect good-faith from others and you just want to torture the English language.