@realcaseyrollins @LemmyDev @FediFollows @icedquinn the slur filter was originally implemented so recklessly that if a substring matched the regex, the UI would hard & fast refuse to accept the whole composition with no specific error, and so users were forced to throw away a potentially long (labor intensive) msg in a way that was blind to the mods & ownership, so the problem wasn't even trackable.

@icedquinn @FediFollows @LemmyDev @realcaseyrollins Lemmy evolved from that but this is not just a coding botch.. it reflects reckless disregard for colatteral damage to legitimate users who have no malicious or nefarious intent or effect. #Lemmy devs & lemmy.ml are tyrants in both their design and especially in their management style. Indeed we need to avoid tyranny, thus different devs, which hopefully #Lenny will satisfy.

@realcaseyrollins @LemmyDev @FediFollows @icedquinn Lenny can't likely solve this problem though: #Lemmy is hard-coded to require client-side javascript to the point that text of posts is entirely unreachable w/out it. This ruins the use of archive.org, so if a node goes down or if becomes CloudFlared access to content can be lost forever. And if a moderator abuses their power to censor, archive.org is blocked from showing the abuse.


@aktivismoEstasMiaLuo @realcaseyrollins@counter.fedi.live @LemmyDev @FediFollows@mastodon.online@icedquinn@blob.cat Blatantly untrue now: web.archive.org/web/2021012818

· · Web · 0 · 0 · 0
Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!