YPPH

The broader question of whether it is appropriate to independently back up your own data in large scale cloud services need not be answered. It is simply sufficient to recognise the risks are far greater when dealing with a one man operation.

It's an easy statement to make: "just take a backup". But that requires me to dedicate time to implementing a secure and automated solution (and of course, routinely testing restoring it). I'm not doing that, because I pay the service to do that for me. If I'm going to that effort, I may as well self-host.

To put things in perspective, I dare say that many large commercial organisations who rely on Office 365 are not backing up emails locally. They do likely have fancy retention holds preventing nefarious actors who compromise access to the account nuking things. I think Fastmail's backup is limited to 7 days. Outside that is a risk; it's one I'll take.

Maybe we have different perceptions of risk. But I think one can reasonably take the view it is unnecessary to have an independent copy in this scenario.

You can't save your personal passkeys on your work phone and vice versa, but when logging in to a service on one device, you should be able use a passkey from the other device via Bluetooth by scanning a QR code.

I suspect this post on HN is more likely to make its way back to a Gboard Developer than submitting feedback in the app.

Where does the GPL state this requirement? It doesn't.

If WordPress doesn't like this, they should have licenced their software under the AGPL or some other licence with stronger copylefting.

Plenty of large commercial entities use BSD licenced software and make a fortune off the software, with little given in return. Take FreeBSD and the significant commercial operations it drives. They never whinge. Because that's the choice they made, and they stick to their principles.

* It's challenging to copy physical items (you have to photocopy every page which few people do) and you can't do it verbatim (you can't make a 'clone' of the book, it will always be an inferior reproduction). It's more straightforward to remove DRM, and you then have a 1:1 unrestricted copy.

* Library books deteriorate with use and get lost, meaning there will always be the possibility for further revenue, particularly with popular items.

* Physical lending is not governed by software interlocks; software which may not be capable of being inspected or audited by the publisher.

The mitigation is good, though I did like pressing tab and having @fastmail.com autocomplete, which doesn’t happen now unless the input box loses focus (so enter alone doesn’t work). However I’ll just get used to pressing <tab> <enter>. I am nitpicking. The implementation is excellent (particularly onboarding).

In my view, it is a backwards step. First, I can’t do username <tab> password <enter>. Secondly, with auto fill, it requires two clicks to sign in.

I can understand it for Microsoft login where push notification login is an option. Otherwise, I’m not sure it is a great design pattern.

I would prefer a regular sign in page, with a button to sign in with passkey (which also does not require username input).

There's some subtle assumptions about ownership in this comment that aren't accurate, insofar as free and open source software is concerned.

FOSS software is not "someone else's" software. They may own the trade mark, but by releasing the software under a FOSS licence, they lose the right to control the direction the software may take. I'm free to copy it, edit it, and redistribute it as I see fit. So are you. So is Debian.

Side note, why were Ticketmaster hiring systems programmers writing such low level code? I grew up in the 90s/00s so missed this era of computing.

What the internal crisis-management paper did not give advice on is what to say if the "advice on what to say if discovered" was discovered.