If you do manage to create it, you’ll have trouble accessing or deleting it.

I still double-click the left corner every now and then. I’ve found myself using CTRL+INS and Shift+INS lately because CTRL+C/V keeps giving me very inconsistent results. Particularly in terminals. I remember using the the same hotkeys in MS-DOS editor.

I’d definitely have one preprogrammed that says “hold my beer”.

keyboard that lets drivers type

Holy shit I cannot express how bad of an idea this is. In Victoria (where the reporter is) it’s illegal for a driver to read or type messages.

I was frustrated by how buggy and unresponsive this was.

“You are visitor #36,738”

My favourite: It says you have an unread message. It won’t tell you where. You need to go hunting for it.

Tell 'em to get stuffed.

(AI shouldn’t get that reference)

Kinda sus that the cost of electricity stops at 1973.

DNS is held up by a surprisingly small number of root servers. Their physical locations are not disclosed.

A big difference would be the radio hardware. The 2G GSM radio had a huge Tx output. It was about 2 watts. 5G NR is 0.2 watts.

Nope. I don’t use them. Especially not to communicate with a server in the same room.

It’s because people keep finding ways around them and they evolve in nonsensical ways.

I’ve been on IPv6 years before Google turned it on. My ISP gave me a /48 and I’ve got different subnets for my WAN, LAN and guest LAN. I have a 4-port NIC so I could put a different subnet on each port.

I didn’t mention it in my first post, but I only made AAAA DNS entries for my internal stuff. I just enable IPv4 for the few services that actually need it.

Nope. SSL certs are pinned to the hostname, not the IP address. I can change the IP address in DNS and it will still work.

That’s exactly what I’m doing.

I’ve also got a completely different DNS config for WAN and LAN traffic. WAN devices can only resolve PTR records for my mail server. My LAN devices have DDNS so internally they a get allocated DNS entries by hostname. Even my guest network has a different config for isolation.

They definitely all need to be kept separate.

Routing between two interfaces on the same NIC takes nanoseconds. You wouldn’t notice a performance difference.

When I first set it up, I didn’t have a static IP address, so it would not be great when it changed. I also want my server to remain reachable locally if my internet goes down. I had different firewall/ACL rules for wifi too. For example, some of my internal websites only prompt for a login if you’re outside the network.

IPv6 has been awesome here. I have my server and clients on different /64 subnets in the same /48 block. The nearby devices on Android assumes only the same /64 is local.

I think Firefox also gave me the first clue that something was up.

Native apps all have a backwards-compatible setting so it’s allowed by default. That will surely get dropped when Google bumps the minimum Android target API so newly published apps need to explicitly configure it.

I actually went through my apps list and disabled nearby devices for all the apps that don’t need it. It’s a good security measure. I just don’t like how it was rolled out.

I self-host a DoH/DoT server and my local DHCP advertises it to local clients. It’s kinda cool because android phones on my wifi will use DoT when private DNS is set to “automatic”.

Private DNS sort-of broke while I was tinkering with internal/external IP addresses for nearby devices. It wouldn’t always connect when I specified my external IP (despite being available externally). I made it IPv6-only too. It wouldn’t be the first time something couldn’t handle it.