Stuur de apparatuur in een stevige doos naar ons terug. Gebruik de doos die je van ons ontvangt of de originele doos. Als je die niet (meer) hebt, kun je ook een andere passende doos gebruiken.
It mentions DuPont wire connectors which is colloquial for a common form of jump wires: the ones that can connect to breadboards, or male or female pin headers. Basically a so called “DuPont wire” is an electric wire with a pin header (either male or female) on each end leading to 3 kinds (not counting ones having multiple connectors on each wire) as male – female is the same as male – female:
female – female
female – male
male – male
Being able to group the connector end of multiple jump wires in one enclosing connector for quick opening and closing is a great idea.
Hopefully the 3D printing files will be released somewhere.
One of the comments is also inspiration for a future 3D printing project:
On OpenWRT GL.iNET based devices, the WireGuard client does not restart upon reboot, even if it was started before rebooting.
Hopefully the /usr/bin/wireguard_watchdog script will help with this as others indicates it should.
My first try was no succes, but since it is supposed to run from cron it does no output. The script on GL-SFT1200 firmware version 3.215, script /usr/bin/wireguard_watchdog is different from the one in the OpenWRT repository, so it needs some investigation.
This resulted in the WireGuard client connection indicator on the GL.iNET to turn yellow instead of green. This means that the handshake is only partially completed (there is a WireGuard connection but there is no returning traffic on it).
Other typed languages and tool sets like C# and Delphi come to mind here as well though you need libraries with 1-based data structures to solve the first point.
I am writing this early 2025, shortly after Odido introduced “Klik & Klaar” for EUR 25/month: yet another of their internet products, this time over 5G, and yet again: no IPv6 support, just like their DSL and fiber products.
This post is a reminder to check if by now Odido has started supporting IPv6.
I know that at the time of writing, of the large Dutch mobile providers, only KPN supported IPv6, but both Vodafone and Odido didn’t. However, for Vodafone it is not a technical limitation: their bean counters need an upgrade to their billing system. The Odido back-haul technically isn’t ready for IPv6 at all.
Regrettably, The Netherlands has been behind on IPv6 adoption, which is a shame for a knowledge worker country. UK, Belgium, Germany, France, Greece, Hungary and even Russia are doing far better on IPv6 adoption:
The reason why RAM has become four times more expensive is that a huge amount of RAM that has not yet been produced was purchased with non-existent money to be installed in GPUs that also have not yet been produced, in order to place them in data centers that have not yet been built, powered by infrastructure that may never appear, to satisfy demand that does not actually exist and to obtain profit that is mathematically impossible.
The reason why RAM has become four times more expensive is that a huge amount of RAM that has not yet been produced was purchased with non-existent money to be installed in GPUs that also have not yet been produced, in order to place them in data centers that have not yet been…
This is the cleanest summary of the AI hardware bubble. We’re pre-paying for a future supply chain, future workloads, and future profits that may never converge. It’s not RAM scarcity it’s speculative coordination failure at industrial scale.
Speculation is fine until the entire supply chain starts optimizing for a world that only exists on pitch decks. At some point, physics, cash flow, and grid capacity pull everything back to reality.
The Wiert Corner - irregular stream of stuff 