1,657 karma · joined January 9, 2021
This is the crux of the issue. It's really unfortunate how botched the rollout of chip and contactless payments in the US has been, magstripes should have been completely eliminated a decade ago.
The UL mark is valuable, as are the other test lab marks. However, while an ethical storefront would require it, Amazon does not. I've bought plenty of things that are not listed, and if I want safe products I generally have to include "UL" or "ETL" in my search. Even that doesn't always work, I've seen products on there claiming a listing in the title but photo shopping the place where the UL logo ought to be off of their product images.
If only :)
This should work, but glibc has a bug where it doesn't support communicating a link-local scope ID in its name resolution subsystem. So you will have to first manually resolve the name, and then use the IPv6 LL address with scope ID directly.
With micro services, that same function call is now a minimum of 200us. And now I have LOC for serialization/deserialization, retries, error handling, etc, bloating my code and making it harder to understand, plus now to do the same integration test I need to understand N different build systems for each component.
post-build-hook = .../upload-to-cache.sh
upload-to-cache.sh: #!/usr/bin/env bash
set -euo pipefail
set -f
export IFS=' '
exec "${NIX_CACHE_NIX_BIN:-nix}" copy --extra-experimental-features nix-command \
--to "s3://my-cache-bucket?region=us-east-1" $OUT_PATHS
Set up environment variables as necessary for auth.Once a data center shows up, that plot of land is locked out of more productive development for decades.
If nothing else, the Sunshine Request site is a good place to get form emails for these requests from.
I don't understand what you mean. Doesn't smearing still mean the clock only goes forward? It's still steadily incrementing. The only difference is that a second is slightly longer/shorter than you expect, but you already have to account for that if you're doing the kind of physics experiment where it would matter.
If only we had research on the effect of a second or two's effect on user experience.
I wouldn't have a problem with it if it was on expensive endpoints like search or deep history dives, where it matters for server load. But it's every single page, out of some strange sense of righteousness.
Money anti-counterfeiting is trivial, it's just 5 dots arranged in a specific pattern. Deciding what is a gun part is impossible, even for an expert human.
Claude needs good variable names a lot less than humans do, so renaming/typedefing doesn't seem to be as necessary.
"Claude, change the libre office file picker to the system default"
"Beep boop it is done"
Linux has a big leg up over windows in this regard because all the GUIs are essentially wrappers around CLIs and text files that LLMs can deal with quite well.
I chose 1mm for my corner chamfer on the base, but you could make it any dimension including something imperceptible.
Greater power draw though; remember that energy is the integral of power over time.
You are welcome to join the conversation and try and convince everyone maintaining Wikipedia that random peoples' tweets should be considered a reliable source. Both those other people you mention have been mentioned multiple times in various reliable articles (see the bibliography), while the only thing I can find online about Ray Peat is something that looks a whole lot like blogspam on usnews.com.
For example, with unsuitable algorithms like sha256, you get this, which doesn't have a version field:
import hashlib; print(f"MD5: {hashlib.md5(b'password').hexdigest()}")
print(f"SHA-256: {hashlib.sha256(b'password').hexdigest()}")
MD5: 5f4dcc3b5aa765d61d8327deb882cf99
SHA-256: 5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8
But if you use a proper password hash, then your hashing library will automatically take care of versioning your hash, and you can just treat it as an opaque blob: import argon2; print(f"Argon2: {argon2.PasswordHasher().hash('password')}")
import bcrypt; print(f"bcrypt: {bcrypt.hashpw(b'password', bcrypt.gensalt()).decode()}")
from passlib.hash import scrypt; print(f"scrypt: {scrypt.hash('password')}")
Argon2: $argon2id$v=19$m=65536,t=3,p=4$LZ/H9PWV2UV3YTgF3Ixrig$aXEtfkmdCMXX46a0ZiE0XjKABfJSgCHA4HmtlJzautU
bcrypt: $2b$12$xqsibRw1wikgk9qhce0CGO9G7k7j2nfpxCmmasmUoGX4Rt0B5umuG
scrypt: $scrypt$ln=16,r=8,p=1$/V8rpRTCmDOGcA5hjPFeCw$6N1e9QmxuwqbPJb4NjpGib5FxxILGoXmUX90lCXKXD4
This isn't a new thing, and as far as I'm aware, it's derived from the old apache htpasswd format (although no one else uses the leading colon) $ htpasswd -bnBC 10 "" password
:$2y$10$Bh67PQAd4rqAkbFraTKZ/egfHdN392tyQ3I1U6VnjZhLoQLD3YzRe