Fair! I’m not giving enough credit to the fact that some applications don’t really have another option than to run root for some dependencies

I know it’s not the issue here really but

the container runs as root

That’s why we need to push for more self hosted containers to support running rootless. There’s no reason for it other than laziness IMHO.

It’s wild to me how many people will jump through a bunch of other random security hoops but not blink an eye about running containers as root

That’s a really good and reasonable idea, which is why I’m absolutely sure it will never happen 😢

This thread just reminded me to cancel mine. Good riddance IMHO. I should’ve done it back when they started spamming me with “quests” (aka ads) for Amazon and random fucking gatcha games. Between the privacy stuff and the pressure to monetize, there’s next to no way it’s gonna get better.

I’m not even a proton user anymore, for several reasons including the politics of the founder.

It’s possible to be correct and also a dickhead, as evidenced by the way nanook is behaving in this thread.

People are downvoting you because you’re being an ass, don’t give yourself too much credit

Isn’t 365 a combo subscription for word plus a bunch of other stuff? I can’t imagine many of those people are paying exclusively to use word

I’m not a great example since I’m a lemmy user, Linux user, and a million other things that makes me weird as a computer user. But I do have to exist in the modern world and file paperwork and shit just like everyone else, and I honestly don’t think I’ve had to interact with a docx file in at least 6 or 7 years. It’s all PDFs and web forms. Work is all Google Docs and confluence and that type of shit. It’s probably been 10 years since the last time I even opened an MS word client proper, once I left academia.

Anyway, I agree with you. Word seems deader than a door nail in terms of any text editing zeitgeist

Seriously. People wonder why politics in America has become a game of Jerry Springer style antics. Then you see people that you otherwise agree with politically eat up garbage political “content” like this.

If you’re gonna spend your time focusing on politics, at least try to avoid wasting your regurgitating their circus PR events.

Yeah I don’t think people realize that the biggest advantage of owning is to lock yourself into a stable housing cost. Even before it’s paid off, you lock in a more or less stable monthly housing bill. Maintenance sucks, big ticket repairs suck. But you’re always going to need somewhere to live.

I bought a place ten years ago, and if I was renting the same house today it would be about double the mortgage. Sure, I highly doubt that doubling will happen again in another ten years. But I doubt even more that we will ever see the prices back at 2015 level.

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.