Microslop at its best.

When people are managing 20 devices on a network, they access everything by IP address directly and struggle with constant DNS issues.

Introducing a more complex system without easing any of the cognitive load and making fun of it is just cruel at this moment.

Users need a simpler way to connect to their devices, and what tailscale did with magic dns shows that users don’t even care about IPv4 they just want to connect to their devices with something simple they can remember.

I have 68 devices on the line at this moment. I just checked. I remember exactly one of their IPs and that’s just one that stuck in my head. I never connect to it by address.

I agree with the sibling comment: crummy CPE is crummy CPE. This is a solvable problem, but people end up with junky routers and it causes them anguish.

Weirdly this might be a CPE problem, e.g. crappy ISP routers.

Put in something more interesting, e.g. OpenWRT, or there are proprietary options too, that provides simple & reliable local LAN DNS, then the problem just goes away.

It’s mind blowing when you check the generated code, because it goes over 50 elements deep for a simple looking website.

Makes me think that there’s no way this is computationally efficient either.

That particular issue is nothing to do with Next or React and everything to do with how HTML/CSS is a really shitty layout engine.

Hard disagree. This is JavaScript frameworks building a hierarchy for themselves and ignoring any sort of complexity on the generated DOM. There’s 0 reason for these 8-10 nested divs other than that’s what the framework spits out.

/compact also takes an optional instruction parameter, e.g. exclude the data format discussion.

Bill Gates: “640K ought to be enough for anybody.”

Might be good for early detection, but unfortunately doesn't provide any defense on its own.

Early detection lets you prepare the defenses.

Like getting some MANPADS teams in the route of an oncoming helicopter assault.

Keep in mind though you may need to deal with encoding, chunking, and other low level issues.

Not hard. I have such a thing as just a few lines of quickly put together python code, using pyserial, dockerized. Has run for an entire year w/o issue. ASCII and Unicode.

It replaced a very unreliable, problematic setup somebody else had set up in the past, which was based on an android phone.

Once I got the sim900-derived device from aliexpress, I moved the sim over and had it working in less than an hour. Polished the code and its setup during the first few days of use, and hadn't had to touch it since.

Thank you Apple for leaving all the iOS 26 capable device insecure, because they didn't want to upgrade the half-assed iOS 26.

> It is highly unusual for Apple to provide a security update to iOS 18 users who simply don't want to upgrade to iOS 26

Duh. I wish Apple also stopped harassing us to update to iOS 26. It simply sucks, maybe iOS 27 would be better, hopefully.

You can switch to the iOS 18 public beta channel to stop the notifications.

> adults who haven't confirmed their age.

I beg to differ, clearly you have to identify yourself before you can use those services and they likely will require verification every time.

Soon you have a continuous face scan to “verify” age during use, and that quickly becomes tracking even your emotional state.