Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dwaite
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
74 ms
·
961.
▲
by
dwaite
4y ago
Mini USB was terrible, and would typically fail well below 1,000 on the device side. Mobile phones might not make it through their first year with a mini usb port back in the day, depending on how many times a day someone attached it to a c
962.
▲
by
dwaite
4y ago
The good news is that all functional USB-C cables will generally charge at 30W. They might not be able to go above 30W, they might only have USB 2.0 speeds. The USB-IF has only just now come up with IMHO their first passable attempt at labe
963.
▲
by
dwaite
4y ago
People expect to be able to charge the headphones they use for their phone the same manner they charge their phone. I suspect they'll be quick to change over such accessories once they change the phone port - they have had several smal
964.
▲
by
dwaite
4y ago
I suspect that Apple has been in progress of moving things over to USB-C for a while (see the recent Apple TV and iPad changes). They have already moved off of USB-A chargers completely, moving onto USB-C chargers. My understanding is they
965.
▲
by
dwaite
4y ago
If your device has limited network connectivity, it can create new passkeys or use a passkey it already has for interacting with a service. However, it won't be able to synchronize new credentials with any cloud service in multi-device
966.
▲
by
dwaite
4y ago
The platform is often managing things, sometimes with Chrome and the platform splitting responsibilities when the Chrome team adds support for additional options. So the ability to see or manage passkeys will unfortunately vary by platform,
967.
▲
by
dwaite
4y ago
Firefox is unfortunately a behind on support for this technology. I believe at least one password manager (Dashlane) has shipped a web extension that would polyfill the missing bits on Firefox. Unfortunately, passkeys.io as a demo falls bac
968.
▲
by
dwaite
4y ago
1Password and Dashlane have announced support via web extensions. I also really hope we have future platform-level support, so that third party "passkey managers" will work outside of the browser (such as on mobile, within all nat
969.
▲
by
dwaite
4y ago
webauthn.io has recently been revamped to support more of the 'passkeys' behavior, such as conditional UI (the password manager/form-fill-like behavior added in certain browsers). webauthn.me has a developer tab that lets you
970.
▲
by
dwaite
4y ago
The use-case is to create a new key pair when you register an "authenticator" device, and then sign a challenge later to authenticate (prove it is the existing known authenticator). It is up to the site to decide if it wants to ac
971.
▲
by
dwaite
4y ago
You register a device (authenticator), which generates and registers a new public key. You show up with that again in the future, which answers a challenge by using the private key. So it's just saying "I'm the same device as
972.
▲
by
dwaite
4y ago
Yubikey is included - as a passkey. They are more secure because they are different per-site and are public-key-based rather than secret-based, so they can't be captured and replayed later, a website compromise doesn't lead to fur
973.
▲
by
dwaite
4y ago
There are yubikeys with biometric readers. The reason they are referred to as PINs rather than passwords is that they are locally set and entered, without being shared with external network systems. Since they are being used to augment the
974.
▲
by
dwaite
4y ago
> I'm curious if resetting a PIN or password on Windows or macOS or iPhone OS would retain the Passkey identities. I suspect it would... Depends on the process for changing the PIN/password. The desktops may have an option to l
975.
▲
by
dwaite
4y ago
1Password and Dashlane have web extensions which replace any integrated browser support with their own UX and functionality. I do not know the current release state of those extensions. I personally hope there is more of an 'officially
976.
▲
by
dwaite
4y ago
The email and passcode is part of the site registration flow for this particular site (e.g. registration requires a verified email address). Other demo sites like webauthn.io do not attempt to add a 'real' registration flow. My gu
977.
▲
by
dwaite
4y ago
Yep! As a user registering an authenticator with a typical site, the authenticator creates a public/private key pair and returns the public portion. Using it later tells the site it is the same authenticator as last time, without optio
978.
▲
by
dwaite
4y ago
The copy operation (⌘C) has an optional variant (⌥⌘C) which copies the pathnames to the clipboard as text rather than copying file references. This will copy either the directory (if no selection) or the selected file(s). If you enable the
979.
▲
by
dwaite
4y ago
Finder should show changes immediately except on certain external filesystems. It gets kernel events on directory and file changes (the same mechanism Spotlight and Time Machine use). This bites me on fake FAT filesystems over USB for hardw
980.
▲
by
dwaite
4y ago
> Moving files is unintuitive. It should be [cmd+x] then [cmd+v]. Instead it's [cmd+c] then [option+cmd+v], and this behavior is not afforded in the UI, you just have to look it up somewhere. Apologies, but what do you expect to hap
981.
▲
by
dwaite
4y ago
I find a lot of people proposing this, like apple is just going to remove the ports in an immature act of spite. In reality they will go for much more mature acts of spite, like ramp down data and power capabilities for "safety reasons
982.
▲
by
dwaite
4y ago
Yes, the iPad Pro was capable of 5 Gbps over its lightning port. They had at least one accessory which used it (to give you a USB-A host port). Considering the nightmare of USB-C cable specs, I don't really fault them for not releasing
983.
▲
by
dwaite
4y ago
micro and mini USB both had three variants - A, B, and A/B - as part of USB OTG (On the Go). This is because they wanted you to be able to connect a computer to a camera, but also to be able to connect that camera to a printer.
984.
▲
by
dwaite
4y ago
> The USB Implementers Forum people are partly why we're in this mess. IMHO it really is. For the first releases of power delivery, the IF decided to _not_ go with Apple's existing system that they developed to negotiate chargi
985.
▲
by
dwaite
4y ago
One trick is to know that spotlight indexes content and metadata separately, and most search interfaces default to content. Typing in "README.md" in system spotlight will look for documents that contain a reference to that name, w
986.
▲
by
dwaite
4y ago
I think the biggest challenge here is getting the resources through the browser - e.g. enough memory to run a decent container, or the ability to open a listening port.
987.
▲
by
dwaite
4y ago
> The rules also state that the path to reject those cookies must be as easy as it is to accept them, so if they have "accept all" button, they are required to also provide "reject all" button, that has similar visibi
988.
▲
by
dwaite
4y ago
Speaking for myself - Red Hat's package manager cratered on an upgrade in the past (early 2000s) when it ran out of user space, and my investigation was that I hit a pretty core issue with the package manager design itself. Since it is
989.
▲
by
dwaite
4y ago
These are all implementation decisions, since behind-the-scenes this is all just Web Authentication API. That also means if you dislike the idea of some big company holding all your keys in cloud backed-up vault, you can just use one of the
990.
▲
by
dwaite
4y ago
I can register an authenticator multiple times, for instance to represent multiple different accounts of my own, or represent multiple people on a shared device. If I delete a credential, the expectation is that registering a new credential
More ›