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…

https://oauth.net/articles/authentication/

That aside, why is nextcloud asking for scopes from remote API in the diagram? What is drawn on the diagram has little to do with OAuth scopes, but rather looks like an attempt to wrap ACL repository access into a new vocabulary.

Scopes issued by the OAuth authorization server can be hidden entirely. The issuer doesn’t hold any obligation to share them with authorized party since they are dedicated for internal use and can be propagated via invisible or opaque means.

I really can’t figure out what’s going on with that diagram.

As a Ruby fan having a blast with Elixir, where the hell is anything BEAM related?

The compass is truly political.

Are you stupid or are you paid? „Let them have land” is literally the simplest most retarded solution, yet you dare use that descriptor against something else.

Ceding land to Russia doesn’t stop people from dying. Never did, never will do.

I get it, your sorry pathetic ass is tired of war that you’re not affected by. You’d rather sweep a few million lives under the rug and call it peace.

Well, your voice belongs under that very rug.

Following years of under-investment and despite increasing ticket prices, DB continues to make annual losses.

Ah, so nothing’s gonna change.

Russian allies also don’t give a fuck about red lines.

Whereas Ukraine’s allies were so unwilling to commit, that the war that could’ve been finished in the first year is increasingly likely to transition into EU invasion.

Would? They already do.

That’s a bit too humane for tankies. I’d rather expect „she’s a bitch and deserves to die” from the get go.

Yeah, had to dive in myself.

The answer is no, they can’t. You need to pass /dev/kvm and /dev/net/tun in a composefile for a reason.

There’s no „windows in docker”, but rather „handy windows vm orchestrator with nice UI in a container”. A bit of a mouthful.

Taganrog, Kuban, Green and Yellow Klyns, Kursk…

If we start to enumerate, Russia has a lot of territories they’ve ethnically cleansed to call them „historically Russian territories”.

Googling at least until fairly recently meant „I consulted an index of Internet”. It is a means to get to the bit of information.

Asking ChatGPT is like asking a well-behaved parrot in the library and believing every word it says instead of reading the actual book the librarian would point you towards.

Fraction of truth is the best lie, and you seem to have mastered it.

• ssh to remote, forwarding some remote port to your local ssh port (-R)
• ssh from remote through the exposed port, starting socks proxy in the process (-D)
• use socks proxy explicitly or find some tool that can route the traffic into it

Similar approach can be used to establish VPN tunnel with no encryption (ssh already provides that), routing everything but your ssh connection through it.

• ssh to remote, reverse forwarding your VPN-over-tcp server’s listening port
• establish vpn connection on remote, route everything but your ssh connection through the newly established interface

It will be wasteful, but it will work.

Why did you mention git twice?

It wasn’t supposed to be the revolution, it was sold like it was.

As a revolution, it relies on infinite applicability of Moore’s law to storage medium. In other words, it relies on infinite growth. It never left the square one.

It’s all about being comfortable with not knowing when you need to act. Believing that you can learn everything upfront is pure hubris, and once you hurt yourself enough times, you just drop the pretense.

In other words, life is Bayesian, not frequentist.

I can often implement 80% of a new feature without ever running the code.

I really love how they then go and invent their own TDD acronym to justify this. Types are proofs, and they replace a whole category of borderline superficial tests with useful assertions, but claiming that you implement a <random number>% of a feature when you haven’t once verified it is… a reason I regularly cuss at code and remain employable. Keep it up.

Good point.