this post was submitted on 27 Jul 2023
29 points (100.0% liked)

Voyager

5673 readers
9 users here now

The official lemmy community for Voyager, an open source, mobile-first client for lemmy.

Download on App Store

Download on Play Store

Use as a Web App

Download on F-Droid

Rules

  1. Be nice.
  2. lemmy.world instance policy

Sponsor development! ๐Ÿ‘‡

Number of sponsors badge

๐Ÿ’™

founded 1 year ago
MODERATORS
 

Sometimes I get this error message when I try to post a comment, then I just cant comment under that post at all. On other posts it does work like it should. I have checked the language settings and they are set proberly. Is this a Voyager-problem or a Lemmy-problem?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] indomara 4 points 1 year ago (1 children)

I got this and had to log into my home instance and under settings in my profile, there is a list of languages. I had to hold ctrl to select "undetermined" and "English". After I saved that it seemed to fix things here.

The "undetermined" language you want to keep, otherwise it will filter out many posts.

[โ€“] dingus 8 points 1 year ago (1 children)

This doesn't resolve the issue of the OP. I'm addition to having a language in your user profile, the desktop version of Lemmy also let's you select a language for each comment you make (which I suppose makes sense if you are bilingual).

Your profile language selects what languages you view, but the comment language selects what language you are posting in. There is zero way to select a default language when posting for some reason. Also for some reason, sometimes when the OP specifically selects a language, it will not let you comment if your comment language is undefined. But, as I said earlier, your comment language will always be undefined unless you explicitly change it for each comment.

This is a Lemmy-side bug. The only way for Voyager to resolve it is to add a functionality of choosing your comment language in your posts.

[โ€“] indomara 1 points 1 year ago

Fair enough, perhaps it was solved simply by going to my profile, checking things, and saving? Either way, I was having this issue and it has been resolved since.