| Website | https://justin.azoff.dev |
| Github | https://github.com/JustinAzoff |
This is a really interesting example of why implicit "zero values" for structs in go can be a problem: https://github.com/ubuntu/authd/security/advisories/GHSA-g8qw-mgjx-rwjr
"The temporary user record we returned in the pre-auth NSS request did
not have a GID set, so it defaulted to GID 0 (the ID of the root group)."
I suppose one could argue that it's more of an issue in posix that a uid or gid value of 0 was not defined as nobody/nogroup but root.
Still not too concerned about the AI robots taking my job.
❯ ollama run gemma3:12b
>>> /clear
Cleared session context
>>> How many letter R's are there in the word strawberry?
There are three "R"s in the word "strawberry".
>>> How many letter R's are there in the word strawberries?
There are four "R"s in the word "strawberries".
PayPal started by paying people to sign up. Their viral growth came from essentially bribing users with $10 to join and $10 for each referral. That’s not innovation — it’s buying market share with venture capital. Uber didn’t disrupt transportation — they ignored taxi regulations their competitors had to
Despite the best efforts of day 22, I managed to get all of #adventofcode 2024 to run in under 100ms (fm13 Ryzen 7840U). This runs and verifies all 49 results including reading and parsing the input files from disk:
❯ ,fast cargo run --release
Finished `release` profile [optimized] target(s) in 0.02s
Running `/dev/shm/aoc2024/release/aoc2024`
Day 1: 0.095ms
Day 2: 0.131ms
Day 3: 0.293ms
Day 4: 0.904ms
Day 5: 0.155ms
Day 6: 4.012ms
Day 7: 4.957ms
Day 8: 0.053ms
Day 9: 4.231ms
Day 10: 0.206ms
Day 11: 2.284ms
Day 12: 1.321ms
Day 13: 0.316ms
Day 14: 7.654ms
Day 15: 0.846ms
Day 16: 7.485ms
Day 17: 0.127ms
Day 18: 1.655ms
Day 19: 0.760ms
Day 20: 3.259ms
Day 21: 0.222ms
Day 22: 34.744ms
Day 23: 14.156ms
Day 24: 6.585ms
Day 25: 0.415ms
----------------
Total: 96.877ms
'cargo flamegraph' was critical as the slowest bits were often not what I thought they were.
Possibly the dumbest thing I've ever written
let val = match value {
"0" => true,
"1" => false,
_ => todo!(),
};
I really can't put a finger on why I loathe Intel so much for trying to make me a Lake expert.
8th gen? 12th gen? 13th gen? Bigger number better, sign me right up.
Raptor lake? Coffee Lake? Fuck right off with this bullshit.
Some CPU feature you're looking for was introduced in Ice Lake, and you have a Coffee lake and want to know if you have support for it? Well, no, sorry, there's just no possible way to know something like this without looking up the magic lake decoder ring.
MostlyHarmless
Jeff Atwood
The Zeek Network Security Monitor