Applications where the APK is not published alongside the source code in GitHub or whatever, and is instead only available through an F-Droid repo (like Mull), take some extra configuration to set up through Obtainium. Fortunately, there is this neat crowdsourced list of popular apps that require that type of extra configuration, where you can find an app like Mull in the list and quickly import its configuration into Obtainium
Mull still requires the manual compat lsit for whatever reason, therefore now in ironfox you run into that issue
But I do not experience that issue with IronFox. The other user above did, but Bitwarden autofill has always worked for me in IronFox with no issue. So far, the only difference I have experienced between Mull/IronFox is the app icon.
Interesting. I have never had an issue using Bitwarden with either Mull or IronFox. I did experience that package ID issue with Mulch (the Chromium version of Mull), but that seemed to have fixed itself at some point somehow. But although all three of those browsers do Bitwarden autofill for me without issue, none are in that hardcoded list.
Now I don't have to worry about having to check every so often to see if they've updated by going to their gitlab!
You might want to look into Obtainium if you have any other apps you do that with. You add a link to GitHub, GitLab, Codeberg, etc. into Obtainium for whichever apps you want to track, and Obtainium will automatically check each source in the background every six hours or whatever.
Is this a fork of Simple Draw? Judging by the screenshots, I think it is. I wonder why they had decided to rename it completely, unlike their other forks.
Sure, but it's still ironic. I'm not saying that it's a bad thing to buy a Google device just to degoogle it, but I think that does fit the definition of irony.
In my experience, KDE Plasma is surprisingly actually better than Gnome for tablet use. You would think that Gnome's more minimal and chunky UI would make it a better fit, but Plasma just has a lot more little usability QOL features.
In season 4, an episode shows a character going back in time to the events that occurred during the pilot episode. Even though the character was not in the pilot episode, this S4 episode implies that they were there in the background, off-camera, the entire time, and playing a pivotal role in the events that kicked off the series.
If you watch a certain scene in the actual pilot episode, you can briefly see that character's shadow in the background, implying that the creators had actually planned these time travel shenanigans from the beginning.
Many fans claim that the shadow was not actually in the pilot when it was first aired; that it was only added in reruns and home releases after that S4 episode was written. Other fans claim to have a home-taped recording of the very original broadcast and that they do see the shadow.
The person that made this video came across a social media post where a user showed off a pre-release promotional tape of the pilot episode. They contacted the user and purchased the tape for an undisclosed amount.
After a drawn out sequence detailing their multi-camera setup used to record the tape playing on their TV (in an attempt to prove nothing is being faked), we see that the shadow does indeed appear in the scene just as it does in all reruns, etc.
Yeah, it probably comes down to resistance. When you start to move the stick from the center, you have to work against a tiny bit of resistance. With a touchpad, there is absolutely no resistance to let you know when you are not at the center. As you say, that little rumble you get is not equivalent at all. Possibly an even more important type of resistance is how a joystick basically has its own physical boundary to limit how far you can push the stick in any direction. You can flick the stick as hard/fast as you want, and it will always stop at a certain point. On a touchpad, you don't have that resistance, meaning you have to manually slow down and stop your finger as you reach the edge, or else it will just fly off the touchpad.
That might be it. I am using Android 15.