The phrasing and pacing sound repeatedly “but wait there’s more” style that AI seems to favor. Always trying to re-emphasize a point already made to make the reader interpret it a specific way.
Not to mention the em-dashes.
Sometimes good writing sounds like that too, but good writers also know to not use and repeat that same style over every paragraph.
Fascinating data presented in a clearly AI written or at least heavily edited format that makes it really hard to read without massive skepticism.
Depends on what threat you’re protecting against IMHO.
If you’re trying to be anonymous, connecting to your home IP first is a dead giveaway to who you are. Both your home ISP and whichever ISP you’re connnected to will know.
Only easy way to maintain some anonymity right now would be to use Tailscale’s Mullvad integration……Tailscale to connect your servers, Mullvad for anonymize/country changing.
Other way might be to ONLY use Tailscale/Mullvad, and set up an alternative auth front door to your own network. Complicated and doesn’t work as nicely tho.
Director of acting intelligent
Heh true enough. And you can run into issues with package updates breaking something. But hopefully that breaks things for others too so there’s some shared misery there rather than just having to curse your past self for decisions you no longer remember? 🤣
DHCP can be set to specifically assign the same IP to specific devices, reserving them and ensuring that no other systems will use the same IP accidentally. So your servers will consistently get that same IP address assigned to them every time, no worry about the ip address changing unexpectedly.
Very old school; yes you can certainly do all of that and track all of that yourself. We all used to do it that way……But it’s 2026….just as you’d use a real editor rather than edlin, or password managers rather than text files, the new ways ARE better, easier and more consistent. Making sure dhcp works is one of the modern (honestly not that modern) basics that make sure your network is set up properly and isn’t hiding some misconfiguration gremlins that only work because of some static ip and route workaround you implemented years ago and worked “until now”.
Wrong. It’s 2026. You should be setting static dhcp entries and using dhcp to ensure static IPs, not avoiding dhcp. Using manually assigned static IPs just means you’ve built a fragile unique snowflake.
Code sloppering
3 words: Gravis PC Gamepad