abcd_f

You are over-exaggerating.

As much of a snob that Jobs was it's nonsensical to say that he would've knowingly insisted on changes that locked users out from their devices. That's just nonsense. At the very least there would've been a prompt to change the password phrase or some such in upgrade. And if it did happen as an oversight, it would've been patched on the first report and some heads would've rolled.

He would've not let the abysmal slop like iOS 26 UI to ship ever.

Some things he didn't appear to care much about, the polished UX was his schtick.

It should be then a switch in the settings.

It's more or less commonly accepted that its creator got jailed for being an arms dealer.

https://en.wikipedia.org/wiki/Paul_Le_Roux

This is more of urban legend that may somewhat hold true in tourist-heavy areas.

The good news is that's edible and apparently tastes good.

Just like it was with that amateur sub that imploded. It later surfaced the Navy heard the implosion and knew what it was.

And who didn't do that! :)

You could also 4x the resolution by using half- and quarter-block characters from the top half of the ASCII table (or it'd be the PETSCII one i C64 case).

> It’s the same assumption is required for any hole punching handshake (including STUN).

This is incorrect.

Hole punching requires being able to predict external port. That's it. If the port remains the same, it certainly simplifies things, but ports going up (or down) by 1 (or 2, or 5) with each new mapping is quite common, trivial to detect and to punch through.

Claimed elegance is based on a very bold assumption that the NAT device preserves the source port of outbound connection.

Hardly the case in even half of typical deployment cases.

Also makes it easier to identify your alt accounts ;)

> can't impact your driving privilege

Unlike improper parking, running red lights should impact said privilege as potential consequences are way more serious.

But they didn't say anything about refunding them and you can bet Trump will oppose that and ask the SCOTUS to decide on it. They of course have an option to take their time to render the decision and then just dismiss the case without a comment.

That's what the GP likely meant.

The circus must go on.

What local options are on par with ChatGPT?

TC still exists, huh?

My wife just said she wasn't getting any chills, but definitely some yawns :)

> when you were somewhere between nine and eleven years old.

As endearing as it sounds, that's pure selection bias on Walter's end rather than something even remotely common.

Clearly there are cases of this sort, like arts and other creative tangents, but on average it's a result of a discovery process much later in life.

It's a tough problem.

Once some users have extra power to push content to the front-page, it will be abused. There will be attempts to gain that privilege in order to monetize, profit from or abuse it in some other way.

The only option along this path would probably be to keep the list of such users very tightly controlled and each vouched for individually.

  ---

Another approach might be to ask random users (above certain karma threshold) rank new submissions. Once in a while stick a showhn post into their front page with up and down arrows, and mark it as a community service. Given HN volume it should be easy to get an average opinion in a matter of minutes.

The solution to this is to allow aliases ... or account groups if you will and then allow/disallow things based on combined karma.

This very post is probably his too, under an alt :)

I read through the RFC and I think it's fair it was rejected, because this was ultimately a half-measure, with severe usability restrictions.

Fat pointers are clearly a way to deal with arrays (and also get "slices" and non-zero terminated strings for free!), but it's just not possible to retrofit them into the language without breaking existing code.

Arrays decaying to pointers is probably the biggest non-platform specific design oversight.

As you said, it's easy to see where it came from, but it should've been fixed long ago.

> the PNW winter

It rains only once ... but for six months :)

Yeah, to intimidate kids when they don't deliver academically :)

> US incompetency

US corruption.

Incompetence would've been a good news here.

Port knocking should open up the port for the IP that sent the knock. Not for everyone.

You can conceal that open port with some form of port knocking. Though this does reinforce your "easy" point.

Also, if it's an UDP port, then using a protocol that expects first client packet to be pre-authenticated and not emitting any response otherwise gets you pretty damn close to having this port closed.

I witnessed something recently that points unambiguously at Whatsapp chats being not private.

Not two months ago I sent a single photo to a friend of some random MacGyver kitchen contraption I made. Never described it, just a photo with the lol. He replied lol. He never reshared nor discussed it with anyone else. We never spoke about this before or after. Two days later he starts seeing ads on Facebook for a proper version of the same. There's virtually no other explanation except for Meta vacuuming and analyzing the photo. None.

... or two separate taps even. Though it's quite a bit more exotic and ancient.

https://ichef.bbci.co.uk/news/1536/cpsprodpb/AF32/production...

Daaamn... Olivetti.

  ,d88b.d88b,
  88888888888
  `Y8888888Y'
    `Y888Y'   
      `Y'

An Olivetti PC was an ultimate dream to have in the late 80s and the early 90s for me, in impressionable age of adolescence, prone to the call of tinkering, hacking and programming. They were the brand, at least in Europe.

Such a nice memory :)