sh.itjust.works Main Community

[–] little_hoarse@sh.itjust.works [S] 3 points 3 years ago (1 child)

okay glad it's not just me, thanks!

parent

[–] Sharp312@lemmy.one 6 points 3 years ago (1 child)

Found the github issue for it, apparantly its gonna be fixed soon

parent

[–] little_hoarse@sh.itjust.works [S] 1 point 3 years ago

amazing, thanks!

parent

[–] Afteg@sh.itjust.works 3 points 3 years ago

Yeah honestly makes it kinda unusable when the page is constantly scrolling away from what im reading

[–] manitcor@lemmy.intai.tech 2 points 3 years ago (1 child)

its just part of how updates work, i think the burstyness is a sideeffect of the load right now.

[–] little_hoarse@sh.itjust.works [S] 5 points 3 years ago (1 child)

i'm gunna guess it has something to do with the web socket connecting (from what i can see in the console) and not disconnecting when load is finished, so it just keeps loading whatever new content is available, instead of loading more when the user clicks reload

parent

[–] manitcor@lemmy.intai.tech 1 point 3 years ago (1 child)

yeah, if its dropping and checking every so-often you might get this, whats the overhead on keeping the socket open? I have used websockets very little.

parent

[–] little_hoarse@sh.itjust.works [S] 2 points 3 years ago (1 child)

no idea, i only know about side effects with react, where if you are fetching something, you should close the connection after it's fetched, then re-open on component mount, unless you are going for a constantly updated type of application

parent

[–] manitcor@lemmy.intai.tech 1 point 3 years ago (1 child)

i think the intent is to constant update at least for one of these tabs, this is how mastadon currently works but its less bursty.

parent

[–] little_hoarse@sh.itjust.works [S] 1 point 3 years ago (1 child)

That seems unsustainable with more and more people joining. Especially on the "All" feed.

parent

[–] manitcor@lemmy.intai.tech 1 point 3 years ago*

im not sure what the user counts on on matadon vs lemmy, its working for them...for now. Note that over 2/3 of my traffic is coming from edge cache, these nodes, properly setup arent working as hard as it seems. The client side however.

parent

[–] Jenga@beehaw.org 2 points 3 years ago (1 child)

I assumed it happened when someone on your instance subscribed to a new community for that instance so it loads in all the posts since they are technically new. Definitely a bug

[–] frankdew@sh.itjust.works 1 point 3 years ago* (last edited 3 years ago)

Interesting take on it. Another bug that I see often is a post with like 5 comments, but when I click on "comments" I don't see any. Even mine in some cases! I'm not mad, I guess all of it will require some fine tuning to work flawlessly. Edit : I've found the problem. It the account settings I had unselected english in the languages list!

parent

[–] frankdew@sh.itjust.works 2 points 3 years ago (1 child)

I saw that too, and most of the times it's a lot of days old post in a specific community... maybe there are some problems with synch operations ? I don't know.

[–] little_hoarse@sh.itjust.works [S] 1 point 3 years ago*

hopefully this is already in their bug logs!

parent

[–] Norrland4ever@sh.itjust.works 2 points 3 years ago (1 child)

Borrowing the thread

Mine is empty, when I log in after a day or so I still see 2, 3 day old posts. How do I get new ones?

[–] cryball@sopuli.xyz 2 points 3 years ago* (1 child)

Those are all known bugs. Apparently the active/hot etc. aren't updating properly after a server has been up for a while. Apparently the dev's are already working on fixes.

parent

[–] Norrland4ever@sh.itjust.works 1 point 3 years ago

Alright, thanks for the info

parent

[–] RoundSparrow@sh.itjust.works 0 points 3 years ago (1 child)

Lemmy code needs some work, it was not really tested with constant activity

[–] Echolot@sh.itjust.works 1 point 3 years ago

Especially the UI seems hastily coded