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.

  • mesa@piefed.social
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    2
    ·
    edit-2
    1 day ago

    I’ll take a look later. It should have a tiny bit my code in there.

    EDIT: So I took a look. If this is the repo:

    https://codeberg.org/quokkau/PyLova

    Then im seeing piefed code pulled into pylova as soon as Nov 5th. Last week.

    It looks more like pylova is pulling from piefed rather than the other way around. I mean this is what open source is for. But it sure looks like rimu did most of the work when you look at: https://codeberg.org/quokkau/PyLova/activity/contributors

    By a HUGE factor.

    It also looks like piefed has much more active development. So this seems like a silly argument to have by a long shot.

    • CobraCommander@quokk.au
      link
      fedilink
      English
      arrow-up
      4
      ·
      12 hours ago

      You can clearly see where the project forked and any upstream contributions from Rimu basically stopped existing except for some bug fixes being bought over, of which PyLova has also contributed to PieFed with bug fixes.

      image

      It does not seem a silly argument to call out a larger project from copying every idea introduced into a rival fork weeks after they introduce it. Why isn’t PieFed coming up with original ideas for what to offer its users? Is the project that devoid of trajectory that it has no idea what it wants to do next.

      image

    • cabbage@piefed.social
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      2
      ·
      14 hours ago

      Pylova is built 50% on piefed, 50% on a complete misunderstanding of what open source software is.