I am willing to think that Google performs fingerprinting on the OAUTH login dialog window, which if prevented, similar to the comment above regarding Firefox being unsafe, it would block login through OAUTH as it pleases.
It also straight up doesn't allow you to publish an OAuth application that uses “restricted” scopes (like `gmail.*`) without a review process subject to arbitrary usage guidelines determined by the Google APIs team. That’s the catch. It doesn't even matter how you run the OAuth flow (though I agree I suspect they fingerprint that too). You get blocked earlier.
Just as you can run any program on any machine given enough time and resources (memory), anyone not lacking intellectual ability can learn anything - some quicker, some slower.
While I agree that everyone CAN learn anything, it doesn't mean they want to. Motivation is a big factor.
And when it comes to software development, the actual writing code part of it, I'm confident you need to have a knack for it.
Mind you, there's plenty of jobs in software engineering that don't involve writing code. We're desperately looking for a manager for example, because our current "self-managing" team is far from effective.
The intellectual part maybe but not the praxis. Some confidence, some unwillingness to stop searching for causes, some taste foe elegance, some ability to simulate things in the abstract space of solutions. The combination is as elusive to some as perceiving the mood of a room is to others.
Yes my understanding is that different people's brains can be wired very differently. Roughly speaking, many areas of the brain require specific stimulus during puberty in order to develop a particular way.
Right now on websites it's not displayed as green, but blue (or greenish blue).
Even the traffic light is called blue here (青) and they would look at you with surprise if you say the lights are green!
It's definitely getting worse and I agree it's worse than Windows 7, but I'll still take it over Windows 8+.
Linux really depends on what you do with it and whether you use a laptop or desktop. Desktop is really not a problem as you don't care about battery life, wireless connections or power management. But on laptops it can be tricky - Bluetooth is still a horrible mess in the Linux world for example.
Could it be that you weren't using it correctly? KeePass database files aren't supposed to remain open (for security of course) and it has quite a number of options to automatically close it after certain amount of time or when the window isn't focus, computer is locked, etc. This would trigger a sync with the (NC) server and assuming that all your clients follow the same usage pattern and close the DB after a small window of time, there shouldn't be any conflict.
> NextCloud to be always up of course, also self-hosted
You could use NextCloud's own hosting. But then Bitwarden's server needs to always be up too, and optionally self-hosted.
> Bitwarden just works
A low bar to recommend a password manager, don't you think so?
My remarks are from the self hosting perspective. To ensure an up-to-date KeePassXC db across all my devices I needed Nextcloud to always be reachable. KeePassXC was not smart about sync, so add one pw on a device before syncing, add one on another and you have two divergent databases that you have to manual reconcile. Bitwarden does not have this issue, and it also keeps itself synced, even if I only set up the add-on in the browser (with KeePassXC you always need the full program installed). With KeePass(XC) it's just an extra layer you need to be aware of, decoupling sync from the db.
For me BW has always just worked, meanwhile I have several KeePassXC dbs with a date in their name because of conflicts. Which arguably is because of NextCloud issues, which are my own "fault" (issues include, on work PC file sync services are not allowed, on Server somehow NC disconnects after every container update, since it is "headless" I often notice this very late, the shitty state of NC client packaging on Ubuntu will let you install very old clients that may stop syncing, you need to be aware of this... etc). Perhaps KeePass(XC) just works if you outsource syncing, but then still, it is easier to have sync conflicts than with BW.
And then there is the ability to share PWs with relatives with a BW account on the same server, KeePass does not have this concept as far as I am aware.
