Yes but only not in the course of their federal duties.

Nope

They are lying about it not being a cost cutting exercise

That's exactly right. Bad leadership got them here. Of course they won't suffer, but their employees will. But only because they announced it as AI related. So the investors don't care.

Oh yeah, AI is just an excuse to sell it to the public. But it's not about that at all. It's about bad leadership.

Yikes. That's bad leadership at that top all around. But we already knew that when they announced layoffs. No good leader lays people off.

In hindsight though, and really also in foresight, it didn't work out that way.

> What? I have never seen this.

What? Never? Is extremely common. I just checked both my Mac and Windows desktops and they both show a link local gateway.

It makes me question whether you've used IPv6 all that much.

Every single machine I use, both at home and at work, has IPv6. Exactly none of them use a link-local address as the gateway address.

>> IPv6 has some quirks that make it harder to digest. > Almost every point in your list is wrong.

You missed the point and almost every counterpoint in your list is wrong.

>> - link local gateway address, makes it hard to understand why the subnet does not have a gateway from the ssme address space >IPv4 has link-local addresses, too. Those are the 169.254.X.X addresses that you see on Windows machines. IPv6 adds nothing new.

That's not what the OP said. Note it says gateways. IPv4 when DHCP'd will show 192.168.1.1 for example when it has a 192.168.1.55 address. IPv6 will show fe23::166:8f2c:9a21:96de when it has a 2001:921:61c:aef:78f:7190:1ca2 address, despite the gateway actually being 2001:921:61c:aef::1. So its highly confusing for no good reason.

>> - privacy extensions: it is very hard to explain to people why they have 3-4 IPv6 addresses assigned to their computer > Well then, don’t use them. Configure the machines with one address each, just like before. If you want the (arguable) advantages of the privacy extensions, they are available, but not mandatory.

While you can configure not use them, by default DHCP'd devices WILL have a bunch. Again confusing for no good reason.

>> - no real tentative mapping to what people were used to. Every IPv6 presentation I did had to start with “forget everything you know about IPv4” > That’s the complete opposite of my experience. Almost everything in IPv6 works exactly the same as with IPv4.

It's the complete opposite experience for most people, including network engineers.

For me, the journey is more important than the destination. Using coding assistance takes all the fun out of it, as well as the learning. (Not to mention adding aggravation of dealing with prompts and figuring out whether the response is correct or not).