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

Most common cause is people changing their language settings in their profile. It’s a daily occurrence. The app really needs to tell people “25 messages not displayed because you are only viewing in Spanish”.

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 !postgresql@lemmy.ml community and asking for help, learning 101 about how to fix their SQL TRIGGER logic like Github Issue 2910 spelled out June 4.

I haven’t seen a feature for that yet, maybe I missed it? If indeed it is absent, I suggest !lemmywishlist@lemmy.ml - posting this

I’ve been testing for hours, and “Subscribe Pending” went away for the first hour or so after the restart of lemmy.ml - but now I’m getting them again. The underlying issue still seems there.

I think lemmy.ml has more posts, comments, likes in the database due to historic reasons - and the backend is timing out, PostgreSQL not keeping up to application timeout. I have seen the problem on Beehaw, Lemmy.world when they are busy and throwing nginx 500 errors on their front page.

Wonder if I can finally sub to lemmy.ml communities…

From my remote instance, I’ve been subbing to lemmy.ml communuites about every 2 or 3 minutes, and it just now started to jam up. I’m speculating that the server restart fixed the problem for the first hour or so, but now it’s back. Open GitHub Issue: https://github.com/LemmyNet/lemmy/issues/3101

Thank you for sharing.

Were these remote instance communities or local ones?

I’ve only seen it happen with remote instance ones. I’m curious what the code is doing.

I found another documentation page that actually tells you how to get the “v3” version…

https://join-lemmy.org/docs/en/contributors/04-api.html

That needs to be part of the “Lemmy from Scratch” documentation page too.

I knew it was v3 because I saw a webapp failure on one of the Lemmy instance (lemmy.ml) I was using ;) We need to update those install documents.

It seems right now I can get a client to load, but websockets aren’t working. Others on Reddit reported the same issue: https://old.reddit.com/r/Lemmy/comments/142sszq/spinning_up_lemmy_websockets_dont_connect/

EDIT: Ok, I solved the websocket problem by using proper nginx config that the instructions said. I was confused about the domain names with the certification generation as I already had some nginx certs for other subdomains in place.

A couple of us have been detailing experience and problems with those instructions:

https://lemmy.ml/post/1165322

https://lemmy.ml/post/1160483

!lemmy_admin is the official place for discussing install and being a server administrator

My guess is to leave open the possibility of adding HashTag support within the app. YouTube hash HashTags that allow you to jump between channels… I could see something like that working.

Is that the correct was to specify the version?

No, I had to dig around too, the correct command is:

curl localhost:8536/api/v3/site

The lemmy-ui steps, the next part - are pretty outdated. It has instructions to install NodeJS 12.x, which is really far back. I have no idea which version the Docker install is using…

The latest version of Node is 20

> thread ‘main’ panicked at ‘Couldn’t run DB Migrations’, crates/db_schema/src/utils.rs:165:25

I fixed this by issuing:

sudo -iu postgres psql -c “ALTER USER lemmy WITH SUPERUSER;”

Obviously this has database security implications, but at least it identified that was why DB Migrations is failing.

EDIT: I found the developers of Lemmy seem to have identified the cause for this, it’s just a couple SQL statements: https://github.com/LemmyNet/lemmy/pull/2983/commits/29c4144e61e97e895fb7eb37d2c257c8520fd6a6

EDIT 2: The developers are currently treating this as a documentation bug: https://github.com/LemmyNet/lemmy-docs/issues/201