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.
Some of the best advice on cryptography comes from a site full of furry illustrations. A good chunk of infosec community intersects with a furry community.
I mean, „counter-revolutionary” should always be mentioned in definition of hypocrisy. The moment it gets thrown around, you know exactly who you’re dealing with.
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.