wefwef is now Voyager! Subscribe to [email protected].
I get this error when trying to reply on kbin on communities hosted on Lemmy.world. I don’t know whether this is a wefwef problem or if it’s just the messenger to a problem with Lemmy world. For the record I do have a language set in my profile
I get the same I’m on lemmy.ca. In my profile settings I chose French , English and Undetermined because there’s a note saying if that’s not picked then you can’t see most posts.
Same issue here, and I do have language set (French, English, and Undefined).
+1
In my case I wat trying to comment under another user's comment, but to the post itself. On kbin.social . Tried all possible methods: wefwef, Connect, Thunder, Liftoff, Summit, Firefox browser, and all failed. Edit: by the way, this comment doesn't show up on my user profile. Edit2: It shows up after my 1st edit. 😐
I'm pretty sure this happens because kbin automatically defines the language of my comment as English, and lemmy is set to only allow responses to comments in the language of the parent comment. (or so I've read)
I don't think I can mark the language of my comment as undefined either...
I'm not 100% sure this is why though.
Test with language set as English from Kbin.
It’s related to the language of the parent comment. I’ve found Kbin comments are showing as Undetermined on Lemmy, despite having a language set on Kbin.
When replying to an Undetermined language comment, Lemmy seems to try to use the same language and generates an error (although the error is silent in a browser rather than API/app).
A work around is to reply to the comment directly on your Lemmy’s instance via a web browser (not in Voyager), and selecting a language other than Undermined on your comment.
The issue is with Lemmy rather than Voyager, but Voyager are tracking the issue here.
I'm having this problem on other apps on android also
I saw this and error on one thread when trying to reply to a specific person. When I made a comment that wasn't a reply to a specific person, there wasn't an issue.