Upon completing the Safari upgrade, I was forced to upgrade to 1Password 7.x, which forced me to upgrade my Dropbox password storage to a new file format… an avalanche of changes and I am afraid I may corner myself into having to spend more on 1Password.
Safari 13 Is Out
71–76 of 76 posts
Re: Safari 13 Is Out
#72One thing Safari really needs to fix: suggesting a secure password but then not save it. I have been trolled too many times.
This.. I'm sure it's happening because the respective websites use JavaScript to submit the form data via XHR, but I've been burned so many times by the password generator that I'm writing down the password from the field before submitting it. Very frustrating! Entering it in the actual login form will then usually trigger a save of the credentials.
Nice thing about 1Password (just a user) is that when you submit a generated password it is also temporarily copied to the clipboard. I paste it somewhere (typically at a bash prompt) in case this happens if it does make or adjust the correct entry. Sucks, but there are, as they say, no standards.
The nice thing about it being at the bash prompt is I can just press ^U and it doesn't end up stored anywhere (and even if it did it would be a random, contextless string).
Re: Safari 13 Is Out
#73> Added support for FIDO2-compliant USB security keys with the Web Authentication standard in Safari on macOS. well this makes me happy at least
I wish there were a way for third parties to enter their protocols into the secure enclave on the Mac and iOS devices. Then you could pay yubikey but not have to carry an extra device.
Likely this would be difficult on levels I can't even imagine.
Re: Safari 13 Is Out
#74Earlier quoted context omitted.
They've had a natively compiled content blocking engine for years, and I've been using Ka-Block. It works really well without killing your battery.
Looks like it is only for iOS, is this true? https://apps.apple.com/us/app/ka-block/id1037173557
No, I use it on macOS too.
Re: Safari 13 Is Out
#75Upon completing the Safari upgrade, I was forced to upgrade to 1Password 7.x, which forced me to upgrade my Dropbox password storage to a new file format… an avalanche of changes and I am afraid I may corner myself into having to spend more on 1Password.
1Password is an amazing piece of software that is worth every penny.
I used to always buy my license instead of the subscription but recently switched because frankly, I know it's a better business model for them, and I get so much value our of 1P I don't mind paying.
I've been a 1P user since before 1.0.
It's too easy to always try to squeeze every penny out of these small companies, but I think it's worth really thinking hard about their reality, and how much their software is actually worth to us.
Re: Safari 13 Is Out
#76Earlier quoted context omitted.
What's a "proper" extension? The only things in the release notes seem to be about broadening the API somewhat.
They did not just broaden the API. Previously, extensions were written in Javascript, roughly following open web standards[0]. This let you write your extension (nearly) once and have it work in all web browsers. Now, all of those Javascript extensions are deprecated (users can no longer install them). If you want your extension to work, you now have to rewrite the majority of it from scratch in Swift[1] [0] https://…
Thanks for this information. How do the capabilities of the new API differ from the old one? If a developer is willing to put in the effort to do what Apple says, what extra capabilities do users get, and what existing capabilities are taken away?
I'm not asking about ad- / content-blockers, because that issue has been discussed many times and there's no value in rehashing that discussion. I'm asking about OTHER TYPES of extensions.