I remember /r/SandersForPresident echoing this refrain. "When Sanders takes office we are going to line up the opposition and give them exactly what they deserve... (beat) ...free healthcare."
bss03
joined 2 years ago
Mine is close to that. I still had a working libc, but the dynamic library for C++ programs wouldn't load, so most of the Gentoo tools and several other things I expected simply crashed on startup.
Found enough working programs to get the library restored and remove the bad arch flags from my configuration to start another emerge world.
After that, I was pretty confident that I could run Linux at least as confidently as I had previously run WinNT 4.
I usually only have to deal with this feeling a few days at a time. I hope it gets better for you.
I primarily operate in strict standard compliance mode where I write against the shell specifications in the lastest Single Unix Specification and do not use a she-bang line since including one results in unspecified, implementation-defined behavior. Generally people seem to find this weird and annoying.
Sometimes I embrace using bash as a scripting language, and use one of the env-based she-bangs. In that case, I go whole-hog on bashisns. While I use zsh as my interactive shell, even I'm not mad enough to try to use it for scripts that need to run in more than one context (like other personal accounts/machines, even).
In ALL cases, use shellcheck and at least understand the diagnostics reported, even if you opt not to fix them. (I generally modify the script until I get a clean shellcheck run, but that can be quite involved... lists of files are pretty hard to deal with safely, actually.)
I personally prefer medium-rare, but if you want a grey ("well" done) steak that is moist, sous-vide is the way to do it. Reverse sear is great for medium, maybe even medium-well, but you have to introduce a moisture barrier (like the sous-vide bag) to keep the moisture in the steak as you cross higher temperatures. The physics of a oven, grill, griddle, or microwave just don't get you moisture and heat at the same time.
The physics might work for pressure cooking.
I doubt a pastry shell ("Wellington") would be enough of a moisture barrier, but not sure.
This is just the problem between the chair and keyboard how to implement the rest of encryption to enforce anonymity of the vote
That's not what that phrase means. Ensuring anonymity requires a fundamentally different process than signing with an asymmetric key -- involving zero-knowledge proofs, a separate theory from cryptography. A PEBCAK would be when the process is correct and unchanged, but the human (in the chair, at the keyboard) does something contrary (or otherwise inconsistent) with the process.
And yes, the software must be distributed consistent with the OSI's definition of open source. (Or consistent with the Debian Free Software Guidelines, which are older but substantially the same, even if it is not packaged for Debian.)
I build my own. Though I still need non-free software to run, I don't think it is from any DMCA enforcers.
System76 is not too bad if you want something mildly customizable but don't want to futz with doing assembly yourself. I get my laptops from them.
I've tried open phones (multiple) and I still use a Pixel. There is a choice, but I was willing to trade off my freedom for function there. I wish that wasn't the choice and when I can I support efforts to make it easier for people to choose freedom there.
So, yeah, there is often a choice. Doesn't make the status quo acceptable.
Theocratic confusion. Republicans worship Supply-Sidr Jesus. Christians model themselves after Jesus of Nazareth, Christ. The similar names are a source of confusion.
Also neither is related to Jesus that sells tamles at the farmer's market, tho I hear he is a pretty good guy.
Seriously tho, didn't one country determine that Subway sandwiches are served on pastry, not bread? I believe the legal definition (in that country) had to do with sugar content and Subway's was too high.
This is inconsistent with the preservation of democracy, as it allows a third party to confirm exactly who you voted for, and reimburse or punish you for it.
Mainly you'll have to tweak point 3, to use existing E2E.verified voting approaches which are only tangentially related to asymmetric encryption (and private keys).
We might use asymmetric encryption and private keys for some parts of identity verification, but you wouldn't sign your ballot with it.
I recommend having a public portfolio. You needn't have all your hobby code be public, but I think having source you've written available is an advantage.
When I was doing interviews, I definitely looked at GitHub (etc.) profiles of they were listed on the resume. I even found at least one indirectly -- either from their email or LinkedIn.
I like to point people at my accepted patched to open source software (Git and a Haskell library).
I "upgraded" to a new Pixel last year because I thought the battery on my old 4A was getting wonky (and I have not had good luck with doing battery replacements). At the time, I did not know (enough) about the Fairphone, and I could not find a new Pixel with an audio jack (maybe I didn't look hard enough?).
I'd like to go back to having a jack. I do have one scenario where I want to use well-fitting BT buds, but I can do that on any phone. I want wired buds that I don't have to charge, can switch between devices in 0.5 second, without interacting with any software, and don't have misbehaving touch controls that trigger when I brush my long hair back behind my ear(s) or shoulder(s). In fact, I still have a set of completely dumb buds that I use for my work laptop that I'd love to be able to use with my phone -- don't need noise cancelling or controls of any kind. I really hope that I can find a phone with a jack next time I do an upgrade. I don't care if it is thicker, I'm gonna stick on Otterbox (or similar) on it anyway.
I was also concerned about security, but full-power BT is fairly secure now. No one can "drive-by" and monitor or replace the audio; they have to get you during "initial" pairing.