The code is open source. Nothing is obscured.

“Security-by-obscurity” is a phrase used for any measure that is useless once you know how it works. In this case it’s hoping that a troll doesn’t know about the specific hardcoded rules. None of the rules in PieFed actually work if you are at all aware of them.

Thanks for clarifying, I guess I misremembered the shadowbanning part. I think I was mixing together the fact that reputation isn’t really transparent (users’ reputation can change by even attempting to upload an image that gets flagged, and the vague error means they’ll probably try multiple times without realizing they’re being moderated) and the fact the communities can autoban any user whose global reputation is low enough.

I still think the security-by-obscurity approach to moderation is inherently flawed though, and I hate to imagine how the dev approaches actual account security if that’s their approach to moderation.

Honestly I would consider [user-obscured] hardcoded shadowbanning just as bad.

Just because I’m closer to agreeing with the PieFed dev’s opinions a little bit more doesn’t mean that I’d support shadowbanning someone because the trivially-evaded checks caught a false positive in the crossfire. Piefed’s auto moderation/social scoring is pretty much textbook definition security-by-obscurity. The second anyone knows how it works, it’s useless. It will pretty much exclusively catch people who just wanted to post a harmless meme or something.

At least (for now) Dessalines isn’t hardcoding his tankie beliefs into Lemmy’s source code.

Edit: Blaze is right, it isn’t shadowbanning, but the rest of my point still stands, added the [] part to clarify

There were a few, not exaustive since it’s been a few months since I looked through the source code, some of this might have changed and there’s also a few other checks that I’m forgetting:

• 4chan screenshots (specifically anything that OCR identified as having “Anonymous #(number)” in it) were banned. Honestly this one is fine as a toggle but I think for a while it was just on by default in the code
• any community that had specific words in it were blocked at instance level. I think “meme” was there, a few swear words, and a few carryover reddit meme community names (196, I think nottheonion was also there, anything with “shitpost” in the name, etc.)
• There’s a hidden karma/social credit score based on a user’s interactions and net total karma hidden from them that gets impacted by any moderation actions, including some of the automated hardcoded ones (e.g. even trying to upload an image that gets flagged by the hardcoded checks). In some cases the user is not informed of any of these changes (the image upload will appear as a generic image upload error)
• users with a low enough net score can be automoderated at both a community and instance level

Edit: the other thing is, a lot of this hardcoded moderation isn’t documented anywhere outside of the code, likely because a lot of the measures would be useless if people knew how they worked

Edit 2: updated based on Blaze’s reply from another comment, I misremembered the shadow banning, I was confusing it with the federation errors that occur when one user blocks another

Tbf Piefed also does have opinionated moderation literally hardcoded into the source code.

It’s pretty easy to modify since it’s python and not rust, but still not great

Gender-wise, women tended to make small interjections, nod their heads, etc, as the conversation went among, to indicate that they were listening

Wait this isn’t something everyone does?

Not sure about link click but To Be Hero X was co-produced between a Japanese anime studio (I forget which one) and Bilibili. The source material is game franchise, so the line is definitely blurry there. But since Cyberpunk Edgerunners generally counts as anime despite being published by an American company and based on a Polish game, I’d say these can fall under the umbrella also.

To be hero X is another really good Chinese one

Worth noting that Linux Mint Debian Edition exists and is based directly on Debian instead of Ubuntu. They starting publishing it specifically because the Linux Mint team doesn’t like the direction Ubuntu is heading in with snaps. Not sure how good it is as I haven’t tried it in a while (and don’t really use regular mint either).

The joke in the meme is John Cena laughing at JKR being in the Epstein files, though. That’s not a joke, it’s disinformation.

But JKR is objectively “in the Epstein files.” It’s not clear whether she was directly or intentionally involved, but her name is absolutely present in the files. This meme isn’t misinformation at all.

Honestly I’d consider using this in combination with NixOS just for the flatpak support

Xlibre is backed for the most part by the singular maintainer that was still willing to work on X11 who got kicked out for being too toxic and breaking existing code. For what it’s worth, it also explicitly used MAGA language in its README for a while.

Phoenix is intended to allow for support of legacy software/DEs and provide a more modern/maintainable version of X11. It isn’t trying to compete with Wayland, it’s trying to live alongside it for environments that won’t or can’t move to Wayland. It also technically won’t be a complete X11 implementation, as it’s ignoring older portions of the protocol.

Neither option addresses the elephant in the room: The X11 protocol is still fundamentally broken in a lot of aspects. Multi-monitor support, especially when monitors aren’t the same resolution, refresh rate, or physical size, is broken at a fundamental level. It will never work even as well as Windows, which is already an incredibly low bar to clear.

Wayland is slow moving, sure, but it is a much more stable base to work with than Xorg ever was. From a security, modularity, and extensibility standpoint, Wayland is a lot better. There is a reason most of the Xorg team developed a completely new protocol instead of just reimplementing X11 themselves.

It can be hit or miss, really depends on the bank. I’m in the US and mine worked fine after I enabled a compatibility setting in the app list, but that’s kind of anecdotal. I think there is a community compatibility list somewhere of banking apps that work/don’t work on GrapheneOS.

If you were able to install Bazzite then installing graphene shouldn’t be any harder than that. It has a web-based installer that was pretty easy to use as long as you follow the instructions.

The pixel 8 will be supported through the end of 2030 (graphene support follows the same timeline as Google because of firmware-level updates that are still needed from them) so you could still get a lot of use out of it.

GrapheneOS my beloved

It’s a kernel compile parameter but most Linux distros have it turned off by default 😔

The only time I’ve ever seen it turned on was on my raspberry pi

I don’t love the way niri handles workspaces across multiple monitors so far but my problems with it are also minor enough that I’m pretty sure I can fix it myself with a script or IPC program if it really starts to bother me

I hate to break it to you but Mario Odyssey is 8 years old and RDR2 is 7 years old. Those definitely don’t qualify as “now” games on a timeline. Elden Ring gets a pass because of the DLC but it’s also 4 years old.

That being said, there are plenty of good games that came out this year. Most of them aren’t AAA though.

I couldn’t have picked better timing to switch to niri if I tried.

I misread it, seems like it’s just the Omarchy theming system it has integration with. My point mostly still stands though, going out of the way to support Omarchy’s system is still a red flag.

For those unfamiliar, the creator of omarchy is a pretty open white supremacist and transphobe among many other things. This blog post does a pretty good job of outlining everything:

https://davidcel.is/articles/rails-needs-new-governance (He also created Ruby on Rails, hence the article title, the focus of the article is mostly on that but it gives a detailed background on DHH as well)