Does that mean if it’s the first time I’ve heated this canned tuna I’m in the clear?

Gottem

I think we’re going to see a lot more of this kind of thing because supply chain attacks are “cheap” to hack together with LLMs now. The attackers are just fishing, if 1 in a million of the people who get infected has a valuable or monetizable credential that they can exfiltrate, they’ll make their money back. Just like phone and text spam became ubiquitous when jank-ass phones and sims became cheap, supply chain and low effort hacking campaigns will become prevalent when jank-ass programming becomes cheap.

CachyOS, which is one of the fastest growing distros and gets haphazardly recommended to tons of gaming refugees, ships with paru by default. Millions of forums, search results and LLM outputs encourage those same users to install stuff from AUR.

Any arch distro that has a sizeable non technical user base should know better than to ship or encourage using AUR. Shit like this is how we kill the “Year of the Linux desktop”.

I haven’t played since Wrath of the Lich King (started with vanilla around launch) and still have super fond memories of the Alliance starting areas in particular

Death to Hogger

Assistive technology as a back door to normalizing use for able bodied people is a pretty common playbook at this point. AirPods use a ton of tech pioneered in the hearing aid, for example, and a lot of consumers were put off by them initially, but 10 years later they’ve become incredibly normalized.

So as much as I agree with you that people with paralysis are an optimal case, it’s good to be careful about allowing public perception to slowly morph over time

Absolutely, anyone who thinks it was a golden age didn’t have to live through the broader flash based website hell. Flash games and videos were just the silver lining on otherwise noxious Adobe shit scented cloud

I live nearish to a military base so a lot of local businesses have a military/veteran discount.

At the store I buy dog food at, the staff are so tired of asking about it that they have shortened “are you a member of the military?” to “any military?”

After I noticed it a few times that every single employee in the store shortened it that way, I started answering “there is one, but I’m not in it.”

Loooots of blank stares. I stopped since apparently nobody gets it or they don’t think it’s funny. I think it’s the former but idk 🤷

Many GraphQL and gRPC APIs do exactly that and return HTTP 200 even if the request didn’t auth.

Just because you are heavily biased toward using HTTP status for application layer errors doesn’t make it right. It is so wildly common that people can’t imagine it working another way, and I get that.

But it’s not “wrong” to do application layer auth status codes and apply no transport layer auth status codes It’s just a different paradigm than most devs are used to.

What do you mean? You can literally run GraphQL without HTTP. This isn’t just a GraphQL-ism, gRPC also does it https://grpc.io/docs/guides/status-codes/

I understand that most people use GraphQL over HTTP and that from a developer perspective you’d rather have HTTP status codes like every other REST API. To which I’d say, why don’t you just use REST instead?

There are a bunch of legitimate reasons why a clean separation of transport layer and application layer makes sense - you just aren’t using them so it feels like an arbitrary frustration to you.

Have you ever run an application like a golang REST API behind an envoy or nginx proxy or load balancer and gotten an HTTP status 500 back and wrongly assumed it was coming from your application/golang code, only to later find it was a problem at the proxy or load balancer? If so, you’ve experienced the misdirection of combining transport and application layer being forced to share a status field. This isn’t a trivial example - time is wasted every day by developers misdiagnosing errors originating from transport as application errors, and vice versa.

You might not like it, but separating them IS smart design.

That’s true, but for a good reason. GraphQL is transport agnostic, so using HTTP status to represent errors doesn’t make sense. HTTP is just a carrier for GraphQL, and the status code represents whether or not the HTTP part was successful.

Ghost of Tsushima is amazing! I’m not usually the biggest open world fan, but that one really worked for me