![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/a4cb9e53-9f83-42ea-ba63-49eb81a0e04c.jpeg)
It’s the vibe
It’s the Constitution
It’s Mabo
It’s the vibe
It’s the Constitution
It’s Mabo
And I’ll argue it’s on-prem even if you don’t have the physical server in your building
It tells you right there in the log: “DRDY”
I think the JST and Molex recommendations are on point, in case you’re after another option I use Tamiya connectors for 12v car chargers
If it is powered on but blank screen, you can try terminating the user session from a terminal
https://linuxiac.com/how-to-terminate-user-session-in-linux/
Of course if you’re watching James, you must also be watching Hames
No need to click, it complains about exactly what has now been changed. In essence you are always trusting the dev, why add other parties to that chain
Yes for dry products where there is little risk of contamination e.g. nuts and dried fruits, or whole fruit and vegetables
I’d reuse as long as the bag was in good condition and clean, maybe up to 5 times
And the 50 shades of grey colour palette that makes every element look identical - Can I click this? Let’s find out!
Powdered “after being boiled and ground”
What’s in the box???
Yes, that video is primarily complaining about F-Droid self-signing, and that it creates: a requirement to trust them; a single point of failure for security; and slows updates
The trade off is that developers must maintain their key, if they lose it the user must uninstall and reinstall the app, as Android will not trust an update signed with a different key
F-Droid used to build and sign the APK for each app they distribute using keys owned by F-Droid
That meant you had to trust F-Droid to distribute the app as per the source, and hope that the source hadn’t been compromised (as the developer wasn’t signing anything)
Now when a new app is added to the repo, they build an APK from source and compare it with an APK distributed by the developer
If they match exactly (and if there is no reason to think the developer key has been compromised) then F-Droid will instead distribute APKs signed with the developer key, and verify that the same key was used for each update
If the same key was used, F-Droid doesn’t need to build the APK themselves but can distribute the update as-is
The advantages then are that F-Droid is acting as an additional layer of security and assurance to the developer signing the APK, and updates can be distributed faster as F-Droid doesn’t have to build them
And the wax can build up in the washer causing all sorts of issues, particularly in front loaders
(Not OP) Thanks but that particular article is AI generated garbage (or just thesaurus generated plagiarism) - you can tell when they replace technical terms like ‘judgement’ or ‘decision’ with synonyms like ‘choice’
While the Cato Institute are some sort of libertarian think-tank, at least this is a real human-written article, and it links back to some better sources:
https://www.cato.org/blog/judge-willett-concurrence-highlights-qualified-immunitys-flawed-foundation
Every time someone says experienced users should use a more difficult to use distribution I die a little inside - I happily use Mint, have done for years, why make my life more difficult?
Does that make this the sequel to the sequel?