

Out of curiosity, do you own your tools?
Out of curiosity, do you own your tools?
You can also “simply” raw-dog Wireguard. It’s built into the Linux kernel, so you barely have to install anything besides the userspace tools.
Basically, I objected to being reliant on the generosity of a for-profit company. “We do these things not because they are easy, but because we thought they would be easy.”
This is a rough sketch:
wg-quick
.Boom. Tailscale’d.
I’m sure I’ve forgotten some steps. I have some janky automation that’s broken in a new way every time I try to use it.
Not a lawyer, but I thought trademarks are distinct from copyright. Even if copyright went poof, it’s still possible to violate a trademark.
I thought flies use ZZ
for the onomatopoeia
deleted by creator
I have no opinion of them, but I’m curious why advertising would imply untrustworthiness. Are you saying they’re too eager or something? Spending money on ads is also consistent with a company that’s making money by charging for a service — I’d be more suspicious of free VPNs.
Given the warning about capitalization, the best possible case is that they’re using ast.literal_eval() rather than throwing untrusted input into eval()
.
Err, I guess they might be comparing strings to ‘True’ and are choosing to be really strict about capitalization for some reason.
My knife is printf, but my scalpel is gdb.
I honestly think autocorrecting your scripts would do more harm than good. ShellCheck tells you about potential issues, but It’s up to you to determine the correct behavior.
For example, how could it know whether cat $foo
should be cat "$foo"
, or whether the script actually relies on word splitting? It’s possible that $foo
intentionally contains multiple paths.
Maybe there are autofixable errors I’m not thinking of.
FYI, it’s possible to gradually adopt ShellCheck by setting --severity=error
and working your way down to warnings and so on. Alternatively, you can add one-off #shellcheck ignore SC1234
comments before offending lines to silence warnings.
Hey man, don’t bring IEEE 754 into this unless you want to discuss how negative zero, infinity, NaN, and subnormals relate to the qualia of color perception.
PSA: Run ShellCheck on your shell scripts. It turns up a shocking number of programming errors. https://www.shellcheck.net/
I lived in a semi-rural area where they didn’t check the gas meter for months at a time and just kinda guessed each month.
Y’all remember Amarok or am I old?
It is pronounced like “curl” though!
We pronounce curl with an initial k sound. It rhymes with words like girl and earl. This is a short WAV file to help you:
You wouldn’t download… a vinyl record…
I’ve accidentally taken a double dose of my stimulants a few times and holy shit, I will never do that again on purpose. I felt an unpleasant manic energy and generally jittery. There’s absolutely zero chance of me abusing or ODing on this drug.
I think you might have to buy one more book as well? If I had four problems, I’d still be left with one.
You only feel the ones that you can feel. The goddamn ninja mosquitoes permeate the air we breathe. They’re constantly feeding on us — sapping our life force — and we never even notice.
Thank you for honoring the ancient memes. I pray that Katy, t3h PeNgU1N oF d00m, accepts this offering.
Are you arguing that assembly languages are not architecture-specific? I don’t think that’s the typical definition.
Nasm is an assembler, but it also represents a specific assembly language targeting x86 architectures.
Gas is an assembler of a higher order. It can emit code for many architectures, and thus it accepts many different architecture-specific assembly languages.