Reminds me of when Dell laptops started smelling like cat urine. Dell denied it for a long time then admitted it was an issue with the manufacturing process. https://www.bbc.com/news/technology-24741832

Different kind of beast. In my opinion Datagrip is meant for heavy DB work with jetbrains ecosystem surrounding you as well.

Heidi is perfect for the kind of person who connects to a DB once in awhile to just get some crap done.

I used to use HeidiSQL a lot, then we moved to Azure SQL with entra mfa which Heidi doesn’t current support. I would switch back instantly if that support ever came out.

He triple downed on it as well.

I ran from Postman to Insomnia. Then that was ruined. Now I am onto Bruno. We will see how long that lasts.

Same except insert some insomnia forks/clones. Silver lining: if/when Bruno goes, I’ll finally be annoyed enough write my own.

Bruno ftw!

So how would this help in this case? The oauth info would’ve just been in the csv or in someone’s env file.

With OIDC, the "info" would be just a URL with the public signing keys that the server accepts as legitimate signers.

The server still does authorisation on top. And unless you control the private keys, you cannot mint JWTs that are accepted as legitimate.

So the "info" leaking is really not a problem.

I have a P50 or P51 and same. It’s a tank but love the thing. Mine is the model before they killed the drop on dock and I prefer that over the USB-C docks.

I loved the drop on dock.

To me this is gif vs gif. The populous has shifted in a direction the originator didn’t intend, but it’s the populous that use it.

RESTful to me is HTTP calls with PUT/PATCH/GET/DELETE and whatever else I am missing. The return doesn’t need to be json but needs to be structured so XML, JSON, etc

Part of the nomenclature problem here is that there's no other way to refer to an HTTP-based API. REST was originally an alternative to the horrible SOAP. I'd be fine with calling it something else (because the author is right, nobody's following Fielding's vision), but there's nothing else to call it.

"JSON-over-HTTP(S)" is a bit verbose, but accurate.

The author suggests RESTless.

HTTP API?

this is explained in the article... referred to as Level 2 of Richard Maturity Model.

"Everyone stopped at Level 2 of the RMM"

While you aren’t wrong, I haven’t seen a distro that defaults to bash not have this enabled by default for a long while.

I remember reading a very similar chain last year, trying it on my Proxmox host, and then being surprised it didn't work. I'm sure it's not the only modern distro this way, but I can't claimed to have tried very many after that.

I don't have debian handy to check at this moment, but the devuan machine (and devuan is typically debian config for the 99% of things that are not systemd) I have installed using mostly defaults, does not have it enabled by default.

Privacy is not anonymity.

Came to say the same thing lol. Especially since Keeper Security deal with credential management.