Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)
-
It's as if someone saw a federated social media codebase that enabled the free movement of users and expression online and though, "someone should fix that".
It isnt that the codebase 'forces' moderation decisions - it's that it's undoing the work done in the lemmy codebase to flatten moderation across instances and make them transparent, and introducing arbitrary metrics that can be used to limit the visibility of expression not just on the local instance but across many
You're free to use whatever software on your server you like, but IMO these 'filters' are petty, low-effort workarounds to features in the lemmy codebase that are what make it truely democraticand decentralized, and they degrade the health of the entire federated network by extension.
Tolerating intolerance doesn't make a community more tolerant. We need good mod tools to remove authoritarians from our communities.
I really want a Xitter filter so I can prevent screenshots from the Nazi website from showing up on our website. Because I think Xitter is worse than 4chan.
-
Well, just copy and pasted rather than written. I would have hoped that infra read-level permission, infra write-level permission and admin interface permissions were all separate to begin with, even if the person who spun up the instance obviously has all three.
You do need a level of trust in an admin, of course, but wide open text boxes for putting in code are a questionable system design choice, in my opinion. It adds an extra point of possible entry that then relies on the security of the overall admin interface instead of limiting it to what should require highest level infra admin permissions to access. And if it is something that would be limited to someone who has those, then what is the actual utility of having a textarea for it in the first place?
Oh, I love it. So much freedom to customise our instance without having to rebuild the Docker image or fork the codebase.
-
Booo. Here I was hoping for something serious to spice up the news and it just turns out it's "it runs on a browser".
Sorry, pal. It's a good software.
-
-
Booo. Here I was hoping for something serious to spice up the news and it just turns out it's "it runs on a browser".
I'm not a spice merchant, and most exploits rarely involve a single step. This screenshot is just a system design red flag.
You're free to examine the repo yourself and find your own spice, my 5 min look tells me that piefed needs to expend a significant amount of effort on infosec to maintain user trust in the longer term.
-
Clean, simple code that is easy to understand and contribute to
The problem with grabbing small snippets of code is a lot of context is lost. Don't trust anyone who does that. PieFed has 50,000 lines of code so anyone showing you 50 lines is leaving out 99.9% of the picture.
These 2 statements are incompatible.
Plus depending on the snippets they definitely can tell how things work
Previous threads about these filters were people complaining about them being hardcoded, completely ignoring that they are completely optional and off by default. It would go something like this:
Look at this awful thing PieFed does!
def do_the_thing(): # relatively simple code that does the thing
It completely ignored the context that the
do_the_thingfunction is only called if the admin wants to do the thing. -
Oh, I love it. So much freedom to customise our instance without having to rebuild the Docker image or fork the codebase.
Out of curiosity, what sort of customizations are you doing with it? I'm just a bit surprised that docker rebuild or a non-trivial fork would be needed, so I'm assuming they're pretty big changes.
-
Edit about the 4chan image blocking, I asked Rimu directly:
I wrote a long message about how that checkbox only notifies about federated posts.
So the difference is for local posts it blocks the creation of the post entirely, but for federated posts it just notifies the admin.
https://chat.piefed.social/#narrow/channel/3-general/topic//near/10529
--
Original message:A few people in the other thread assumed that it was required to fork the code to disable those filters. That's not the case, the filters can be configured, and are off by default.
To hide the reputation system, here's a line of CSS that admins can add in the admin area to hide it for every user
That CSS line can also be used by any user wanting to hide the score at the user level.
I'm in, anything with less Tankies and less channers is good.
What's the best instance to use, I assume I can keep my current user and just view posts via piefed.social
-
I'm in, anything with less Tankies and less channers is good.
What's the best instance to use, I assume I can keep my current user and just view posts via piefed.social
Well if you specifically want less 4chan adjacent content, piefed.social.
-
Out of curiosity, what sort of customizations are you doing with it? I'm just a bit surprised that docker rebuild or a non-trivial fork would be needed, so I'm assuming they're pretty big changes.
So far I've only changed the colour theming, but I like freedom in general. One thing I want to do at some point is change the font of any instance of the string MULTIVERSE, My partner suggested it as a cool branding idea
-
Clean, simple code that is easy to understand and contribute to
The problem with grabbing small snippets of code is a lot of context is lost. Don't trust anyone who does that. PieFed has 50,000 lines of code so anyone showing you 50 lines is leaving out 99.9% of the picture.
These 2 statements are incompatible.
Plus depending on the snippets they definitely can tell how things work
Simple != few lines of code, nothing incompatible about those two statements
-
There's never going to be parity of administration philosophies across all instances regardless of tools. Some will use word filters. Some will hold very strong opinions on 4chan culture. Some will block new community creation for members. Some will force account age limits to interact on locally hosted communities (i've seen this in the modlog).
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.
-
Out of curiosity, what sort of customizations are you doing with it? I'm just a bit surprised that docker rebuild or a non-trivial fork would be needed, so I'm assuming they're pretty big changes.
Some instances have used it to do something like a dynamic message of the day. That is the most I have seen it used for so far.
Edit: See the top of the main content pane of anarchist.nexus as an example.
-
just wanted to show you this post, for piefed.blahaj.zone
-
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.
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.
The reputation ratings of users are purely based on downvotes received, it's not really opaque.
The 4chan thing again, can be turned off.
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.
The reputation/attitude system is not concealed at all.
-
just wanted to show you this post, for piefed.blahaj.zone
These have been our settings pretty much since we set up pbz
-
Those checkboxes have been there since version 0.9. Ages.
The problem with grabbing small snippets of code is a lot of context is lost. Don't trust anyone who does that. PieFed has 50,000 lines of code so anyone showing you 50 lines is leaving out 99.9% of the picture.
As I said a month ago, anyone with honest questions about how things work who wants to make PieFed better knows where to find us. You don't have to be a coder, we need translators, designers, documentation writers, bug reporters, community evangelists and all that.
get back to work hardcoding censorship and pushing your tankie ideology in your code.
What is wrong with you? Why would you put malicious code into piefed that deliberately misleads users?
-
Those checkboxes have been there since version 0.9. Ages.
The problem with grabbing small snippets of code is a lot of context is lost. Don't trust anyone who does that. PieFed has 50,000 lines of code so anyone showing you 50 lines is leaving out 99.9% of the picture.
As I said a month ago, anyone with honest questions about how things work who wants to make PieFed better knows where to find us. You don't have to be a coder, we need translators, designers, documentation writers, bug reporters, community evangelists and all that.
The problem with grabbing small snippets of code is a lot of context is lost.
To me, it was obvious that these parts were configurable. There were literally boolean checks for it.
But these features remind me Reddit. And I'm pretty sure most users simply unaware about these things enabled on the .social instance.
-
Edit about the 4chan image blocking, I asked Rimu directly:
I wrote a long message about how that checkbox only notifies about federated posts.
So the difference is for local posts it blocks the creation of the post entirely, but for federated posts it just notifies the admin.
https://chat.piefed.social/#narrow/channel/3-general/topic//near/10529
--
Original message:A few people in the other thread assumed that it was required to fork the code to disable those filters. That's not the case, the filters can be configured, and are off by default.
To hide the reputation system, here's a line of CSS that admins can add in the admin area to hide it for every user
That CSS line can also be used by any user wanting to hide the score at the user level.
Link to the comment for more context: https://lemmy.ml/post/42339089/23619001
-
Edit about the 4chan image blocking, I asked Rimu directly:
I wrote a long message about how that checkbox only notifies about federated posts.
So the difference is for local posts it blocks the creation of the post entirely, but for federated posts it just notifies the admin.
https://chat.piefed.social/#narrow/channel/3-general/topic//near/10529
--
Original message:A few people in the other thread assumed that it was required to fork the code to disable those filters. That's not the case, the filters can be configured, and are off by default.
To hide the reputation system, here's a line of CSS that admins can add in the admin area to hide it for every user
That CSS line can also be used by any user wanting to hide the score at the user level.
Is there anyway for users to know which piefed instances have this and the other censorship settings enabled? I was trying to upload an image the other day and kept getting an error and now i realize it was because of the code itself?!
Like why the fuck wouldn't it tell me that image isn't allowed instead of giving me an error
