2
PieFed v1.9 is released - Shared Blocklists, Auto-bans and TOTP (codeberg.org)
submitted 7 hours ago by to c/PumpkinDrama@reddthat.com
comment fedilink hide all child comments
 

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

**Rust port: ** https://git.polarisocial.xyz/hirrolot19/piefed-rs
https://piefed.polarisocial.xyz/

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.

no comments (yet)

sorted by: hot top controversial new old
there doesn't seem to be anything here
48 comments in c/fediverse@lemmy.world view that post
[–] 20 points 14 hours ago (5 children)

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.

Maybe an unpopular opinion, but I have mixed feelings about the social/community implications of shared block lists.

It's essentially social blacklisting, and while it gives people more options for controlling what they see, I'm not entirely convinced it's healthy compared to manual blocking of users and servers on an individual level.

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
  • [–] 3 points 6 hours ago

    I think it's way healthier than the uninvited community mixing that comes from automated post merging. There's already a pretty significant ideological bent against moderating communities on the threadiverse; this is just an opt-in tool to counter the entitlement to an audience.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 5 hours ago (1 child)

    It really helps communities of people who get harassed regularly. This feature not being on mastodon was a big reason the blacksky community formed based on bluesky. They tried fedi first but desperately need these types of controls to keep from getting called slurs.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 2 hours ago

    Actually kind of funny that your comment and another right under you are kind of like the same reasoning from both sides. Like one doesn’t want the furrys harassed and one doesn’t want to know the furrys exist. So ig the block list thing is not the worst?

  • permalink
  • fedilink
  • source
  • parent
    • [–] 5 points 8 hours ago

    All I want is to be able to view my upvoted and downvoted content in voyager and Alexandrite.

    👍 1
  • permalink
  • fedilink
  • source
    •
    [–] 12 points 14 hours ago (2 children)

    Auto ban sounds terrifying and definitely won't be abused

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 3 points 5 hours ago* (last edited 4 hours ago) (1 child)

    I mean, it makes running a smaller instance a lot easier. Maybe read what it actually does and think about why it would potentially be problematic.

    Presumably people running small instances would make us of this drawing on moderation efforts from a bigger instance that they trust. It'll benefit people on smaller or single use instances, but shouldn't affect the majority of users. Just makes decentralization more painless.

    I agree some other name such as "filtered banlist federation" or something could seem less scary as a label than "auto-ban".

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
    • [–] 3 points 1 hour ago

    Giving control over blocks and bans to a 3rd party sounds like a great idea. Especially if you like groupthink.

  • permalink
  • fedilink
  • source
    •
    [–] 8 points 18 hours ago* (35 children)

    PyLova already had this feature, does PieFeds work with it or is it breaking Fediverse compatibility?

    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?

  • permalink
  • fedilink
  • source
  • hideshow 35 child comments
    •
  • [–] 18 points 16 hours ago* (14 children)

    Sharing of ideas and code is a core tenant of FOSS. PyLova literally started as a copy of Piefed. Why shouldn't the ideas and features flow both ways?

    Multiple images in posts and in-line comment editing are basic features coppied from Reddit (and, like, every social media site), which probably coppied them from somewhere else. Let's not pretend like PyLova is breaking new ground here, lmao.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 14 child comments
    •
  • [–] 8 points 15 hours ago* (3 children)

    These are only being added straight after PyLova does it. And considering Rimu’s hostile history it’s clearly an attempt to try to ensure PyLova cannot gain traction with its own unique feature sets.

    And the way they are being added is not compatible with PyLova’s methods. Which breaks Fediverse compatibility. If any software such as Lemmy were to implement it in the future they would most likely ensure compatibility with the larger userbase PieFed model.

    This is the similar to Microsoft’s “Embrace, extend, and extinguish” philosophy to kill off the competition.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 7 points 15 hours ago (1 child)

    Do you have any context/source for "Rimu's hostile history"? Because I've tried looking into that a few times but I've only ever found this Piefed devlog post which makes Piefed sound reasonable but obviously has every incentive to be biased.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 15 hours ago*

    Why shouldn’t the ideas and features flow both ways?

    why doesn't @rimu@piefed.social admit that he got the ideas from Mia then? why copy changes from PyLova, and strip attribution, then admit to MrKaplan that he did it so that she wouldn't be attributed? moth supposes that perhaps he does not want to admit Piefed is inferior to PyLova.

    Let’s not pretend like PyLova is breaking new ground here, lmao.

    no, but PyLova IS doing most of the dev work for Piefed.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 0 points 11 hours ago (8 children)

    How come pylova isn't publishing these updates here too?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 5 points 10 hours ago (7 children)
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 1 point 10 hours ago (6 children)

    Interesting. Either I scrolled past it or didn't know what it was and ignored it.

    Is there any history on why it was forked? Could be useful to add to the repo.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 6 points 4 hours ago (5 children)

    according to the PyLova devs, it was forked to remove the hard-coded (at that time) censorship in Piefed, especially the anti-memes censor and upvote punishment. memes are a valued and culturally important form of self-expression, and even if the Piefed author is from an older generation, it doesn't mean those memes should have to swim upriver just to get the same engagement on Piefed as they do on Lemmy.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 4 points 4 hours ago (4 children)

    Anti-memes censor and upvote punishment? Is this real? 😂

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 4 points 4 hours ago (2 children)

    yes, although after quite a bit of backlash, he apparently added a switch to turn off most of it. it seems that Rimu does not like memes, judging by the fact he added several functions to suppress them. things like marking meme comms "low quality", making upvotes count less than on other posts, etc. those functions have been removed in PyLova for obvious reasons. memes are fun, and they are culturally relevant to millennials and Gen Z. and while it's true that older generations like Rimu might not appreciate them as much, they shouldn't be quietly punished without telling anyone.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 3 hours ago (1 child)

    Good to know. I guess if I ever sign up to another instance, it'll be a pylova instance, not a piedfed one.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 43 minutes ago

    well having had the pleasure to speak with Mia in Matrix, moth can only highly recommend quokk.au, what one might consider the flagship PyLova instance. she does a terrific job and has surrounded herself with a cadre of very progressive people who genuinely care about the users and their wellbeing.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 17 hours ago (10 children)

    Its a fork isn't it? So like 95℅ of the codes the same.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 9 points 16 hours ago* (6 children)

    The fork split off 7 months ago, PyLova independently added these features weeks and months before PieFed ever did.

    And it has now been confirmed that Rimu has made it non-compatible.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] -1 points 10 hours ago (4 children)

    Maybe it’s because the PyLova maintainers refuse to let their code be contributed back, loosing their shit and accusing Rimu of stealing instead of contributing their code back.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 4 points 5 hours ago

    the PyLova maintainers refuse to let their code be contributed back

    as soon as the fork was made, were the PyLova devs not banned from all Piefed channels? was the first security patch authored by the PyLova devs not ignored by @rimu@piefed.social, despite attempts to reach out so that Piefed could take advantage? tell moth, how long should the PyLova devs continue reaching out, only to have Rimu push them away? why do you have this double-standard?

  • permalink
  • fedilink
  • source
  • parent
  • [–] 7 points 10 hours ago* (2 children)

    Rimu is welcome to bring over PyLova code, he only needs to attribute it instead of deliberately removing the author from the work as he did last time and has been well documented in his conversation with others admitting trying to do.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -3 points 9 hours ago (1 child)

    Did he really though? For the main code including the patch file should have preserved the author for the commit, right? As is shown in the blog post. Honestly that is enough to meet the license requirements. I guess you could argue that he skipped it for the themes, but really? Do you still think that warrants the narrative that they’re stealing code? (Which is a fucking rich statement for a fork to accuse the source project of anyway)

    It would also have been nice to shoutout in the release notes as well, but we never got to see that because of the drama.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 8 points 9 hours ago

    image

    He exported the code as a patch, while not knowing it would make her (correctly) the author. His intention very clearly looks to be as if to use her code without bringing over the authorship. And he did do exactly that later on with copying the themes and renaming it.

    So yes I believe that warrants calling out at the time he did steal the code.

    I am not saying he stole the code here, I am simply saying he is jacking the new features being introduced in an effort to harm PyLova by making it not be able to stand out with unique features. These are really the only big new user facing features he is adding and it's conveniently shortly after we do.

  • permalink
  • fedilink
  • source
  • parent
  • [–] [S] -4 points 11 hours ago* (2 children)

    Yeah that means PyLova copied a lot of features from PieFed lol, that's how forking works.

    It does suck if it's not all compatible though, I hope that gets figured out

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 3 hours ago

    It wouldn't be so bad if Rimu had actually copied the code, which would then be compatible. Or even implement his own code in a compatible way, if attributing PyLova's devs is such a taboo for him. But he chose to implement a non compatible feature, fomenting fragmentation and a worse user experience. And for what?

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 6 hours ago (5 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 6 points 6 hours ago (4 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 0 points 4 hours ago (3 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 4 points 3 hours ago (2 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 34 minutes 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".

  • permalink
  • fedilink
  • source
  • parent
    • [–] 1 point 6 hours ago

    Yay totp

  • permalink
  • fedilink
  • source
    •