Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)A

anarchiddy

@ anarchiddy @lemmy.dbzer0.com

Posts
2
Comments
735
Joined
1 yr. ago

  • The Actual Gavin Newsom Is Much Worse Than You Think

    Jump

  • Gavin Newsom has a greater chance of losing to Vance and almost any other democratic candidate.

    Libs need to stop falling for the 'leftists want trump to win, see look they wont commit to voting for the Democrats' shtick. They just want to discredit the part of the base that's trying to actually save the party.

  • Locked

    feddit.org's Zionist bar problem: community ban(s) vote

    Jump

  • Im not usually a fan of defederating over differences in moderation. Frankly, I dont pay attention to their communities because they're the next most libbed instance next to .world or piefed.

    I guess im alright with it if that's where the vote takes us, but I honestly dont find them threatening. They've backed themselves into a corner by hitching their wagon to Israel, and i think they're so outnumbered here that they've basically ostracized themselves anyway.

  • Real Nazis

    Jump

  • The democratic system gave up on serving the disenfranchised long before the disenfranchised gave up on the democratic system.

    If you want to be angry, be angry at those protecting the system from change, not the people who have given up hope that it can be changed.

    Be kind to people, be ruthless to systems.

  • Not good for business

    Jump

  • Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)

    Jump

  • Have Lemmy mods approached Rimu at all?

    He chose to fork his own code rather than work with them - I think the better question is why he hasnt vetted his changes with the existing codebase better, or why he cant be bothered.

  • Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)

    Jump

  • It is what it is. Mbin also existed before Piefed.

    Mbin isn't nearly as egregious as piefed in the way they introduce breaking changes to the network.

    You’re assuming some hand has been offered that has been slapped away by Rimu

    I'm not assuming anything, it's been stated repeatedly. Rimu could implement his preferred features in ways that don't degrade the health of the network but chooses not to.

    you know as well as I do three instances of note are heavy defederated (hilariouschaos being the third incase you were wondering)

    I'm not sure what relevance that has, but you can count those instances on a hand missing two fingers (i'd note that dbzer0 does not defederate from 2 of the three that I assume you're referring to, nor would I advocate for it). It would be interesting for someone to map out just how much of the fediverse is effectively being defederated for piefed servers with large user block lists - i imagine it's quite a large chunk, especially when the most popular users to block are the ones producing the most activity. The larger those servers grow, the bigger those holes will become.

  • Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)

    Jump

  • If a hypothetical lemmy-alternative existed, regardless of why, it could still cause disruption in all kinds of ways if there’s a fundamental design contradiction ethos

    Which is why it's important for users to reject attempts at splitting the network into different codebases in the firstplace.

    That piefed and many of its users reject working with lemmy devs on principle over political grievance doesn't change or justify the fact that they are destroying the democratic nature of the federated network they're taking advantage of.

    This doesn’t bother me that much primarily because defederation differences can cause this anyway

    Which is why defederation is a last resort and usually requires some democratic discussion as an instance. Same with instance-banning users - that ability is limited to admins, which means users can hold them accountable if there's abuse. It's a reason why i consider users who go out of their way to foment division against other instances or users over petty disagreements to be caustic and unwelcome, but are at least still working within a decentralized and democratic framework. When any user has the ability to create the same kind of holes in the network, all accountability vanishes and it starts to look like swiss-cheese.

  • Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)

    Jump

  • How could Piefed make this disparity of blocking philosophy mesh with Lemmys here?

    Without forcing every server to adopt the same blocking system universally? It can't. What it's doing now is functionally no different than if they hid replies on the user front end for users blocking others outside the home instance, except instead of doing this non-destructively (and preserving data pairety across instances), they've decided to blow huge holes in the federation service that are no longer mirrored on the other instances.

    If the piefed method of handling blocking is to make it impossible for all users in every instance incapable of replying to a user who has blocked them, then every server would need to adopt the same method universally. Piefed has every right to hide content from their users that their users have chosen to block, but doing so by rejecting that content for the whole server while the rest of the network carries on ends up creating shadow forums on every instance.

    rimu may still have made his own reddit clone or someone else may have - which would handle things very differently

    That would be preferable to the 'embrace, extend, extinguish' path that they are currently on.

  • Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)

    Jump

  • It doesn’t. On Piefed [...] But Lemmy obviously doesn’t work like that.

    Yes, that's exactly what i'm pointing to. Rather than implementing this in a way that's non-destructive and transparent, they've created an asymmetry by dropping comments entirely. They could render comments based on block-checks and not create this problem, but instead they chose to say 'fuck the lemmy instances' and create hundreds of holes in the federated activity out of seemingly nothing but spite.

    What do you mean “made clear”? Has Piefed refused help or support from other developers?

    Not "other developers" generally, "the other developers". I'm speaking specifically of the already existing lemmy codebase. Piefed was created as an alternative to lemmy - at least in part - because of disagreements over the developer's political views. It wasn't because lemmy was poorly written, it was because a couple of developers decided they wanted to fork the project into their own that they could manage independently from lemmy.

  • Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)

    Jump

  • Yea, see this is what I mean by 'petty vindictive development'.

    None of this speaks well of the project and risks undermining the entire federated network.

  • Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)

    Jump

  • The Piefed system of blocking is more aligned with how most other sites do blocking

    I don't know any other site that allows blocked users to reply to the blocking user but deletes the reply on the backend server for everyone on it.

    But regardless - that decision was made unilaterally by piefed and corrupts the federation of the rest of the network. Huge holes of mis-matched comment threads are being created everywhere because piefed chose to implement a destructive blocking system rather than a front-end filter, or by working with the other implementations on a solution that doesn't misalign data across the network.

    I understand that you agree with how piefed restricts certain content - my point is that the way piefed has implemented those features corrupts the integrity of the entire network. They've made it clear that they have no interest in collaborating with the other developers, even if it means creating incompatibilities between the integrations to the point of functional defederation.

    "Move fast and break stuff" isn't something anyone should be aspiring to.

  • Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)

    Jump

  • I'm not collaborating with a developer who has it out for the platform I'm working to improve. If he wants to fix the shit he broke, he can.

  • Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)

    Jump

  • That's admin and community dependent - an admin or community can take that reputation metric and use it to automate moderation. There is/was an entire community whose whole gimmick was auto-banning users from every instance for activity across the entire federated network. But beyond that, piefed already drops content instance-wide for as little as a single user blocking another.

    if parent_comment.author.has_blocked_user(user.id) or parent_comment.author.has_blocked_instance(user.instance_id): log_incoming_ap(id, APLOG_CREATE, APLOG_FAILURE, saved_json, 'Parent comment author blocked replier') return None

    The codebase is riddled with shit like this.

  • Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)

    Jump

  • I mean, I disagree, but that's my own preference.

    Ranking/sorting/filtering systems should always be up-front and user-configurable, and their implementation should be instance-agnostic. Hiding it in the code is definitely the worst part of this, but far from the only problem.

  • Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)

    Jump

  • Is there any indication to users interacting with those instances that their content is being limited by metrics that may or may not be visible to them, and by rules that may or may not be documented anywhere but the piefed codebase?

    These are wildly hostile features to anyone not using piefed, and it's feeling a bit like that's the point.

  • Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)

    Jump

  • There's nothing in the code that I can see that indicates that any of the penalties are undone by turning off the filter - but that's kind of the point. They've introduced a new metric that thumbs the scale of content visibility that's hard-coded and inscrutable to everyone but those with knowledge of the codebase, and that makes the entire project and the devs who made those choices un-trustable.

    Is there a version of their reputation system that's less objectionable? Sure. But it would need to be exceedingly transparent with clear documentation on how to configure, alter, and revert if there's a mistake made. But there's nothing here that indicates the devs of piefed are willing or capable of transparency or even just clear documentation.

  • Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)

    Jump

  • This is like hiding changes in a 500 page TOS - is everyone who is impacted by this code going to know to look at this thread any time a new way of fucking with user reputation calcs is introduced?

    Absolutely not.

  • Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)

    Jump

  • That isn't true - the comment filters also dock users reputation points, and without any notification to users that it's happening.

    None of this is presented to users - that's the definition of opaque. They've shoehorned these features into their code without any notice to other users or instance admins, and have provided no way of notifying anyone of what is happening on the backside that might effect how content is handled or federated.

    All of this irreparably injures the reputation of not just the piefed implementation but of the broader fediverse.

  • Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)

    Jump

  • It's one thing to empower admins with mod tools, it's another to establish reputation ratings based on opaque rules, hide them behind fake error messages, and then enforce them using destructive workarounds that cause nothing but confusion to users and other federated server admins.

    Go ahead, be restrictive with who can participate on your server - that's perfectly fine. But be transparent about how your moderation tools work and don't hide punitive ranking systems in your codebase.

    It certainly makes it seem like the devs have an axe to grind, and don't care how their careless decisions effect the rest of the network.