dbx12, dbx12@programming.dev

Forbidden cookie

I’m not ja JS or TS developer, but I’ve never saw the appeal axios has over the standard fetch.

The tagging system is good on paper but will be gamed by the advertisers in no time. Basically bad SEO (adding random text without context just to push the site rank) all over again.

Pathogens could easily spread this way since your collection bin would require to meet hygiene standards (i.e. cooling and rodent-free) and you would need to make sure the people treat the scraps they throw in right. And are not such with gastroenteritis or similar diseases.

If you had a magic wand which removes all pathogens, your approach becomes viable I guess.

What makes you think it’s slop? Yes, she has an abnormally large bicep, but apart from that? Honest question.

Plus that adapter takes up one port…oh wait. But I’m still team wired mouse.

Fucking Gopher?

sad golang noises

(I know that Gopher and the protocol are not related)

Oh my, good thing I decided to play watch dogs 2 instead of ED yesterday. I hate it when I lose progress thanks to hacking shit bags.

Godzilla had a stroke trying to read this and fucking died.

Or random scrolling around. I’m looking at you CircleCI.

What’s wrong with a search button oder “press enter to search”? Am I getting old?

That looks a lot like HCL / Terraform / OpenTofu.

I’m not sure if that is an universal thing or just a Linux / X11 kinda thing but I can scroll horizontally with my mouse wheel. Just hold shift and then scroll the wheel.

There are actually “rules” about which pins may go into which positions. For example, you don’t want a very short pin (resulting in a “thick part” on the key’s blade) in the first position (closest to the bow, the part you are gripping on a key) and then only longer pins the further you move towards the tip. If you had such key, you could remove it from the lock while the plug is turned as only deeper cuts (for longer pins) are encountered by the first pin. And a deeper cut can take a shorter pin without issues. That’s why you don’t see keys with a “staircase pattern”.

Another limitation is MACS (maximum adjacent cut specification), which governs which cut depths may be adjacent. When you insert a key, the pins ride up and down the cuts on the key. If you were to put a super deep cut next to a super shallow cut, the “slope” gets too steep and the key is hard to insert or remove. This means if you know the depth of one cut and the MACS for this model of lock, you can rule out certain cut depths for its direct neighbors. For example, you know that the key you want to forge has a very deep cut, let’s say depth 8, on a particular position. Since we know the model of the lock (the professionals recognize a lock just by looking at the keyhole), we know that MACS is 5 and the deepest possible cut is a 9. The direct neighbors of our 8 can be either a 9 or anything from 7 to 3. They cannot be 1 or 2 since that would violate the MACS and repeating the same depth is also very unusual, so we can rule out 8.

Now add manufacturing tolerances into the equation and the potential key space is getting even smaller.

Edit yes, locks are a great thing to nerd out about.

HTTP 414 in the wild!

Understandable :D

Imagine you are an animal videographer and have to film dozens of goats falling to their death just to get one which miraculously survived.

Thanks for this wonderfully odd fun fact.

Wasted opportunity for a lemon speech, but still close enough.