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.
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)
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).
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.
Their point regarding old and unmaintained apps seems a bit silly. Getting the same old and unmaintained app from the app’s website isn’t going to make it any safer. You’re still going to need to switch to a different app/fork to get updates.
F-Droid doesn’t usually remove apps that aren’t maintained, as far as I can tell. There are apps that haven’t been updated in over a decade (Quill). Since F-Droid sorts by recency of release, they tend to just sink to the bottom of searches anyway.
The addon version works on Android.. There’s an issue/“idea” for Chinese support as well. If I recall correctly, though, one of the problems is tokenization (the languages currently supported for example have spaces to separate words).
Whoops, I forgot to enable the dark theme on the page; maybe the need to explicitly enable using the browser’s dark theme is why Safari doesn’t really bother. I’ve switched the dark theme to use Firefox’s colors, let me know if there’s anything that is still broken.
Could you upload a screenshot of this page?
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.