Mastodawn

Wccftech | Hardware, Gaming, and Mobile News Jan 5

NVIDIA To Bring Back The GeForce RTX 3060 In Q1 2026 To Tackle Current-Gen GPU & Memory Shortages

https://web.brid.gy/r/https://wccftech.com/nvidia-to-bring-back-geforce-rtx-3060-q1-2026-tackle-memory-shortages/

Kevin Karhan

Dec 9

#IPv6 is a mistake!

Noone needs #128bit address space!
21+ years of protocol existance, yet no mandatory & widespread adoption…
You want to have more than 1 PC per line? We have a solution for it, it's called #NAT!
IPs should not have variable lenghts and hexadecimal digits!!!

#SLAAC? #RouterAdvertisement?? #6rd???

These are real #IPv6only mechanisms deployed in the real world!

"Yes, I'd love to have all my devices loose their #IP assignments everytime my #WAN connection resets/disconnects/…!"

They have played us for absolute fools!

#meme #shitpost #IPv4 #Enshittification

Show thread

Patrick Mevzek Jul 21, 2025

@kkarhan @landley @jschauma @ryanc @0xabad1dea "still, a #64bit #AddresaSpace would've been more than sufficient". Yes, the famous "640KB should be enough for everyone". "A #128bit address space is quite inefficient" Why/where/how inefficient? Do DFZ routers have problems? Is storage SO constrained nowadays that we can't store 128bits values? Or is this again the revenge of "oh my god IPv6 is so difficult, I can't remember all those long addresses like I did in IPv4"?

Show thread

Kevin Karhan

Jul 21, 2025

@pmevzek @landley @jschauma @ryanc @0xabad1dea still, a #64bit #AddressSpace would've been more than sufficient as we can see by the fact that /64 is the default #IPv6 allocation for basically any consumer connection.

A #128bit address space is quite inefficient given we ain't saturating even half of it.

#ZFS does have that problem, abeit #Sun engineers at the time expected #64bit to be as quickly deprecared as #16bin and #32bit.

Show thread

Kevin Karhan

Apr 25, 2025

@landley @jschauma @ryanc @0xabad1dea yeah, the exhaustion problem would've been shoved back with a #64bit or sufficiently delayed by a 40bit number.

Unless we also hate #NAT and expect every device to have a unique static #IP (which is a #privacy nightmare at best that "#PrivacyExtensions" barely fixed.)

I mean they could've also gone the #DECnet approach and use the #EUI48 / #MAC-Address (or #EUI64) as static addressing system, but that would've made #vendors and not #ISPs the powerful forces of allocation. (Similar to how technically the #ICCID dictates #GSM / #4G / #5G access and not the #IMEI unless places like Australia ban imported devices.

I guess using a #128bit address space was inspired by #ZFS doing the same before, as the folks who designed both wanted to design a solution that clearly will outlive them (way harder than COBOL has outlived Grace Hopper)...

Personally I've only had headaches with #IPv6 because not only do I only have #IPv4only #Internet but my #ISP refuses to allocate even a singe /64 to me (but has no problem throwing in a free /29 of #IPv4's in with my contract!)and stuff like #HurricaneElectric / #HEnet's #Tunnelbroker fail face first due to #Geoblocking and the fact that #ASNs get geolocated, not their #PoPs...

If I was @BNetzA I would've mandated #DualStack and banned #CGNAT (or at least the use of CGNAT in #RFC1918 address spaces) as well as #DualStackLite!