That feature you linked to is to flair users… there is a different issue to flair posts: https://github.com/LemmyNet/lemmy/issues/317

cool. I’m in the camp that the feature causes more problems than is useful. Entirely hiding posts of another language would not be my choice, it should at least say “there are 5 comments you do not see because of your language preferences”.

it does show the comments on incognito

That means it is tied to your login, something is set in your preferences so that you aren’t seeing content.

Picking “undetermined” isn’t the same as having never touched it. There is a steady stream of people who accidentally touch the language settings and say they don’t see anything.

People have called out how confusing the whole thing is: https://lemmy.world/post/523012

Sorry I can’t be specific on how to click and what works, I just know you aren’t the first to get their account where it stops showing routine content.

Without more details, it’s hard to know what you are describing. Do you mean comments from other people on posts you make? or your own comments?

I assume you are talking about the main webapp, lemmy-ui, and not a smartphone app or other front-end? The first thing to try is anonymous reading of the same post - are the comments there for incognito mode?

I’ts not uncommon for people on Lemmy to set their languages to something odd and and Lemmy will hide a lot of content.

I know you are salty about how you are getting treated over at GitHub

No, it isn’t about my personal treatment. It’s about the cultist attitude you have towards Lemmy and the leaders without any ability to see what they are doing behind the scenes with the code. I know cults and religious faith is how many people enjoy the world.

A 2-line SQL TRIGGER removal takes about minutes to fix. It was crashing the entire site constantly. They sat by and asked for donations of money.

A reminder to move to smaller instances for a better experience

A reminder that this constant advice people blindly parrot to install and flock to smaller instance has now created something like 1000 new servers in 50 days that are poorly run and already going offline as quickly as they went online.

Github Issue 2910 is the kind of PostgreSQL problems that the developers ignored for months and people still defend the developer choices to have the code doing real-time counting of every single comment and post for numbers nobody needs to needs done in real-time.

PostgreSQL is voodoo to this project, they do everything they can to avoid going to [email protected] community and asking for help, learning 101 about how to fix their SQL TRIGGER logic like Github Issue 2910 spelled out June 4.