Is google play required for the app to function, or would sideloading the apk from a mirror site work?

I use sync, but I think they still should be FOSS, or at least open source. Just because when anything gets left behind or never fixed, you can take it and patch it up yourself. That includes clients too, lots of good clients that get left behind because Dev stopped and whatever they were interfacing with changed.

It’s just how many of us are used to things. Particularly the collapsed comments along with rainbow colors depending on the nested comments. I’m sure one of those has it, but Sync has all my patterns. And it was as simple as importing my sync for reddit config to get all my options as they were. Worthwhile wait, and I don’t mind supporting a Dev. Especially when there is a one time ad-free payment option, which is all I need.

Using web, going back always put the feed active, despite me changing the sort. So yeah, having the app back is good. And I got all my use patterns back!

Love it.

Some replies to a reply are showing up in the wrong place. Might be a bug, might be because I imported settings from old sync to save myself the trouble of configuring the application anew. Worked like a charm though.

I have a question, can I pin a instance in the feeds? Eg I have a lemmy.world account. Right now it shows me Everything, Local, and Subscribed. But I do want to see everything in programming.devs main page. It’s like an everything for programming, so I see that as a valid use case.

There is a small yes, but not for that big of a gap. There is some minimal advantage, which is if the framerate goes above that of a screen(even at 30 fps caps, you might hit 31 occasionally depending on how it’s limited), you get screen tearing. Screen tearing is where new and old frame overlap causing the image to tear. VSYNC and other tech avoids this, but comes at a cost of a small delay in framerate.

So the solution is simply to cap framerate either to a divisible part of the framerate, eg. 30 fps for 60 Hz screens, 60 fps for 120 Hz. You want divisible because if you create 35 fps, the frames will not be done at the same time as the screen is with showing a frame. Thus the need to have it semi matched up.

But this is a rather big loss for a good screen, so you’d like to just cap fps to a few frames below the screen Hz. Modern technologies deal with that by talking better with the screen, so the screen shows a frame until given a next one. GSYNC and FreeSync are the ones that allow variable framerate without needing to match screen Hz and FPS. (There are some limitations, particularly they can be limited to some framerate ranges iirc, and if you go above screen refresh rate you’ll still have either screen tearing or VSYNC kick in with that extra delay.)