andsens

Agreed. With all the improvements in namespacing I’m seeing the potential of all desktop apps being namespaced in a reasonable way, where filesystem access to e.g. /home is controlled through a kernel-hook prompt callback, with something like “always allow for this directory” etc. That’d be so awesome!

That's not a move of a company that thinks it can still grow. That's a Netflix "we have 90% of the market, let's squeeze them" move. This is the beginning. We have all seen this pattern over the last 5+ years. You know their next few moves.

100% agreed. I don’t understand the point of throwing all conventions out the window and building their own brittle scripts on top of it. All their images require docs to configure because none of the upstream documentation applies.

As someone watching and following all this from across the pond in Europe: This looks like a fucking coup alright.

Here’s a good answer that tracks with what my parents, who are dentists, told me: https://www.reddit.com/r/explainlikeimfive/s/H4MsnWKatM

> For the longest time, surgeons, dentists and optometrists weren't part of the medical profession. You'd have a barber who could give you a shave or pull your teeth, or a butcher who could cut up a hog, or cut off your gangrenous leg. Optometrists were craftsmen who made the spectacles in their shop. Doctors were University educated in Latin and Greek to read ancient medical texts and despised the uncouth yokels.

> Surgeons muscled their way into the medical profession, originally with the help of the Royal Navy, who only had space for one or two people in charge of both cutting off legs and looking after crew health on their ships.

> Dentists and optometrists never did, so they started their own universities, certification boards, etc. By the time they became respectable enough for people to try to merge them with the medical establishment, in the 1920s, they had no desire to give up their independence.

> The first insurance policies were private contracts with groups of doctors and the system developed from there.

Details vary from country to country of course, but the gist of it generally holds true.

The reason the average age is so young is because they are the ones getting caught.

Agree with all the positive takes in here. Just wanted to add that the graphic design is chef's kiss. Especially the image transformation of the album art! Some of them are hard to parse and it almost becomes a game, and then there are others where it's clear as day that e.g. the band is posing for a picture. Also just recognizing covers that you know is fun.

EU market regulators: "Hold my beer" *cracks knuckles

7 lines into the README buddy: > The command essentially looks at the lines that were modified, finds a changeset modifying those lines, and amends that changeset to include your uncommitted changes.

Now that’s the kind of clickbait title I can get behind!

This is satire. Right? Right?!?

The fact that it is even legal to ask patients to sign away their right to privacy boggles the mind.

> Pueue is considered feature-complete

Oh that is sweet sweet music to my ears!

devils advocate: Is this maybe a case of discarding an 80% solution because you can’t do the last 20%?

I understand the constraints, but imagine how legible you could make code by replacing some key parts with a graph type that everybody knows. I honestly think that having a type that supports a small subset of possibilities and only has the simplest algorithms implemented would go a long way.

I never understood the appeal of service meshes. Half of their reason to exist is covered by vanilla kubernetes, the rest is inter-node VPN (e.g. wireguard) and tracing (cilium hubble). Unless I’m missing something encrypting intra-node traffic is pretty silly.

K8S has service routing rules, network policies, access policies, and can be extended up the wazoo with whatever CNI you choose.

It’s similar to Helm, in that Helm puts a DSL (values.yaml) on top of a DSL (go templates) on top of a DSL (k8s yaml), just that it is routing, authentication, and encryption on top.. well, routing (service route keys), authentication (netpols), and encryption.

It boggles the mind!

In that case whoever is linking the script is “breaking” it, I’d say. There’s stuff that is simply outside the responsibilities of the script/maintainer. If you start worrying about that for “simple” scripts, the logic for handling that is quickly going to outgrow the initial logic itself.

Well aaakshualy *nudges glasses up the nose

Heh, kooky bastards

> The files the threat actor obtained in the Okta compromise comprised HTTP archive, or HAR, files, which Okta support personnel use to replicate customer browser activity during troubleshooting sessions. Among the sensitive information they store are authentication cookies and session tokens, which malicious actors can use to impersonate valid users.

I know that troubleshooting for pwms is hard, but leaving unencrypted files to access accounts on a server that’s not governed by the same threat-model seems very negligent to me.

Get your employer to pay for Kagi. It has honestly saved me several days in search time over the last 1,5 years.

The most prominent feature for me is that it only shows 0 or maybe 2 search results when there really isn’t more to find. It’s freeing, honestly.

I used to verify it with a Google search like you, only to be confirmed every time. I haven’t been doing that for a while now :-)

When talking about security updates it most certainly is. You can’t blame LE for that. That responsibilty lies squarely on manufacturers who are not even maintaining the bare minimum of security patching like an up-to-date root cert list.

> Those were the best hours of blissful bewilderment.

What a fantastic alliteration to describe his state of mind :-)

shameless plug If you want to avoid having to write your own args parser everytime or think getopt is a pain, you should check out my little project:

https://github.com/andsens/docopt.sh

No dependencies, the code is directly inlined into your script, and you write the args parser by writing the help-text.

Made me think of the good ‘ole Pessimal Algorithms paper: https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.11... Always a hoot to read ^^

> However, suppose the maze is actually quite agreeable, so much so that we wouldn’t mind spending a few extra cycles in the search for v; in fact we vaguely hope, nay, decidedly wish, that the search will take as long as possible,

Uhm. You’re basically asking how the entire NN works. There is no easy explanation for that.

Heh, yup. I remember an article on here about some low-level calculation optimization for 32-bit ints that bugged out even with extensive edge-case testing. The conclusion being “just test all the numbers”, 2^32 isn’t that much!

Years ago I wrote an article explaining how to do that in pure CSS: https://medium.com/@andsens/radial-progress-indicator-using-...

It's basically the same thing, just fully radial instead of just a gauge.

Here's a working example: https://jsfiddle.net/andsens/mLA7X/ (click in the middle of it to animate to another random percentage)

In Denmark we have a term that circumvents this issue completely. It was coined by Peter Naur in 1966: “Datalogi”. The discipline of understanding and working on data. I think it encapsulates the core of the profession really well while avoiding overlap with other disciplines.

I would love for an EU law that prohibits sellers from swallowing the cost of transaction fees or marketplace cuts. Imagine the app store having to specify the additional cost a user has to pay for a monthly subscription or a customer balking at the 4%-6% surcharge they have to pay because they want to collect their AmEx points or want to pay with their built-in iPhone ApplePay feature. Those leeches of the financial industry would disappear very quickly.