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.

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

    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.

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

      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!

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

        At this point I’m not sure you even read my comment… WHAT strong claim? Would you like to take a look at my previous comment and tell me which of the 3 possibilities you think was the case?

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

          WHAT strong claim?

          You made the strong positive claim that rimu deliberately broke compatibility with pylova.

          I’ve asked you twice now for your source for that claim. You’ve instead given me other scenarios you imagine could be the case if it wasn’t true that rimu deliberately broke compatibility.

          That’s completely non-responsive to my question… No one asked what you imagine might have happened.

            • null@piefed.nullspace.lol
              link
              fedilink
              English
              arrow-up
              1
              arrow-down
              2
              ·
              edit-2
              18 hours 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
                ·
                18 hours 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
                  18 hours 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.