Earlier quoted context omitted.
If that's the case, how does the Github app work on iOS?
Differential enforcement.
Apple’s App Store enforcement is very arbitrary. For example, if the app developer offends steve jobs, you’re banned for life.
IPv6 traffic crosses the 50% mark
221–230 of 643 posts
Re: IPv6 traffic crosses the 50% mark
#222Great, then another 20 years and we can retire IPv4.
Re: IPv6 traffic crosses the 50% mark
#223If GitHub flipped a switch and enabled IPv6 it would instantly break many of their customers who have configured IP based access controls [1]. If the customer's network supports IPv6, the traffic would switch, and if they haven't added their IPv6 addresses to the policy ... boom everything breaks. This is a tricky problem; providers don't have an easy way to correlate addresses or update policies pro-actively. And cu…
If you can't handle sites switching to ipv6 in 2015 (ten years ago) your security plan is garbage.
Re: IPv6 traffic crosses the 50% mark
#224It's only a matter of time before laptops get 5G. Macbooks have been rumoured for a while to get cellular modems. [1] This will probably help adoption. On the one hand it will generate more IPv6 traffic. On the other hand it will expose more developers to IPv6; which will expose them to any lack of support for IPv6 within their own products. [1]: https://9to5mac.com/2025/08/14/apples-first-mac-with-5g-cell...
I can't imagine a worse privacy nightmare. Always on backdoored baseband in 5G with a unique permanent IPv6 address assigned to the machine. Okay, maybe it could be worse if each user account is assigned its own unique IPv6 perma-cookie.
You're thinking of MAC addresses. Machines don't have permanently-assigned v6 addresses, rather the IP is assigned by whatever network they're currently attached to and will change based on that network's whims, just like it does in v4.
Re: IPv6 traffic crosses the 50% mark
#225It has barely hit 50% and it's already plateauing. This adoption rate is ridiculous despite basically all network interfaces supporting it. I thought I would see IPv6 take over in my lifetime as the default for platforms to build on but I can see I was wrong. Enterprise and commercial companies are literally going to hold back internet progress around 60 to 75 years because it's in their best interest to ensure users…
ISPs often fail to do this because there is always someone in the hierarchy who says, "nobody is demanding it."
I with I knew how to get through that I want it. I'm supposed to be a tech guy - that means I need experience with the latest tech in my house
Re: IPv6 traffic crosses the 50% mark
#226Just in time for ipv8 - https://www.ietf.org/archive/id/draft-thain-ipv8-00.html
Re: IPv6 traffic crosses the 50% mark
#227Earlier quoted context omitted.
They supported IPv6 for a short time, but then stopped their experiment. An excellent reason to move away from Github, I find.
I've been there. Management was fine with the testing but it added too much overhead for nearly no benefit to us. One more thing to troubleshoot at 3 am, one more thing to teach to a disinterested tier 1 support team, one more thing for Chrome to be weird about, hundreds more rules to manage in a hostile load balancer, logging tools that don't understand ipv6. Turned it off. End customer asked why the site got a litt…
One of the big challenges with IPv6 remains that many of the knows-just-enough-about-networking people, like support staff, often never received any IPv6 training (or, for that matter, even enough IPv4 training that they don't need to Google things that come up in real life). Another is that the weird, awful, everyone-hostile corporate "solutions" often break IPv6 in stupid ways (like load balancers and logging tools being unable to cope with minor changes and requiring a full configuration rework).
Things have definitely gotten better over time, though. The massive 90s style corporate networks will probably never transition, but smaller and more modern companies don't have that issue.
Apple mandating that apps are IPv6 compatible and various government legislation forcing companies to make their shitty middleware IPv6-compatible has improved things quite a bit so far. As uptake keeps rising, the need for technologies like STUN and TURN will slowly start decreasing, and as a result more and more people will end up in "untested" situations where not having IPv6 and falling back to legacy paths starts becoming a problem.
Re: IPv6 traffic crosses the 50% mark
#228If GitHub flipped a switch and enabled IPv6 it would instantly break many of their customers who have configured IP based access controls [1]. If the customer's network supports IPv6, the traffic would switch, and if they haven't added their IPv6 addresses to the policy ... boom everything breaks. This is a tricky problem; providers don't have an easy way to correlate addresses or update policies pro-actively. And cu…
Thanks to the trend to SASE like Palo Alto GlobalProtect or ZScsler this practice is not a good idea anymore. Speaking of ZScaler, they are still IPv4 only, right?
Re: IPv6 traffic crosses the 50% mark
#229Re: IPv6 traffic crosses the 50% mark
#230Earlier quoted context omitted.
The big reason is that domestic ISPs don't want to switch (not just in the US, but everywhere really.) Data centers and most physical devices made the jump pretty early (I don't recall a time where the VPS providers I used didn't allow for IPv6 and every device I've used has allowed IPv6 in the last 2 decades besides some retro handhelds), but domestic ISPs have been lagging behind. Mobile networks are switching en m…
Except that is completely wrong. Consumer/residential networks have significantly higher ipv6 adoption rates that corporate/enterprise networks. That is why you see such clear patterns (weekend vs weekday) in the adoption graphs.
There are still a lot that have not.