It really isn't. I mean, at a very basic addressing level, sure, IPv4 addresses and IPv6 addresses are just a sequence of octets. But at a network infrastructure level they are quite different, and IPv6 is (conceptually) designed for large-scale, hands-off deployments. See: SLAAC, NDP, DAD, GUA/ULA/link-local address scopes, unicast vs. multicast vs. anycast, etc.
Thread is also IP(v6)-based. But in this context, Thread would go a fair ways toward solving stavros's concern, as it means security could be enforced on the Border Router(s), rather than each individual device.
It's possible that the WSL kernel has that code compiled-in rather than as a loadable module. If they ship the kernel config somewhere, you could verify with
Using bpftrace to watch calls to module_request, openat, etc., it looks like when the kernel calls modprobe, it doesn't even look at the disable-algif.conf file:
Restart WSL2, run the bpftrace, and try `sudo modprobe algif-aead`, and that shows it looking at (or I guess opening) other files in /etc/modprobe.d, including the new one.
> The branch itself gets created with the ticket number and everything follows from that, there's no extra effort.
Only problem there is the potential for a deeply-ingrained assumption that the Jira key being in the branch name is sufficient for the traceability between the Jira issue and commits to always exist. I've had to remind many people I work with that branch names are not forever, but commit messages are.
Hasn't quite succeeded in getting everyone to throw a Jira ID in somewhere in the changeset, but I try...
I think most of the battery life improvement is the much more power-efficient SOCs available. The original Pebble used an STM32 processor and a TI Bluetooth chip, where nowadays having BLE integrated into the SOC is table stakes.
Did you get it in black like I did? My buttons also cracked practically right away (within a day), I suspect because the reinforcements were installed poorly (the buttons are VERY hard to press). It made the down button unusable.
But kudos to Eric and Claudio, they're shipping me a replacement (in white, which, as I understand it and as they said in their email, should be less susceptible to the issue, something about the white rubber versus black makes it less problematic). My only frustration was how quickly it failed, since I know it's a new-old-stock case.
Highly looking forward to the Time 2. I only stopped using my Pebble Time Steel when the battery life degraded to ~3 days (after about 6 years), used a Fossil Hybrid for a few years, now a Pixel watch. Measuring battery life in weeks will be a breath of fresh air :)
[0]: https://en.wikipedia.org/wiki/2025_in_spaceflight#Orbital_la...
[1]: https://en.wikipedia.org/wiki/2026_in_spaceflight#Orbital_la...
Edit: mistyped 317 as 313