RoundSparrow

joined 2 years ago
[–] RoundSparrow@lemmy.ml 1 points 2 years ago

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

[–] RoundSparrow@lemmy.ml 1 points 2 years ago* (last edited 2 years ago)

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".

[–] RoundSparrow@lemmy.ml 1 points 2 years ago

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".

[–] RoundSparrow@lemmy.ml 0 points 2 years ago (2 children)

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.

[–] RoundSparrow@lemmy.ml 0 points 2 years ago (4 children)

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.

[–] RoundSparrow@lemmy.ml 0 points 2 years ago (1 children)

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.

[–] RoundSparrow@lemmy.ml 0 points 2 years ago (3 children)

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.

[–] RoundSparrow@lemmy.ml 1 points 2 years ago

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

[–] RoundSparrow@lemmy.ml 2 points 2 years ago

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.

[–] RoundSparrow@lemmy.ml 1 points 2 years ago

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.

[–] RoundSparrow@lemmy.ml 1 points 2 years ago (3 children)

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

[–] RoundSparrow@lemmy.ml 2 points 2 years ago

Thank you for sharing.

 

A posting on the Instance-specific issues/observations about the upgrade: https://lemmy.ml/post/1444409

KNOWN BUGS

  1. Searching site-wide for "0.18" generates an error. This was working fine in 0.17.4 before Lemmy.ml upgraded: https://lemmy.ml/search?q=0.18&type=All&listingType=All&page=1&sort=TopAll
 

!lemmy_admin@lemmy.ml

I'm trying to get "Lemmy from scratch" working so I can hack on the code.

 

Example of posting I am talking about:

https://lemmy.ml/post/1165264

I can't find any way to click on the image to see it in full size to actual be able to read the text in the image. I can right-click and open the image in a new web browser tab... but it would seem ideal to be able to click on the image and see it larger.

Thank you

 

Still learning, but so far the webapp non-mobile experience seems to be that if I'm sitting on the home page looking at the listing of postings, it automatically inserts new ones at the top without me having to hit refresh.

That's different from "old Reddit", Fark, Slashdot behavior where the page output was static and a manual browser refresh is required.

Is there a preference to control this behavior so it can be a static page? I tend to revisit my web browser tabs after an hour or two and want to finish reading where I left off - and it dynamically updating goes against my desires.

Thank you.

 

The webapp is somehow using data from another posting or something? You can see in the screenshot that the posting was only 1 minute old.

 

Anyone able to confirm this problem before I open an issue on GitHub?

view more: next ›