I'm fine with 16 but they should have only used the bytes as they were needed, at least for 5 and 6 byte addresses, so those who desire short addresses could buy them.
My vrrp address for my dns server at home is 2001:8b0:abcd::53
It's about as easy to remember as 81.187.123.45//192.168.0.53
Almost all ipv6 addresses I encounter start with 2001, so I just need to remember my home prefix is 8b0:abcd, which is about the same length as my home public IP of 81.187.123.45
::53 means subnet zero host 53, which is easier to remember than which rfc1918 range I used (and basically is the equivalent of remembering the 2001:: prefix)
If I have an internal server I'd have on 192.168.4.12 I could address it with 2001:8b0:abcd:4::12 just as easily, with the "4.12" translating to "4::12", and the "81.187.123.45>192.168.x.y" translating to "2001:8b0:abcd:x::y"
Just because slacc gives you an extra 64 bits of randomness doesn't mean you need to use them.
fe80:: is for link local. You'd want to use something starting fc00:: or fd00::
In your typical home environment, just set your ULA to fd00::12 instead of 192.168.0.12, or fd00:16:34 instead of 192.168.16.34
Yes you'll run into issues if you were to later want to merge your private IPs with someone else, and you should use fd12:3456:7890::12 instead, remembering those extra 10 digits, but its not a problem at home, and no more of a problem with business mergers than ipv4 clashes anyway.
An extremely simple scheme is allowing voters to enter an identifier of their choosing and displaying that with the votes publicly. This is both verifiable and anonymous.
Any issues you can come up with this scheme are also iirc pretty easily solvable.
I use TUIs almost daily on my android phone, either some Linux application in Termux or a DOS application in DOSBox. Both have some extra on screen controls to add special keys, and DOSBox in particular allows adding widgets to control things (including invisible buttons, that are fun to add in some cases over parts of the screen in DOS to give an old game or application touch controls).
If you have a TUI the correct way to support mobile browsers is to 1-shot a React page equivalent. Trying to make the mobile keyboard work for this would be silly.
I used to use XFCE a lot, but since then, even though it sucks in its own ways quite a lot, Gnome defaults to a nicer environment nowadays and doesn't seem so resource intensive anymore.
Yeah the reason Google and OpenAI etc are silent is because their services do the same but they "aren't the bad guys" so if they shut up the crisis will pass.
This of course implies that the crisis itself and persecution of Musk/Grok is politically motivated, or just based on stupidity.
The same capabilities might be present in many available models, but I do think that the public/social aspect in usage is quite different— people can’t come into my Google account and save nudified versions of my family photos directly to my Google drive, but X generated a lot of attention because the users are directly replying or quoting other users and @ing them with the modified photos.
It's beautiful, though, but that's about it.
t. a Finn
reply