C4K3

As the other commenter mentioned the web editor is probably the most beginner-friendly editor. It might seem a little daunting but it's actually not that difficult to edit OSM. When you save your change there's an option to request a review of it. That'll get an experienced contributor to take a look at it and help clear up any mistakes.

OSM also has a public database of GPS tracks that contributors use to aid in mapping. Even just walking the trails with GPS tracking on and then uploading the tracks to OSM without doing anything else is a valuable contribution that will allow other contributors to map the trails at some point in the future.

Keybase or any of the tools inspired by keybase (foks.pub etc)

At the very least they should have excluded any chats with disappearing messages enabled from being included in backups.

With disappearing messages off it was already reasonable to assume that a compromise of a counterparty's phone would result in exposure of all previous messages, so enabling backups wouldn't expose you to new risk.

That would cater to those who want to keep their chat history forever without exposing those with disappearing messages enabled to new risk.

They conclude that there's no wireless component to the feature.

This feature is not at all related to wireless activity. The law enforcement document's conclusion that the reboot is due to phones wirelessly communicating with each other is implausible. The older iPhones before iOS 18 likely rebooted due to another reason, such as a software bug.

Browsers could add the less severe warning before the certificate expires, for example 3 days before it expires have a "this certificate is about to expire, are you sure you want to continue?" warning. That would maintain the security guarantees around expiration while still getting the attention of users/administrators.

I learned about this when I encountered a server with an aggressive fail2ban that wouldn't let me log in because I had too many ssh keys. It apparently counted every wrong key as an auth attempt, so it blocked me before my ssh client tried the right key. Since then I've used IdentitiesOnly=yes

A reasonable solution would be to have a "Do you want to disassociate this phone from your iCloud account?" prompt as part of the factory reset.

Personally I think the screen being made bigger is a downside, makes it harder to use one-handed.

Still, it's too bad there isn't a 14 mini.

I've been doing this for close to a decade and sometimes salespeople and customer service people will ask to confirm, but that takes 5 seconds and isn't awkward (in my opinion.)

It has more benefits than knowing who leaked your email, it lets you easily filter your incoming email by who you gave the email to, and when your email is leaked it lets you shut off that email address. Of course you can also filter your email by the sender's domain, but that isn't as consistent, and doesn't help at all when your email address has been leaked.

It's true that you do have to set it up so that you can send email from the addresses to avoid not being able to reply by email, and you will want a password-manager or something to remember exactly what email you used, for convenience.

Personally I'm glad I've done this, it's made it much easier to organize my emails.

You don't have to use microsoft authenticator. TOTP is a big step up from SMS and most/good apps won't violate your privacy.