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.
As a reminder, you can always just uninstall OneDrive and call it a day.
Until Microsoft takes that option away as well…
Not PeerTube, but he is on Odysee/LBRY.
On the one hand, having an AI generated alt-text on the client side would be much better than not having any alt-text at all. On the other hand, the pessemist in me thinks that if it becomes widely available, website makers will feel less of a need to add proper alt-text to their content.
The original research was regarding supercapacitors, not Lithium-ion. Based on the PNAS preview it seems it has to do with changing the design of a supercapacitor to increase charge rate.
Increasing capacitance (how much charge is stored to reach a certain voltage) or the voltage it is charged to would indeed increase the capacity. Putting several in parallel would work, as would making a bigger capacitor. The main problem as far as I can tell is that the energy density of even supercapacitors is low, so you’d need a much larger volume to have the same capacity (and thus a much thicker phone).
Alexandria and Stract use their own open source crawlers. Brave is also independent, if I recall correctly.
It’s more the other way around. Both distribution on the App Store and through third parties will incur the fee. However, if you don’t distribute on third parties, you can stay under Apple’s old terms, avoiding the fee. It’s a way of monetarily punishing third party app distribution.
Email subscriptions also sometimes have that, with bonus points for several vague and similar sounding categories, and emails not mentioning what category they’re in.
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)
The problem is that Apple doesn’t accept the responsibility. it’s the DMA that’s doing this to their customers, not Apple. By vilifying the DMA as harmful to privacy and security, Apple gets to make themselves out to be the good guy. When things get worse, Apple can just blame the DMA again.
Is there a picture of what this actually looks / would look like? Honestly, although it is going down a bad path, it isn’t actually all that surprising. Firefox already has sponsored address bar suggestions by default.
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.
The main downside is that there is a lot less customization of filters short of using a different DNS. There is also the potential for logging DNS (present with normal DNS servers as well). LibreOps claims they don’t log requests, and personally I don’t think they have much reason to lie, but there is still that element of trust. Many of the more well known DNS servers don’t offer ad blocking DNS, so you’ll most likely be switching to a different provider.
Another way is through DNS (eg. noads.libredns.gr).
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.