orangeboats

7 ms·

61.
by orangeboats 10mo ago
When something happens over IPv4 people treat it like "the Internet has malicious actors, water is wet", but when it happens over IPv6 it must be IPv6's fault. Sigh...
62.
by orangeboats 10mo ago
Compared to 0% like others? 50% is a very substantial retention rate.
63.
by orangeboats 10mo ago
Another day, another Godwin's law of networking. >It was doomed the moment you had to maintain two separate stacks Pray, tell me, how are we supposed to extend IPv4 with another {insert a number here} bits without creating a new pro
64.
by orangeboats 10mo ago
By being IPv6-only they are effectively making their users to preferentially connect over native IPv6 though. Personal anecdote, but once you have IPv6 setup properly (meaning your devices prefer IPv6 over IPv4) 70-80% of your internet traf
65.
by orangeboats 10mo ago
>CGNAT is nowhere near the common case yet. And frankly, I’m horrified that anyone’s describing it as a good thing. For some reason, "CGNAT == privacy" is a very common sentiment on Hacker News. Yeah, Hacker News. It's b
66.
by orangeboats 10mo ago
>IPv6 ... still hasn't taken over the world [after thirty years of deployment]." is a very different statement than "IPv6 has failed.". It's incredibly likely that the GP was referring to comments in this thread,
67.
by orangeboats 10mo ago
A single /32 IPv6 prefix is actually easier on the router (computational and memory wise) than a dozen /24 IPv4 prefixes.
68.
by orangeboats 10mo ago
>Also NAT is a pretty simple abstraction, it's literally a single table. ...And now, let's try punching a hole through this "simple" table. Oops, someone is using a port-restricted or symmetric NAT and hole punching h
69.
by orangeboats 10mo ago
>How? Why is using hex any more intuitive than binary or a md5 hash for anyone who doesn’t do networking for a living? Well, what is the address range for 192.168.0.0/27? That's also non-intuitive for a layman as well. In the e
70.
by orangeboats 10mo ago
Regardless of the prefix size, a subnet is always /64 in IPv6. A shorter prefix simply means you can have more /64 subnets.
71.
by orangeboats 10mo ago
Their IPv6 deployment rate saw a huge jump from 40ish% to 53% after this report though. https://stats.labs.apnic.net/ipv6/CN
72.
by orangeboats 10mo ago
Your goalpost already moved from "IPv6 just works" to "IPv6-only just works" though. ;) In all seriousness, I have IPv6 enabled and GitHub works just fine for me. Though at a slower speed sometimes because the IPv4 CGNAT
73.
by orangeboats 10mo ago
Can we put a stop to this weird obsession with attacking Pottering under _every_ systemd-related thread? Fine, we get it, you don't like him. Or you don't like systemd. Whichever it is, comments like yours often provide zero subst
74.
by orangeboats 10mo ago
>Why assume that a game has to be made? Well... the project calls itself a game engine. It's really not out of the world to make the assumption.
75.
by orangeboats 11mo ago
Clearly you have not visited China. Try it someday. You _will_ be surprised by some of the technologies there.
76.
by orangeboats 11mo ago
I find it very ironic that you are calling out sockpuppets when your name is literally "RustSupremacist" and your submission history is less than stellar.
77.
by orangeboats 11mo ago
This was posted less than 2 weeks ago. Why bother doing it again? https://news.ycombinator.com/item?id=45849204
78.
by orangeboats 1y ago
>Then any replacement project should start with implementing a better test suite in order to know what you're doing "Then any replacement project should not include bugs in their code." Like I said before, broad statements
79.
by orangeboats 1y ago
Congratulations to you on being the 10000th? person [0] to miss the point of unsafe/safe. 1. Unsafe doesn't mean the code is actually unsafe. It only tells you that the compiler itself cannot guarantee the correctness of it. 2. Un
80.
by orangeboats 1y ago
>You do coverage testing, which would have found the missing date -r path. The original coreutils test suite didn't cover the -r path. The same bug would have not been statically discovered in most programming languages, except pe
81.
by orangeboats 1y ago
> I can assure you that the core utils have all already went through static analysers doing more checks than the Rust compiler. Some checks are pretty much impossible to do statically for C programs because of the lack of object lifetime
82.
by orangeboats 1y ago
Do you really think your solution of "IPv4 with extra octets" will not introduce so called "broken everything"...? Whether it's the addition of one octet or twelve octets, you are nevertheless introducing a new Inte
83.
by orangeboats 1y ago
How is your proposal _materially_ different from today's NAT64 and the 64:ff9b::x.x.x.x prefix?
84.
by orangeboats 1y ago
Oh no, the Godwin's law equivalent for networking is proving itself once again. >someone will again complain about the address format, without realizing that shoving in extra address bits on an IPv4 datagram is already a new protoco
85.
by orangeboats 1y ago
Yes, but currently the decompressors we use (so things like zstd, zlib, 7z) come from a mostly-verifiable source -- either you downloaded it straight from the official site, or you got it from your distro repo. However, we are talking about
86.
by orangeboats 1y ago
Can't the decompressor still produce a malicious uncompressed file?
87.
by orangeboats 1y ago
That's the implicated solution to this problem, correct. But you have a bunch of people on HN opposed to it for no good reason other than "IPv4 works for me™".
88.
by orangeboats 1y ago
For any P2P protocols to work, including BitTorrent, you need to be able to access the other nodes. In today's world, that's becoming harder because everyone and their granny are gradually being hidden behind a strict CGNAT.
89.
by orangeboats 1y ago
Usually it all boils down to "aesthetics". I am pretty sure most would agree that Gall-Peters is atrocious looking!
90.
by orangeboats 1y ago
Sometimes it's not just "your code". Strings are often interchanged and sent to many other parties. And some of the codepoints, such as the surrogate codepoints (which MUST come in pairs in properly encoded UTF-16), may not b

More ›