this post was submitted on 15 Jun 2023
6 points (100.0% liked)

sh.itjust.works Main Community

7584 readers
3 users here now

Home of the sh.itjust.works instance.

Matrix

founded 1 year ago
MODERATORS
6
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

Final edit: Has nothing to do with specific terms used, this person is correct. Language setting related problem. https://sh.itjust.works/comment/173272

First Edit: Damn, seems to be working fine now. Wonder if it was community-level wherever I tried to post (don't know if language filters can be implemented at that level. Can't remember what I tried to reply to), or if TheDude is updating some stuff and I happened to post at just the wrong time? Or maybe it was a post from another instance?

Second edit: Ahhh, interesting. So it was a reply to https://kbin.social/m/[email protected]/p/435069. And the offending word at least seems to be 'Beehaw'. Anyone have any insight re: what's happening here for a mostly Lemmy illiterate sh.it.head?

Original comment:

Just had a weird experience trying to reply to a post. Is there a language filter now? I used a very soft cuss often spoken in normal discourse (starts with a d, ends with an n, 4 letters) and got an error.

Is someone able to explain the rationale? Maybe it's just me but casual cussing is a) pretty much my default mode, and b) from the outside doesn't seem like a real problem that needs to be addressed. People cuss on the internet. Now, personally not opposed to a filter for clearly derogatory terms (you know what they are, don't @ me), but my recent experience seems a little extreme.

you are viewing a single comment's thread
view the rest of the comments