Salta al contenuto
Citiverse è uno spazio aperto a tutte le comunità. Se vuoi aprire un gruppo locale o una sezione per la tua organizzazione, puoi contattare gli amministratori: pagina dei contatti.

PieFed v1.9 is released - Shared Blocklists, Auto-bans and TOTP

Fediverse
184 37 7
  • 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 the project have any original ideas?

    scritto ultima modifica di
    #41

    Probably cause Pylova is vibe coded slop

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

    scritto ultima modifica di
    #42

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

  • These are only being added straight after PyLova does it, 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 ensures they are not compatible with PyLova’s methods. Which breaks Fediverse compatibility, and if any future 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.

    scritto ultima modifica di
    #43

    And the way they are being added is not compatible with PyLova’s methods.

    Hey, I'm not familiar with either implementation - how does PyLova do it? And how does PieFed do it?

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

    scritto ultima modifica di
    #44

    People complaining about shared blocklists and autobans don't really get the philosophy of PieFed. It's clearly very opinionated on particular moderation practices that many other people would consider questionable. That's fine, that's the devs prerogative. If you like it, use PieFed, if you don't, don't.

    The thing about PieFed now making equivalent features that are seemingly intentionally incompatible with the PyLova fork though... that seems suspiciously deliberate to break federation between the platforms. This goes against the entire fediverse idea. That is what I would question more (though I don't know the details of the incompatibility).

  • 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".

    scritto ultima modifica di
    #45

    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.

  • Probably cause Pylova is vibe coded slop

    scritto ultima modifica di
    #46

    piefed is too🙃.

  • People complaining about shared blocklists and autobans don't really get the philosophy of PieFed. It's clearly very opinionated on particular moderation practices that many other people would consider questionable. That's fine, that's the devs prerogative. If you like it, use PieFed, if you don't, don't.

    The thing about PieFed now making equivalent features that are seemingly intentionally incompatible with the PyLova fork though... that seems suspiciously deliberate to break federation between the platforms. This goes against the entire fediverse idea. That is what I would question more (though I don't know the details of the incompatibility).

    scritto ultima modifica di rimu@piefed.social
    #47

    I can't work with or communicate with the PyLova people. I have too much trauma from the bullying campaign they continue to operate.

    I'm giving away code. It's a gift. Giving that gift does not put me under any obligations including talking with anyone else, especially not with groups which attack me and disparage me whenever they can.

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

    scritto ultima modifica di
    #48

    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.

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

    scritto ultima modifica di
    #49

    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.

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

    scritto ultima modifica di
    #50

    deliberately breaking compatibility

    Source?

  • 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?

    scritto ultima modifica di
    #51

    We really need general purpose lists that can be either block or follow. That way everyone can use the same furry list and be happy.

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

    scritto ultima modifica di
    #52

    We are so small haha. Its so silly.

  • piefed is too🙃.

    scritto ultima modifica di mesamunefire@piefed.social
    #53

    ...what? No its not...https://codeberg.org/rimu/pyfedi/commits/branch/main its all people. real people.

    Plus the code is not in the style AI usually does python.

  • We really need general purpose lists that can be either block or follow. That way everyone can use the same furry list and be happy.

    scritto ultima modifica di
    #54

    I like where your head is at

  • deliberately breaking compatibility

    Source?

    scritto ultima modifica di awesomelowlander@cozyver.se
    #55

    {
    "@context": "...",
    "id": "https://example.org/blocklist/general",
    "type": "OrderedCollection",
    "name": "General Blocklist",
    "summary": "Description of the list",
    "attributedTo": "https://example.org/u/admin",
    "published": "...",
    "updated": "...",
    "totalItems": 2,
    "first": "https://example.org/blocklist/general/entries?page=1",
    "inbox": "https://example.org/inbox",
    "visibility": "public",
    "subscriberCount": 10
    }

    The feature is nothing more than shared basic JSON data. If your thrust is that Rimu is too incompetent to handle that, I don't really think so, but I can accept that too.

  • People complaining about shared blocklists and autobans don't really get the philosophy of PieFed. It's clearly very opinionated on particular moderation practices that many other people would consider questionable. That's fine, that's the devs prerogative. If you like it, use PieFed, if you don't, don't.

    The thing about PieFed now making equivalent features that are seemingly intentionally incompatible with the PyLova fork though... that seems suspiciously deliberate to break federation between the platforms. This goes against the entire fediverse idea. That is what I would question more (though I don't know the details of the incompatibility).

    scritto ultima modifica di
    #56

    People are pointing out the flawed philosophy of piefed. It's explicitly designed with a singular person's vision.

    The issue is people are happy to ignore that completely and would rather attack those pointing it out than admit the issue.

    Then there's the piefed dev acting like the victim for their own terrible decisions and attacks on others.

    I can't interact with them because they call me out on my bullshit

  • I can't work with or communicate with the PyLova people. I have too much trauma from the bullying campaign they continue to operate.

    I'm giving away code. It's a gift. Giving that gift does not put me under any obligations including talking with anyone else, especially not with groups which attack me and disparage me whenever they can.

    scritto ultima modifica di
    #57
    1. Harassment, Hate Speech, and Discrimination

    Isn't that your first rule? Yet your here doing exactly that while still attacking them?

    I can't work with or communicate with the PyLova people. I have too much trauma from the bullying campaign they continue to operate.

    Which is incompatible from what was said by you in just August

    Verdict?

    Perhaps I was clumsy and ham-handed with my work in this situation? Perhaps I didn’t follow social conventions about how FOSS projects are supposed to work together? I hope my corrective action was enough. What do you think?

    Regardless, I am sorry for any problems I caused for the Pylova project and will not be doing that again. I wish them well with their fork.

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

    scritto ultima modifica di
    #58

    That is exactly what rimu wants so 🤷

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

    scritto ultima modifica di
    #59

    Rimu is here making it worse fyi

  • deliberately breaking compatibility

    Source?

    scritto ultima modifica di
    #60

    You won't acknowledge it but for everyone else here's rimu saying well it's just unfortunate and their fault totally nothing I did


Citiverse è un progetto che si basa su NodeBB ed è federato! | Categorie federate | Chat | 📱 Installa web app o APK | 🧡 Donazioni | Privacy Policy

Il server utilizzato è quello di Webdock, in Danimarca. Se volete provarlo potete ottenere il 20% di sconto con questo link e noi riceveremo un aiuto sotto forma di credito da usare proprio per mantenere Citiverse.