- On-prem
- Self-hosting
And I’ll argue it’s on-prem even if you don’t have the physical server in your building
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
I love every ape I see, from chimpan-A to chimpanzee…
Everything?
That’s because the Beatles broke up in 1970, so anyone who remembers them from their active years is well over 60, which would be really stretching the definition of middle-aged
I did the same thing, set up OpenWRT perfectly, then changed the local range from 192.168.1.0 to 192.168.0.0 to suit some legacy connections. Everything works, except I can’t change settings on the router, so for now I leave it alone
If you weren’t already watching James Hoffman, then Hames Joffman may not be the place to start… the latter is an unauthorised parody account, although apparently James is aware and not bothered
Of course if you’re watching James, you must also be watching Hames
You’re probably right, as I don’t speak Vietnamese. This is how they made the White Coffee I ordered here last week
Vietnamese Iced Coffee (Cà Phê Sữa Dá)
Ice |
Ice |
Ice |
Coconut milk |
Condensed milk |
Espresso |
SOHCAHTOA and a calculator have been real useful for that too
After 99 you just get a ♾️ symbol
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, 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
It’s the vibe
It’s the Constitution
It’s Mabo