mariusmarais
mariusmarais on Hacker News
It was also deliberate in the sense that they specifically wanted to make it impossible to link different identities on the same key in order to protect privacy.
So you can be user1 and user2@ without the site being able to tell from the authentication process alone. (Obviously cookies, IPs and other side-channels exist, but if you protect against that, FIDO won't give you away.)
I like how the replies are starting to make the little arrow thing. Reminds me of something...
Hope it wasn't P1 for the full 21 years.
Edit: Bumped from P3 -> P1 3 months ago :)
I think a big part of the problem is that probably 12x of those have to re-implement because they want to change something unrelated like styling, or want to add more components, but can't extend existing libs without using the same styling, so they end up re-doing everything.
So we end up with 20x libs all doing roughly the same thing, sometimes badly.
This one doesn't seem like the typical Munroe +1, because it's not trying to rule them all, just put a visually unopinionated base in place with the tricky, boring stuff handled. It kinda feels like other libs are doing too much in any case.
For me I get the best result when the receiver is on a USB extension hanging down from the table behind the monitor. Currently it's about 30cm from the floor. Every single on-desk position caused interference and delays.
(This is from a Macbook with USB 3 hub, so that might be the actual culprit.)
I was thinking about domains that may have transferred recently. We took over a very "nice" domain last year, but obviously not the historic emails.
Seems like someone finally got to Inbox Zero.
But terrifying at the same time. I wonder how many valuable targets might have had outstanding validations from 10 years ago, or even 3 years ago.
According to that document, they only take action after four weeks of no response from the original owner.
It doesn't say so explicitly, but to me it seems that a cordial "No" from the original author will probably be the end of it.
They don't. If insider information is suspected, the company can sue, and then prove it in court. See Waymo.
This is infinitely better than automagically preventing employees from being employable after working for a specific company.
This sounds more like the Oracle model than AWS.
Or exactly what Docker just did if you squint a bit.
In which case, just move.
I don't think _you_ (nor I in my personal capacity) would, but your provider definitely should, and then you get the benefit.
So if you're hosting via some accelerator like Cloudflare, AWS API Gateway, whatever Google has in this space, or app host like Heroku and friends, they'll happily do the work because they get the aggregate benefit. Your own site will become marginally faster or have happier roaming users, and so on, essentially for free.
When you're developing a generic website, I don't think you should care about this. When you're self-hosting, you can decide if it might be worth it or not. It probably won't be worth the effort unless you're doing something really intricate or special, in which case you'll be really happy that you have the option.
What you're proposing as a solution has already happened: Google relinquished their control over this protocol to the IETF, where it changed so much as to be incompatible with Google's original.
Now they're updating their own deployment, making it compatible with the updated standard.
Chrome/Android/google.com is literally changing what they do to match what the standard says.
I am personally very happy a company has come along to build something useful while charging a (fair?) price for it.
So happy that we just bought a team license for Tailwind UI.
Too many marketplaces exist where there is no value-add instead of sitting in the middle.
This is a nice tool and the Dockerfile is quite handy, but my guess is these books probably have a download limit per book since more used to be available.
Maybe use the script's category or individual book modes to ensure more people can get access to them?