How exactly does discussion of failures of a society help those who struggle right here right now?

When you see a burning building, it’s not a good time to start a discussion on merits of various building materials. Here’s a bucket, start hauling.

Oh the fucking irony!

Did you lose track of the written words after the first question mark perchance?

Not voting is a vote for the winner by default. I highly doubt that every single person that didn’t vote did so due to being unable to.

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!

I’ve been hoping for it to become widely available since first reading about it somewhere south of 2010. But I guess it would need to become easily manufacturable in local pharmacies for procedure to become widespread.

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.

This is one of those times when the attempt to address the wrong part of a statement immediately goes into Ackermann-like recursion.

The only irony present is the pretense of validity of the supposed contradiction.

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.

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.

You pronounce it yiff, obviously.

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.

But hey, you do you.

Yeah, something tells me that’s gonna need a persistent internet connection.

Probably tongue.

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.