Comments URL: https://news.ycombinator.com/item?id=48140071

Points: 9

# Comments: 2

Let's not use this cope to mislead anyone into thinking this is a unique Mac innovation (it isn't) that trumps this abomination of human factors (it doesn't).

The "SS" and blue connector inserts are recommended in the spec to denote 3.0-capable ports.

Apple never followed the spec recommendation because colors and labeling are ugly and for dumb PC users.

Maybe you should reassess your confidence.

That's where you're wrong. They're not one and the same.

Debian stable often defers non-security bug fixes for up to two years by playing this game.

I'm not interested in new features unless they make things actually work.

Debian stable time and again favors broken over new. Broken kernels, broken packages. At least they're stable in their brokenness.

Hence my complaint.

Debian patches defaults in OpenSSH code so it behaves differently than upstream.

They shouldn't legally be allowed to call it OpenSSH, let alone lecture people about it.

Let them call their fork DebSSH, like they have to do with "IceWeasel" and all the other nonsense they mire themselves into.

When you break software to the point you change how it behaves you shouldn't be allowed to use the same name.

But I doubt it, they will lazily backport these patches to create some frankenstein one-off version and be done with it.

Before anyone says "tHaT's wHaT sTaBlE iS fOr": they have literally shipped straight-up broken packages before, because fixing it would somehow make it not "stable". They would rather ship useless, broken code than something too new. It's crazy.

https://www.youtube.com/watch?v=fW4Q7NNSBME

Comments URL: https://news.ycombinator.com/item?id=48110771

Points: 14

# Comments: 5

Steve indirectly had a hand in this, by emphasizing the humanities. That, unfortunately, backfired as a sort of positive feedback loop.

Someone hired a few underemployed artists onto the team, and the artists invited all their friends and soon took over the department.

People that in an alternate timeline would be smoking weed whilst sculpting wood in a derelict loft somewhere are now the lead designers, using our software as the canvas of a perpetual avant-garde art piece.

They also need to look productive to justify their jobs, so the need to change things is constant.

That's why in 2026 you could have a PhD in CS and still need to watch a YouTube video to learn how to change the volume.

Can anyone name a single substantive UI improvement in the last 20 years? They're simply hiding or moving stuff around at this point while no one has even touched accessibility.

Guess they've never been on the phone with an elderly relative in tears because she can't figure out basic tasks on an iPad anymore after years of learning how.

That's when you realize you, as a highly-skilled technical person, can't either, because they've moved, hidden, or otherwise obfuscated them.

Yesterday I learned there are two icons in the Files app called "..."

Yes, two.

Incidentally I was looking for how to delete a file, which is now deliberately missing from the object's context menu, and intentionally hidden under one of these.

Comments URL: https://news.ycombinator.com/item?id=48109549

Points: 3

# Comments: 0

So you login the first time and they either match, or they don't. If they don't you start over. The end.

Ignore the fact that most people will probably use the box to host a poorly coded vulnerable service anyway.

I'm not confident you understand how crypto works.

You do realize the entire threat model here is a house of cards perched atop someone else's software hosted on someone else's hardware all of which you implicitly trust and discard in favor of some unlikely cloak and dagger interception scheme.

Yes you implicitly trust the public key on first login.... then just... immediately compare it with what's on your box?

Might as well seal your doors with duct tape to prevent ghosts from entering your home because this is equally effective.