I'm using Jerboa and while I was able to comment initially, it first started saying "deleted" immediately after posting and now it says "language_not_allowed" and the comment is gone, irrespective of content. What's up with that?

all 11 comments

sorted by: hot top controversial new old
[โ€“] 12 points 3 years ago (2 children)

It happens if you are replying to someone from an instance with strong language requirements (e.g. Kbin). You have to switch to the web interface to be able to select a language.

Annoying, but I'm sure the devs are aware of this

  • source
  • hideshow 4 child comments
  • [โ€“] 1 point 3 years ago (1 child)

    Huh. When this happened to me I assumed they had some odd filter that assumed I said a bad word when I didn't.

  • source
  • parent
  • hideshow 2 child comments
  • [โ€“] 9 points 3 years ago
    [โ€“] 7 points 3 years ago

    I had the same problem initially when joining Lemmy, but it works now.

    To comment I had to use the web interface, and where it says "select language" choose English. Otherwise you're posting with "no language" , which is not on the Community list of language, so the webUI would spin endlessly, and Jerboa would fail with language_not_allowed.

    I think if you choose English once when commenting from the web interface, Lemmy should remember it and Jerboa should use English and should work. Assuming you don't need to often swap between languages.

    I think the language mechanism is probably a good thing in the long run, but right now it feels a bit janky and confusing. For sure Jerboa needs an update to be able to choose Language in the app itself. It also needs to not eat your comment when it fails, cause having to type out a long comment again is infuriating.

    For some more info, see: https://reddthat.com/post/1976

  • source
  • [โ€“] 6 points 3 years ago

    Just assume everything going wrong is a bug at this point ๐Ÿ˜… it's quite early in development

  • source
  • [โ€“] 2 points 3 years ago (1 child)

    I've come across this before and just chalked it up to a random bug.

  • source
  • hideshow 2 child comments