Just Fucking Use IPv6
Comments on “Just Fucking Use IPv6”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Robin argues in an opinionated personal essay that teams should adopt IPv6, keeping a dual-stack CDN edge for IPv4-only users and using NAT64/464XLAT for IPv4-only dependencies. The case is that IPv6 removes the stacked NAT between clients and services and offers cheaper address space than IPv4, where a /24 reportedly costs $5,000–$10,000. Only the Microsoft example, which cites private-range overlap and 10.0.0.0/8 exhaustion, is sourced. The adoption figures (APNIC 43%, Google 50%) and the claims on mobile networks and CDN pricing are unsourced.
Why it ranked
No. 17 of 46 with a score of 0.58. The panel rated it highest on audience breadth (0.77) and practical relevance (0.76), lowest on substantiated (0.47). The judges disagreed most on new information (spread 0.70), so the story is marked contested. Placed No. 17, No. 38 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Opinionated advocacy piece on IPv6 adoption with real technical substance on NAT and addressing, but a profane polemic with little new information and some overstated claims.
- AI judgeJudge 3gpt-5.6-luna
- A technically informed, actionable argument for IPv6 adoption, with useful deployment details and quantitative context. It is opinionated and occasionally overstates benefits or simplifies operational and security trade-offs.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.58total under rubric v2.3Contestedjudges differ by 0.70 on new information
- Significance0.48
- Reader interest0.65
- Audience breadth0.77
- Practical relevance0.76
- Substantiated0.47
- Technical depth0.68
- New information0.66
- Counts against: Promotional0.05
- Counts against: Overclaim0.49
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.50 | 0.35 | 0.58 | 0.48 | 0.23 | +0.24 | +0.114 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.54 | 0.60 | 0.82 | 0.65 | 0.28 | +0.26 | +0.170 |
| Audience breadthHow many people who build technology does it concern? | 0.90 | 0.70 | 0.72 | 0.77 | 0.20 | +0.13 | +0.101 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.80 | 0.70 | 0.78 | 0.76 | 0.10 | +0.22 | +0.167 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.33 | 0.45 | 0.62 | 0.47 | 0.29 | +0.05 | +0.023 |
| Technical depthHow technically substantive is it? | 0.75 | 0.60 | 0.68 | 0.68 | 0.15 | +0.05 | +0.034 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.89 | 0.20 | 0.90 | 0.66 | 0.70 , above the contested threshold | +0.05 | +0.033 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.08 | 0.05 | 0.01 | 0.05 | 0.07 | −0.19 | −0.009 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.53 | 0.35 | 0.58 | 0.49 | 0.23 | −0.11 | −0.054 |
| Sum of contributions | +0.580 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.580 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-09/17/"><img src="https://rubric.hrih.si/badge/2026-11-09/17.svg" alt="Ranked #17 on Rubric, 9 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 1 matches source · 6 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Matches sourceCausal conclusion
Microsoft has been struggling with overlapping private address ranges and exhaustion of 10.0.0.0/8, which is one reason it is moving to IPv6 internally.
The cited source says the same thing.
The article says “Microsoft has been struggling with both of these things, which is one of the reasons they’re moving to IPv6 internally”
The source says “Microsoft IT has exhausted almost all RFC1918 space. There are small discontiguous pockets remaining, but not enough for our current and future needs”
Source cited by the article: labs.ripe.net/author/mirjam/ipv6-only-at-microsoft
No source givenNumber
IPv4 has 3.7 billion addresses dedicated to global unicast, far fewer than the number of networked devices in the world.
The article gives no link or citation for it.
The article says “IPv4 has 3.7 billion addresses dedicated to global unicast, a hell of a lot less than the number of networked devices in the world”
The source says No source to compare with.
Couldn’t checkNumber
An IPv4 /24 costs about $5,000–$10,000.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “an IPv4 /24 costs about $5,000–$10,000”
The source says No passage could be compared.
Source cited by the article: dreamstation.systems/personal/arin410.html
No source givenCausal conclusion
IPv4 address scarcity has led to NAT and to scarcity-driven pricing of addresses.
The article gives no link or citation for it.
The article says “This has led to both NAT, and a scarcity of fucking numbers”
The source says No source to compare with.
No source givenGeneralization
RIRs are still handing out IPv6 space at no charge on top of the annual service fee.
The article gives no link or citation for it.
The article says “RIRs are still handing out gobs of IPv6 for no charge on top of your annual service fee”
The source says No source to compare with.
No source givenNumber
APNIC estimates global end-user IPv6 capability is around 43%, and 50% of Google clients are on IPv6.
The article gives no link or citation for it.
The article says “APNIC estimates global end user capability is around 43%, and 50% of Google clients are on IPv6”
The source says No source to compare with.
No source givenGeneralization
Basically every mobile network is IPv6-only to the handset, using NAT64 and 464XLAT.
The article gives no link or citation for it.
The article says “Basically every mobile network is IPv6‐only to the handset, with NAT64 and 464XLAT carrying your laggard service”
The source says No source to compare with.
No source givenGeneralization
Almost every major CDN, transit provider and colo has had IPv6 for years and charges much less for it.
The article gives no link or citation for it.
The article says “almost every major CDN, transit provider and colo has had IPv6 for years and charges much less for it”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 5 pts, not on front page
Recorded for context only, checked 9 Nov 2026, 05:46 UTC. It played no part in the ranking.