throw0101a

> I want to switch to fully native IPv6 without changing any of my addresses. There's no reason this should be impossible.

… except for the fact that you have to have completely new data structures and packet format to fit more address bits, and once you change the structures you need a new version field so any gear that sees a packet knows where to use the old code paths or new ones.

Then you're at the point where you have to push new code everywhere to handle these changes, and some nodes will have only the old code and some the new code, so now you're into translation and/or tunnelling to make sure the old addresses can talk to new addresses. Depending on their risk tolerance, some operators will enable the new code and some will not.

You also have to update DNS with new records, as A records are hard-coded to 32 bits. So now you're updating DNS libraries and user land.

There is no way to expand address space without going through all the same issues as what we call "IPv6" (originally SIPP) has gone through.

* https://github.com/becarpenter/misc/blob/main/why6why.md

> Yes it's 3A. They didn't need to make the new protocol have separate state from the old one.

Except there will be a period of time when many 'network elements' (routers, firewalls, servers (web, SMTP, DNS, etc), clients) will not be updated for the new protocol so you may also need 3B.

And this will be true for any IPng, and not just the one that just happened to be chosen to be for "IPv6" (which was SIPP, over CATNIP and TUBA; see RFC 1752).

> Let me keep my old address on the new protocol.

You can/could. You can encourage people who have addresses in the older protocol to use the new one with "free" "automatic" address assignments in the new one to encourage translation and tunnelling:

> For any 32-bit global IPv4 address that is assigned to a host, a 48-bit 6to4 IPv6 prefix can be constructed for use by that host (and if applicable the network behind it) by appending the IPv4 address to 2002::/16.

> For example, the global IPv4 address 192.0.2.4 has the corresponding 6to4 prefix 2002:c000:0204::/48. This gives a prefix length of 48 bits, which leaves room for a 16-bit subnet field and 64 bit host addresses within the subnets.

* https://en.wikipedia.org/wiki/6to4

And the 'old' IPv4 addresses are available in the new IPv6 world:

> Addresses in this group consist of an 80-bit prefix of zeros, the next 16 bits are ones, and the remaining, least-significant 32 bits contain the IPv4 address. For example, ::ffff:192.0.2.128 represents the IPv4 address 192.0.2.128. A previous format, called "IPv4-compatible IPv6 address", was ::192.0.2.128; however, this method is deprecated.[5]

* https://en.wikipedia.org/wiki/IPv6#IPv4-mapped_IPv6_addresse...

There is no way around this limitation: you must have a separate network space because of physical limitations.

Your supposed solution, and many others, have been thought of already. Have been tried. You are not thinking of anything new in your proposal.

As a Canadian I have no idea what 72˚F means or feels like: is it warm or cold? I do know what 22˚C feels like and how to dress for it. How "intuitive" a temperature number is completely learned behaviour and cultural acclimation.

Pounds vs kg: see above. All the non-American people seem to have "intuitive" grasp of metric measurements.

> 0-100 MPH lines up well with car speeds, which is usually the thing you're measuring with that. KPH is excessively granular for that. Probably not by design, but yeah.

So 'more granularity' is good for temperature but not for speed. Got it.

> The feet/inches vs meters/cm thing matters less. It's base-12 vs base-10. You can do decimal feet or fractional meters of course, but it's less common, so apparently both ways are fine.

By "foot" do you mean 'regular' foot or survey foot:

* https://www.nist.gov/pml/us-surveyfoot

Because there are two different units in the US customary system, used for basically the same purpose, that use the same name. And the "foot" isn't the only unit like that:

* https://en.wikipedia.org/wiki/Pound_(mass)

* https://en.wikipedia.org/wiki/Pound_(force)

Here's another one: which weighs more, a pound of feathers or a pound of gold? A pound of feathers. Because feathers use one 'pound-system' [1] and is 453g, while gold uses another pound-system [2] and is 373g. But of course an "ounce" of gold (31g) is more than an "ounce" of feathers (28g), because Troy is 1/12 of pound but Avoirdupois is 1/16. In addition to the above "ounces" there is also "fluid ounces".

[1] https://en.wikipedia.org/wiki/Avoirdupois

[2] https://en.wikipedia.org/wiki/Troy_weight

> The nice thing about imperial (as well as the customary system used in the US) is that it's based on measurements that people have found useful over thousands of years. They're human units, adapted to what people need to do with them, not the other way around.

US customary is not "thousands" of years; temperature (Fahrenheit) only came out in 1724 for example, and many other units were only standardize much more recently:

* https://en.wikipedia.org/wiki/History_of_measurement#History...

* https://en.wikipedia.org/wiki/System_of_units_of_measurement...

Second, even with-in the system itself there was also sorts of inconsistencies. Until just a few years ago there were two "foot" units; one was recently retired:

* https://www.nist.gov/pml/us-surveyfoot

Here's another one: which weighs more, a pound of feathers or a pound of gold? A pound of feathers. Because feathers use one 'pound-system' [1] and is 453g, while gold uses another pound-system [2] and is 373g. But of course an "ounce" of gold (31g) is more than an "ounce" of feathers (28g), because Troy is 1/12 of pound but Avoirdupois is 1/16. In addition to the above "ounces" there is also "fluid ounces". And let's not forget about the third system [3], which got replaced by… the metric system in 1971.[4]

[1] https://en.wikipedia.org/wiki/Avoirdupois

[2] https://en.wikipedia.org/wiki/Troy_weight

[3] https://en.wikipedia.org/wiki/Apothecaries'_system

[4] https://en.wikipedia.org/wiki/United_States_Pharmacopeia

Also:

* https://en.wikipedia.org/wiki/Pound_(mass)

* https://en.wikipedia.org/wiki/Pound_(force)

> Think about it. Imagine you were never taught a measurement system. You find yourself needing to come up with a unit to make measurements for wooden planks you're going to use to build a house. Would you choose a unit as long as a meter? Or one as short as a centimeter or even a decimeter?

Millimeters. That single unit gets you down to very small scales (finer than 1/16") and to large lengths: four significant digits (9999mm) gets you to the equivalent of >32' (~11yd).

* https://web.archive.org/web/20200516223819/https://themetric...

As evidence for this Australia/NZ/EU do everything in millimetres in construction.

> […] but it's based on the original mistake of making it an entirely separate network from v4 with new address blocks.

This was not a "mistake":

      So it's a matter of mathematical and physical fact that to expand
      the address size, you must change the protocol, and that means 
      [three] things immediately:

            You have to change the version number.

            You have to add new code to handle the new version.

      […]

            You need a coexistence technique so that updated systems, 
            with the new protocol, can connect to old systems that know 
            nothing of the new protocol.

      Two minutes of thought show that this third requirement has only 
      two solutions:

            (3A) Dual stack, in which the new machines speak both 
                 the old (IPv4) and new (IPng) protocol.

            (3B) Translation, in which something translates addresses
                 between the old and new protocols.

* https://github.com/becarpenter/misc/blob/main/why6why.md

* https://datatracker.ietf.org/doc/html/rfc1671

> All they needed to do was add a couple more dots onto IPv4 and maybe switch to hex.

There is no 'just' extending the address length:

      So it's a matter of mathematical and physical fact that to expand
      the address size, you must change the protocol, and that means 
      [three] things immediately:

            You have to change the version number.

            You have to add new code to handle the new version.

      […]

            You need a coexistence technique so that updated systems, 
            with the new protocol, can connect to old systems that know 
            nothing of the new protocol.

      Two minutes of thought show that this third requirement has only 
      two solutions:

            (3A) Dual stack, in which the new machines speak both 
                 the old (IPv4) and new (IPng) protocol.

            (3B) Translation, in which something translates addresses
                 between the old and new protocols.

* https://github.com/becarpenter/misc/blob/main/why6why.md

* https://datatracker.ietf.org/doc/html/rfc1671

You also have to update DNS to create new resource record types ("A" is hard-coded to 32-bits) to support the new longer addresses, and have all user-land code start asking for, using, and understanding the new record replies. Just like with IPv6. (A lot of legacy code did not have room in data structures for multiple reply types: sure you'd get the "A" but unless you updated the code to get the "A+" address (for "IPv4+" addresses) you could never get to the longer with address… just like IPv6 needed code updates to recognize AAAA, otherwise you were A-only.)

In any 'address extension' plan the legacy code cannot use the new address space; you have to:

* update the IP stack (like with IPv6)

* tell applications about new DNS records (like IPv6)

* set up translation layers for legacy-only code that cannot be update to reach extended-address-only destination (like IPv6 with DNS64/NAT64, CLAT, etc)

> IPv6 is dead. Nobody cares about it.

Except for everyone on T-Mobile US:

* https://www.youtube.com/watch?v=d6oBCYHzrTA

Or all of FaceMeta's internal infrastructure:

* https://engineering.fb.com/2017/01/17/production-engineering...

Or 86% of France:

* https://www.google.com/intl/en/ipv6/statistics.html#tab=per-...

> For TechSavvy I believe it was dynamic /64 by default but static /56 for free on request.

"On request" meaning you told your CPE equipment to send a DHCP-PD packet, i.e., you didn't have to call them and ask for something special with your account.

> Well, there is; you can just wait for more helium to be produced underground.

Funnily enough that seems to be the same idea for petroleum. :)

> Even with Germany it turned out that Angela Merkel did grave mistakes and Germans were able to find out about those only after she left office. Being continually in office gives you the ability to hide your trials.

A "required absence" is a thing in a number of sensitive positions, especially financial/regulated industries.

> I think you're missing the mark by putting the blame on morals while ignoring actions such as Reagan dismantling unions and removing accountability from news reporting

Also cutting tax rates and encouraging 'pass-through' S-Corps, the latter of which really helped many people skirt taxes:

* https://archive.is/https://www.newyorker.com/magazine/2026/0...

* https://phys.org/news/2026-10-private-business-fortunes-reve...

* https://us.macmillan.com/books/9781250378507/theeverywheremi...

In the late 1990s, under Clinton, the US was in a fiscal position such that people were worried about US Treasuries (bonds) not being available anymore because of surpluses. Then there was Bush (wars, tax cuts), the GFC, Trump 1.0 tax cuts, Trump 2.0 tax cuts: and people are wondering how the US can solve its fiscal mess? How about you go back to 1997 (tax rates), the last time this was a non-issue.

While tech bros and Wall Street may get a lot of press of getting lots of money, the recent book The Everywhere Millionaire: Who Is Really Rich in America and How They Got There seems to show (using IRS data, etc) a large portion of the wealth being held in private hands.

Interview on Bloomberg's Odd Lots:

> In 2014, the economists Owen Zidar and Eric Zwick were asked by the Treasury to conduct a study on the tax burden of private business owners. It was tricky to figure out how much these sorts of business owners — auto dealers, contractors, the like — actually owed in taxes: After Reagan's 1986 tax reforms, pass-through businesses and other accounting tricks became widespread enough to obscure this class of wealthy Americans hiding in plain sight. The research they conducted led to their new book The Everywhere Millionaire: Who Is Really Rich in America and How They Got There, and one of their central findings is that there are about three million private business owners who have an average wealth of around $25 million. They call this group “Main Street Millionaires” and their influence on the economy and politics in the US is considerable. We speak with Zidar and Zwick today about how they measured the actual number of rich people in America by sifting through reams of tax forms, why income inequality started to rise in tandem with the growing number of pass-through businesses, and how it's possible that the collective revenue of the nation's dentists far exceeds that of the NFL.

* https://www.youtube.com/watch?v=dh7A2VyveUw

* https://podcasts.apple.com/us/podcast/theres-a-mind-boggling...

* https://omny.fm/shows/odd-lots/theres-a-mind-boggling-number...

* https://open.spotify.com/episode/3wFRjaeUQOiNmlYYTwhwRf

(Lots of other interviews as well as the book just came out a few months ago, so the authors did a book tour.)

Some take aways from the books:

> According to Zidar and Zwick, Main Street Millionaires hold over 13x more wealth than the Forbes 400. And where do they hold it? In pass-through entities (like LLCs and S-corps) in various industries. Which industries in particular? Zidar and Zwick note that the top five are:

> 1. Legal services. This is mostly law firm partnerships.*

> 2. Financial investment activities. This includes venture capital, private equity, and hedge fund managers.

> 3. Auto dealers. These are the local, independently owned dealerships that sell new and used cars.

> 4. Professional and technical services and management consulting. This includes independent consulting firms and other specialized professional practices.

> 5. Oil and gas extraction. This includes fracking companies in North Dakota, Pennsylvania, and other states.

* https://ofdollarsanddata.com/who-is-really-rich-in-america/

An interesting observation: a radiologist working at a hospital may make much less if they're an employee of the hospital, versus something like a 'consultant' who use an pass-through S-Corp at the same hospital doing the same work.

> We convince ourselves we need phones, but I promise you, they are optional.

Many people's employer's use of MFA (including my own) says otherwise.

For many people ensuring their spouse and/or their children's school be able to reach them for emergencies and sudden matters says otherwise. Or an elderly parent (e.g., location tracking).

> Would you say the same thing about Anthropic defining the terms of use of its technology to the military?

No. With Anthropic (AIUI) the terms of use were agreed to beforehand. With Starlink things were changed suddenly on a whim.

If Starlink doesn't want to be involved with military operations, then put that in the ToS, and Ukraine cannot / will not use it for that.

But Starlink agreed to the use — especially with defence-only operations which were part of the agreement, and what was being done — and suddenly yanking capabilities basically means aiding the murder of civilians.

> In a normal world, this would be treason by an illegal immigrant to the US.

As other comments have stated, this is not treason. However, a private individual/citizen should not have the ability to dictate national security policy:

* https://paulkrugman.substack.com/p/its-time-to-take-starlink...

> Because /s is stupid […]

It's the best 'defence' against Poe's law that we have:

* https://en.wikipedia.org/wiki/Poe%27s_law

> It's not that secure anyway, as evidenced by the multiple 1-click exploits going around on X this week.

Anyone know if those exploit(s) worked on iPhones with Lockdown Mode enabled?

* https://support.apple.com/en-ca/105120

* https://arstechnica.com/tech-policy/2026/02/fbi-stymied-by-a...

> The fact so many technical people believe that security and freedom are mutually exclusive, and pay for that lie, is proof the Apple propaganda is working exactly as intended.

My Aunt Millie's iPhone is secure against herself because she can't install random garbage off the Internet and is in a walled garden.

As someone who works in IT: users are often their (and their organization's) own worst enemy. We've tried training and blacklisting (with anti-virus) for decades, and it appears that whitelisting and locking things down is what actually works.

I'd be happy with a 'compromise' where there's a factory reset where you can install your own code but it blows an e-fuse to indicate that device is no longer 'OEM certified secure' state.

David Byrne was recently on, of all things, Bloomberg's Odd Lots podcast:

> History is littered with ideas that have been tossed aside, only for them to gain relevance at some later date. Think of Moby-Dick: forgotten in Melville's time, but now regarded as the great American novel. Or the work of economist Hyman Minsky, which became influential a decade after his death, when the 2008 financial crisis made “the Minsky Moment” a mainstream term. These are just a couple of the things we talk about with the legendary musician David Byrne on today's podcast. Byrne's new book, Sleeping Beauties: Why Good Ideas Go Dormant and How They Wake Up, looks to categorize numerous “sleeping beauties” — ideas that were lost but then rediscovered. Besides Melville and Minsky, we also talk about the lost Roman recipe for concrete and we get into Byrne's thoughts on how to write a song and his own experience of having his music rediscovered by a new generation.

* https://www.youtube.com/watch?v=U3x7aZ11WT4

* https://podcasts.apple.com/us/podcast/david-byrne-explains-h...

* https://omny.fm/shows/odd-lots/odd-lots-david-byrne-v1

"Old Music Friday":

* https://www.instagram.com/owencutts/reel/DejK_APRynG/

> One of my absolute favorite bands is a random street band I stumbled across in New Orleans some years ago, called Yes Ma'am.

If we're talking street performers, Lucky Chops et co laying it down in Herald Square (NYC); "Funkytown / I Feel Good":

* https://www.youtube.com/watch?v=-km8p6rb_EY

* LC's official video, but I don't think the audio is as good as above: https://www.youtube.com/watch?v=da-wrSJaV-E

> https://www.instagram.com/reels/C9h9xpNOoEN/

Source is "The Real Reason Why Music Is Getting Worse" from 2024:

* https://www.youtube.com/watch?v=1bZ0OSEViyo&t=1m50s

* Found via transcript search for "fool in the rain": https://filmot.com/search/fool%20in%20the%20rain/1?channelID...

Also similar "HOW WOULD JOHN BONHAM SOUND TODAY? (Quantized)" from 2019:

* https://www.youtube.com/watch?v=hT4fFolyZYU

> why would you need to destroy anything if there's pardons involved.

To prosecute people guilty of state-level violations (which are not covered by Presidential federal-level pardons). To find 'collaborators' (and perhaps prosecute them, as it may difficult to pardon 'everyone'). To know what happened to perhaps help prevent it happening again in the future.

Well:

    There are actually only two hard problems in computer science:
        0) Cache invalidation
        1) Naming things
        4) Asynchronous callbacks
        2) Off-by-one errors
        3) Scope creep
        6) Bounds checking

* https://news.ycombinator.com/item?id=38806257

Also: https://martinfowler.com/bliki/TwoHardThings.html

> These are the Meta-owned ranges I'm blocking now, in case it helps anyone: 57.141.0.0/16, 57.142.0.0/15, 57.144.0.0/14, 57.148.0.0/15

What's Meta's ASN? May be simpler to just null-route the entire organization.

Another article/discussion from ~year ago on doing the same thing, "Native Secure Enclave backed SSH keys on macOS":

* https://news.ycombinator.com/item?id=46025721