Restricting access to files within a user is why sandboxing is useful. It in theory limits the scope of a vulnerability in an app to only the files it can read (unless there is a sandbox escape). Android instead prevents apps from accessing other apps’ files by having each app run as a separate user.

One way to keep the encryption keys encrypted at rest is to require the login password (or another password) to open the app, and use it to encrypt the keys. That said, if an adversary can read Signal’s data, they can almost certainly just replace Signal with a password-stealing version.

While I don’t disagree, it is possible that Kling picked up the writing style of he/him for unspecified gender. Kling is Swedish, and Swedish only recently made their gender neutral pronoun official. On the English side, it seems he/him for unspecified gender started getting pushed in the 1800s, though I can’t find info on when they/them regained usage.

Also, superior depends on the user and use case. One person might find that GIMP has all the tools they actually use in Photoshop, and another might find that the ones they use are missing from GIMP. Without knowing the audience, it’s hard to know what they want to hear.

The example implemented in Mithril.js, for comparison.

IIRC the main reason it isn’t enabled by default is because >=1080p is only available via DASH. Normally Invidious can just point the client to fetch videos from Google’s servers, but for technical reasons DASH requires the Invidious instance to act as a proxy (the client asks the instance for video data, then the instance fetches it from Google and sends it to the client). The net result is that watching 1080p streams requires much more bandwidth from the server.

As far as I can tell running xz directly should be fine, but for the extra paranoid check the version of the xz-utils package. If it is safe, it will be either less than 5.6.0, or it should be 5.6.1+really5.4.5-1 (xz 5.4.5 with a spoof version number to ensure compromised systems get the update).

Thanks, edited this into the post (along with the distros listed by LWN)

Amarok has support for managing music on iPods. Rockbox is an alternate operating system which doesn’t use the iPod’s database, and instead does its own indexing.

DarkTable sort of works for that, though if I recall correctly the browsing is based on a “library folder” rather than freely browsing. It is very heavily focused around editing photographs.

My recommendation is to combine a decent image editor (eg. GIMP) with a good file manager with image preview.

If I understand correctly, the idea is to cross-reference with the listed PGP keys to validate they haven’t been changed (implicitly by an adversary)? This essentially sounds like what you’re supposed to do with PGP anyway: keep the key so you can detect replacement of the key. The main difference is for someone who doesn’t already have the key, they can cross reference it with the directory (essentially like a Wayback Machine for PGP keys).

That’s specifically referring to when auto updates are enabled; on newer Android versions app stores can now update apps they’ve installed without needing the manual confirmation popup. Previously autoupdates would need a separate shim installed via root, since only system applications could perform unattended installation.

I’m not sure what would cause the difference, but the old behaviour (at least on my device) was to only do the download when updating all, with each individual app needing to then click the update button and the popup. With F-Droid Basic (which had this change for a while now), any apps it can update do so automatically when the update all button is pressed. Apps that it can’t do unattended updates on, such as those that were installed by another app, still required manual update on the first one.

The unattended updates just mean you don’t have to sit through and manually click the second install popup for every update. They come in handy even when F-Droid doesn’t have automatic updates enabled.

If you mean the IzzyOnDroid one:

The app uses Sentry, which is enabled by default and sends reports to Sentry.io.

Emacs is actually one of the easier editors to use in my opinion. The ribbon at the top makes most functionality accessible even without knowing any of the keyboard shortcuts.

Emacs does have an Android version, though it’s kind of buggy and not worth it (especially not without a physical keyboard).

Emacs org mode could work if you’re okay with tinkering a bit. There are keyboard shortcuts for check/uncheck, and you can do a lot of customization of how it renders in Emacs. Search might be a problem though.

Used US and JP qwerty, both are fine after a while, but switching can be annoying (mostly I mix up whether " or @ is Shift-2).

The one thing I hate is the fragmentation of the bottom left cluster. I started out on keyboards with Ctrl Fn Super Alt, but now I much prefer Fn Ctrl Alt Super.

Good data (and program) structures are definitely quite important. Well chosen structures make implementation much easier (and likewise bad structure makes things needlessly difficult).

Also, the film editing example is also an example of a piece table, which makes cutting very simple. Cutting out a section is just a node insertion + update the end of the original node ({0-3} -> {0-1}, {2-3}).

I’ve had similar issues as well very rarely with other languages. I’d type out a bit and get a syntax error, but when I complete the partial code it won’t update the errors. When that happens restarting the language server tends to fix it, so I presume the language server just locks up sometimes.

My guess is they see Tachiyomi as making it easier to access such content (through downloads and library management). I don’t know how the legalities play out, but on their end taking down Tachiyomi inconveniences those accessing pirated content, while being easier than directly targetting the sources.