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.

  • Blaze@piefed.zip
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    4
    ·
    11 hours ago

    I use both, starting another flamewar doesn’t seem positive for either project.

    • CobraCommander@quokk.au
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      2
      ·
      11 hours ago

      If I don’t call out bad behaviour it will continue. As it stands doing nothing is only harmful for PyLova who has it’s unique features copied at each step.

      • Blaze@piefed.zip
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        2
        ·
        10 hours ago

        Is Mia supposed to patent Pylova features, and prevent any other Fediverse software to use them, be it Lemmy or Mbin? Serious question, as otherwise I don’t see how this can be solved.

        Features have always been replicated between software, even beyond the Fediverse.

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

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

          • Blaze@piefed.zip
            link
            fedilink
            English
            arrow-up
            2
            arrow-down
            1
            ·
            6 hours ago

            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”.

            • ルルㇲ@retrofed.com
              link
              fedilink
              English
              arrow-up
              1
              arrow-down
              1
              ·
              5 hours ago

              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.

              • Blaze@piefed.zip
                link
                fedilink
                English
                arrow-up
                2
                ·
                4 hours ago

                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.

                • ルルㇲ@retrofed.com
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  arrow-down
                  1
                  ·
                  4 hours ago

                  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.