Comment on Do posts from instances that don't allow downvotes have an unfair advantage?
Anafroj@sh.itjust.works 10 months agoYou’re welcome. I don’t use mobile myself : do you use an app, or it’s just about opening your Lemmy instance url in a browser? If it’s the later, you can go in the settings and there is a “Show Scores” checkbox. Just uncheck it, hit the “save” button and you’re done. :) This is also where you find the “Sort Type” select box which allows to define default sorting and put it to “New”. It only works for posts on the homepage, though, you have to take the habit to manually click “new” after reading a post to sort its comments (I could have swear it was using the “Sort Type” option before, or maybe just remembering last sort, but it’s not the case anymore).
CloverSi@lemmy.comfysnug.space 10 months ago
I use the mobile site, so this is perfect! I’d been through the settings but totally missed that checkbox. Thank you!
It’s funny, I vaguely remember having comments sorted differently by default too, but I can’t seem to find any actual record of it. Mandela effect? Anyway, I’m hoping the option will be added soon, since I can’t get it to work quite right with a script:
This only seems to work when the page is refreshed for some reason. If you or anyone else happens to know a solution that’d be greatly appreciated, I don’t know javascript well.
Anafroj@sh.itjust.works 10 months ago
Thanks, that’s a good idea.
The reason why it only works on page reload is because Lemmy is a SPA : it makes it look like you’re browsing several pages, but it’s actually always the same, and it uses javascript to change the url and load new content. So the “load” event, triggered when the current page is done loading, is only triggered once because the page is only changed once. If you wonder why : SPA became commonplace in the 2010s because javascript applications started to get way bigger than previously, and it was helping with page load speed. For a time… because when you make page load faster, people just make it load more things until it’s slow again. :)
My first reaction was that additionally to binding to the
loadevent, we probably just can bind to thepopstateevent, which happens when the url is programmatically changed. But my first tests were not successful in doing that. I’ll have a quick look at the source code of Lemmy in the morning to see if I can solve this.CloverSi@lemmy.comfysnug.space 10 months ago
Thank you for the explanation! That’s wild, I’ve certainly visited SPA sites but I’ve never given much thought to what must be happening under the hood there. I guess it has its use cases but from a user’s pov the quirks can be kinda annoying. Case in point, I see why
loadwouldn’t do the trick - hope you can find whypopstatewouldn’t either (and thanks again)!Anafroj@sh.itjust.works 10 months ago
You’re welcome. :) Oh yeah, you probably use a lot of them, they are everywhere, although it’s not obvious to the user. One way to figure it out is to open the browser inspector (usually control + shift + i, same to close it) and look on the “network” tab, which lists all network requests made by the page, to see if this list gets emptied when you click a link (if it’s a real new page, the list is emptied and new requests appear).
My apologies, I spent an hour on the popstate problem before losing interest and calling it a day. Lemmy uses the
infernofrontend framework (a clone ofreact), which uses theinferno-routerrouter to handle page changes, which uses thehistorylib to do it, which… usespushStateas I expected it would. And yet, binding on popstate won’t work. 🤷 Maybe I’ll have an other look at it one day if it bugs me enough. :)