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.
No, my argument is that Russia’s and Russians’ actions are consistent across multiple statehoods and governments, making any attempt at redeeming them by shifting blame to a specific government an example of mental gymnastics.
Only actual attempts at taking responsibility for what Russia has been doing should count. And frankly, those Russians that do take responsibility—many of whom already got disappeared—will get erased from history and from possible future definition of „Russia” if Russia is not taken seriously to be your enemy here and now.
Russian mafia regime is Russia. Both its genocidal conquest policies and the tradition of subservience to a central authority predate the word “россия” and are consistent across governments and states.
The idea that wars of conquest and genocide Russia throws itself in since before we formulated the definition of a word „genocide” are somehow not about Russia would be the winner of every mental gymnastics competition for years to come.
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.
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.
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.
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.
UIA is effectively defunct. Iran isn’t gonna pay anyone shit. The whole ruling, if it were to be taken seriously, would ground flights in Israel.
This looks „performative”. I hope there are enough assets left for families of the victims to get a reasonable compensation - that is frankly the best way to liquidate assets of a bankrupt company. I don’t actually expect it - creditors tend to strip everything, leaving barely an insult behind.
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.