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