#128bit

Wccftech | Hardware, Gaming, and Mobile Newswccftech.com@web.brid.gy
2026-01-05

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

web.brid.gy/r/https://wccftech

<p><a href="https://wccftech.com/nvidia-to-bring-back-geforce-rtx-3060-q1-2026-tackle-memory-shortages/"><img alt="NVIDIA To Discontinue GeForce RTX 3060 GPUs Soon As Production Dries Out, Still The Most Popular GPU On Steam 1" class="attachment-large size-large wp-post-image" height="462" src="https://cdn.wccftech.com/wp-content/uploads/2023/11/NVIDIA-GeForce-RTX-3060-GPU-728x462.png" width="728" /></a></p><p>NVIDIA is reportedly going to recommence production of its GeForce RTX 3060 GPUs owing to DRAM shortages. NVIDIA GeForce RTX 3060 GPUs Might Soon Make A Return On Retail Shelves As DRAM Shortages Hamper Current-Gen Supply NVIDIA started to discontinue its GeForce RTX 3060 GPUs back in 2024. The original lineup, which was introduced back in 2021, is still the most popular gaming graphics card on Steam, and while the 4060 &amp; 5060 are picking up the pace, it looks like NVIDIA might once again open up production lines for this GPU. The new report comes from @hongxing2020, who has [&hellip;]</p><p>Read full article at <a href="https://wccftech.com/nvidia-to-bring-back-geforce-rtx-3060-q1-2026-tackle-memory-shortages/">https://wccftech.com/nvidia-to-bring-back-geforce-rtx-3060-q1-2026-tackle-memory-shortages/</a></p>
Kevin Karhan :verified:kkarhan@infosec.space
2025-12-09

#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

Patrick Mevzekpmevzek@framapiaf.org
2025-07-21

@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"?

Kevin Karhan :verified:kkarhan@infosec.space
2025-07-21

@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.

Kevin Karhan :verified:kkarhan@infosec.space
2025-04-25

@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)...

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!

Kevin Karhan :verified:kkarhan@infosec.space
2024-05-25

@lea we'd still need to decide upon bit width (I'd recommend #128bit to future-proof it!) and have like a #JVM as "#rubtime"-#OS...

Granted, #Sun did that already - sort-of...

On Desktop:
en.wikipedia.org/wiki/Java_Des

And Server:
wetdry.world/@amycatgirl/11249

Kevin Karhan :verified:kkarhan@mstdn.social
2023-09-21

@HopelessDemigod @ncommander

That being said #AIX and the #RS6000 is as far away from a #consumer #PC as #zArchitecture, #DB2 and a lot of other #IBM products...

After all #Services make #Software,
Software makes #Operating Systems,
#OperatingSystems make #Hardware.

Otherwise noone would deal with #AMD64 and everyone would've transitioned to #ARM64 or even #RiscV #128Bit ages ago...
youtube.com/watch?v=XzhCGSE7KK

Kevin Karhan :verified:kkarhan@mstdn.social
2023-07-26

@ariadne I hope #128bit #RISCV will fix that...

Kevin Karhan :verified:kkarhan@mstdn.social
2023-06-05

@b0rk Personally, I want a native #128bit architecture that doesn't do anything but 128bit...

Kevin Karhan :verified:kkarhan@mstdn.social
2023-01-02

@eniko There is no #128bit #ix86 #CPU, it's not even specified.

AFAIK only #RISCV has an #ISA for 128bit and even that is still in #draft and not finalized with 0 #ASIC's produced that implement it.

2017-02-06
Today's #random #hex #128bit sequence. Unlucky for some as they say: 8d856230edf8366c
That said, I think a couple of folks will be quite pleased with that result!

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst