Well, IIRC it’s not indirectly. Sam Altman negotiated pre-purchase of massive chunk of wafer supply, which OpenAI backs up with its virtual money.

So DRAM manufacturers are facing a wafer shortage in near future. Which translates into prices now.

Deadbeef

Cue sheets are important.

Beetroot salad. You will panic, though.

The windows have all the modern anti-burglary features and the plumbing is immaculate

— excerpt from a sale advert for a house with its front wall missing and the living room exposed to the elements

The market can stay irrational far longer than you can stay solvent.

No.

Every bit of code a maintainer accepts becomes their responsibility to maintain. Considering that half the time „improvements” don’t even have tests to help maintaining them, feel free to maintain your own fork.

„How do you know” is such a powerful question.

I especially like the Electrolux one. It’s simple, memorable, and once you see a butt and bikini, you can’t unsee it.

Thanks, I hate it!

If you guessed it right, your inflexible implementation becomes an advantage against other inflexible implementations.

There, I generated an AGI (actual grumpy ignoramus) summary for y’all.

A naive answer:

Replace “Lemmy” with a “Nazi manufactured gun”.

A less naive answer:

Consider various meanings “use” takes in your question and decide accordingly.

First, Omarchy doesn’t need funding or partners. It’s backed by a Nazi multimillionaire.

Second, the whole apolitical argument is bullshit. Everything is political. Support for a distro that doesn’t really need support by nature of being a child of a Nazi multimillionaire is a support for that Nazi multimillionaire.

“We didn’t support them because of that” means nothing. The support still sends a message. Just like artist loses control over interpretation of their art the moment they release it, people lose control over interpretation of their actions the moment they act. Does it sound fair? Maybe not, but it’s how reality works.

He’ll rather gain strange kinks. Losing weight with Polish cuisine is impossible.

Power users rebase with squashes and fixups multiple times a day. Especially if the job’s integration process isn’t enforcing long living branches.

Reflog is useful then, because you literally rewrite history every rebase.

It did solve my impostor syndrome though. Turns out a bunch of people I saw to be my betters were faking it all along.

Any claim of universal system of morality existence shatters at the minutest contact with history.

The idea of morality is dominant and potentially universal across human societies. The actual definitions are invented and reinvented constantly and fairly rapidly.

However you like, REST doesn’t dictate anything there. Just be consistent and use hypermedia.

JSON APIs almost never follow REST because they almost never use JSON as hypertext. Worse, no complete stable hypertext JSON standard exists. There’s JSON-HAL, but it lacks a way to represent resource templates (think HTML’s <form>).

Therefore, with JSON APIs ignoring one of the most basic idea behind REST, why would anyone expect them to follow another idea of REST - consistency?

REST is a deceptively simple concept. Any time you build an HTML website a human can navigate without consulting documentation, you’re doing it better than vast majority of swagger documented corporate APIs.

JSON API almost always means “not REST”. In other words, it works as intended.

I can’t muster any sarcasm out of sheer disappointment. You win this time…

I’d probably add that for something like nextcloud granted scopes can be an „orthogonal”–for the lack of a better word–subset of requested scopes.

The set of requestable scopes has to be defined by the system itself, not its specific configuration. E.g. „files:manage”, „talk:manage”, „mail:read” are all general capabilities the system offers.

However, as a user I can have a local configuration that adds granularity to the grants I issue. E.g.: „files:manage in specific folders” or „mail:read for specific domains or groups only” are user trust statements that fit into the capability matrix but add an additional and preferably invisible layer of access control.

It’s a fairly rare feature in the wild and is a potential UX pitfall, but it can be useful as an advanced option on the grant page, or as a separate access control for issued grants.