growse

Alternatively, IPv4 simply does not scale effectively on the LAN, whereas IPv6 allows much simpler addressing and routing topologies. Simple = good.

My blog's hosted on either 3106689564 or 42540619367231808600192856535952785520 depending on your addressing scheme.

See, no colons in sight!

You're welcome to not use hex. For either addressing scheme.

You just have one big one on the root.

(Half joking).

Thank you for articulating.

> That passkeys come with some limitations, like oh by the way, now you're stuck paying Apple/Google/1password a subscription fee for the rest of your life, is merely a happy side effect for the corporation.

I see this, but I disagree with the conclusion for two reasons.

1) there's no evidence of this happening in the consumer passkey space despite enormous opportunity.

2) we already have instances of lock-in to services by service providers. Whether it's banks demanding you use their little weird dongle to login, or apple demanding you use an iDevice to use airtags or parental controls. This is, I agree, a problem. But the market seems to be working it out quite well

I disagree. TFA is extremely muddled in it's thinking, and the appeal to conspiracy is rather distracting from any good points that might exist.

Hence my question about "why though?". The only answer I can see is "user control", but I have no idea what that is. It sounds like a means, but to what end?

I don't understand what "Complete user control" means, or how it relates to passkeys?

Why though? What's the objective, and why are passkeys the easiest way to achieve that objective?

BigTech doesn't need attestations in the passkey spec to limit freedom.

Attestations were added so that highly specific domains where attestation is required (by law, a regulator etc.) can still use the same passkey spec as everyone else without having to invent their own thing.

If there was benefit to BigTech of locking in Auth to a specific device, they'd have done it long ago - it's not difficult.

Apple and Google don't need the passkey spec to mandate that you only use their services from non rooted Google/ Apple devices. They could do it before passkeys existed, and they can do that right now if they wanted to.

What's any of that got to do with passkeys and attestation?

Flags Wikipedia articles where the subject's parents also have Wikipedia pages. Draw your own conclusions.

A clock ticking every second is generating an event every second.

If you sample the CPU usage at 1Hz, the metric is attached to the tick event.

What I find confusing about this is that otel is two things.

1. A spec 2. A ref implementation

Similar to other projects (e.g. python), if there's complaints about (2), that should trigger an ecosystem of alternative implementations that are guaranteed to be compatible because of (1).

I suspect there's actually quite a few private, separate otel implementations. Maybe these just aren't being contributed as oss?