Lemmy.ml famously limits your ability to upvote, comment, or post, and bans accounts that they hate, all while lying about the reasons why (the rules make no mention about saying anything critical about Russia, China, or North Korea, though it’s exceedingly obvious what is going on there).
Dumb mod actions != Baked into the code of software, that you have to remove.
I know shouldn’t expect much from someone who has continuously been proven wrong and kept spreading misinformation because learning facts is hard.
But Jesus Christ, the actions of moderatiors being stupid for Russia/China because they think it’s revolutionary as they jerk off all day, is not the same as the software being opiniated because he dev doesn’t know what he’s doing.
Talking about baking ideology into the code, the Lemmy devs previously HARD-CODED an English slur word filter. Nutomic said in response:
If you dont like it, fork it. Stop bothering us about it, we will never fully remove the slur filter.
This sounds fairly opinionated to me. Fortunately after a HUGE outcry, they did later relent.
Rimu did not have to go to all the trouble of making the vote quota into an environmental variable, easily changed without needing to modify the code (even when running PieFed from a docker container), but he did. Note I am not even defending him here, simply stating facts.
My opinion - shared by most programmers I presume - is that the ideal in both situations would have been to use an opt-in feature, rather than make it opt-out or far worse, HARD-CODE it directly in. Also, it would be nice to announce such things rather than leave people to stumble upon them.
Fwiw, people have previously reported that PieFed hard-codes other matters as well, but this was shown to be misinformation caused by merely looking at lines of code in isolation without bothering to figure out how the code actually works - in particular how those lines are never actually run without particular settings having been turned on.
IF (setting) THEN (feature)
Is NOT the same as hard-coding a feature!!
Also, Lemmy refuses to so much as notify people when their content is removed - overall its set of features is heaviest on giving power to admins, less so to mods, and least of all to the end-users. In contrast, PieFed offers tons of power to users, for instance at least bothering to tell them when their content gets removed by a mod (but ironically not when the voting quota is exceeded, reputedly).
BOTH softwares are fairly opinionated. Lemmy has historically been far more so. Lately it has calmed down and it is PieFed making the waves instead - some of it unfairly, and some of it well-deserved.
Do you really want to vote more than 240 times per day? That’s one vote per minute for four hours straight - only the terminally online would ever want to do such a thing.
I was not discussing the content of slurs, but the process of HARD-CODING them into the software (especially only in English). Elsewhere PugJesus gives a fairly great explanation as to why a slur filter is not a great idea though - e.g. those people should be banned, not merely filtered, but not by an automated procedure and rather by a human being who can judge nuance.
Dumb mod actions != Baked into the code of software, that you have to remove.
I know shouldn’t expect much from someone who has continuously been proven wrong and kept spreading misinformation because learning facts is hard.
But Jesus Christ, the actions of moderatiors being stupid for Russia/China because they think it’s revolutionary as they jerk off all day, is not the same as the software being opiniated because he dev doesn’t know what he’s doing.
Talking about baking ideology into the code, the Lemmy devs previously HARD-CODED an English slur word filter. Nutomic said in response:
This sounds fairly opinionated to me. Fortunately after a HUGE outcry, they did later relent.
Rimu did not have to go to all the trouble of making the vote quota into an environmental variable, easily changed without needing to modify the code (even when running PieFed from a docker container), but he did. Note I am not even defending him here, simply stating facts.
My opinion - shared by most programmers I presume - is that the ideal in both situations would have been to use an opt-in feature, rather than make it opt-out or far worse, HARD-CODE it directly in. Also, it would be nice to announce such things rather than leave people to stumble upon them.
Fwiw, people have previously reported that PieFed hard-codes other matters as well, but this was shown to be misinformation caused by merely looking at lines of code in isolation without bothering to figure out how the code actually works - in particular how those lines are never actually run without particular settings having been turned on.
IF (setting)THEN (feature)Is NOT the same as hard-coding a feature!!
Also, Lemmy refuses to so much as notify people when their content is removed - overall its set of features is heaviest on giving power to admins, less so to mods, and least of all to the end-users. In contrast, PieFed offers tons of power to users, for instance at least bothering to tell them when their content gets removed by a mod (but ironically not when the voting quota is exceeded, reputedly).
BOTH softwares are fairly opinionated. Lemmy has historically been far more so. Lately it has calmed down and it is PieFed making the waves instead - some of it unfairly, and some of it well-deserved.
You really wanna say slurs? That’s your biggest issue? You weren’t allowed to call people slurs?
That tracks for people who hate lemmy’s software. “They didn’t let me be racist! And then they removed it!”
Do you really want to vote more than 240 times per day? That’s one vote per minute for four hours straight - only the terminally online would ever want to do such a thing.
I was not discussing the content of slurs, but the process of HARD-CODING them into the software (especially only in English). Elsewhere PugJesus gives a fairly great explanation as to why a slur filter is not a great idea though - e.g. those people should be banned, not merely filtered, but not by an automated procedure and rather by a human being who can judge nuance.