So, respectfully, you shouldn't dismiss grandparent with "This isn't really true".

I tried to lipread the Inauguration, and where it was successful I did read the same nonsense, but often it wasn't possible because they weren't looking at the camera or the microphone was in the way.

The Seagulls, however, the only thing I could read was amm-amm-ammmmm-am-am-aaaammm. Nothing else. Of course, the doll has very simple mouth mechanics.

What this article is missing, I think, is that lipreading is not replacing auditory input with visual input because there are too many, let's just call them homophones. I find the word "visemes" a bit too cute. You need a lot of context. So I always struggle if someone asks me a very short question, because I don't know what it's about. Someone comes to me, says hello, and asks the question, and I don't have an idea what they want to know.

Re gameplays, the context is special, because you can assume that the football coach is not shouting "HAKUNA MATATA" over the field. This simplifies lipreading during gameplays. Essentially it devolves into something like a set of radio buttons.

I thought up to 3x a week and never consecutive days is the maximum.

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

Points: 1

# Comments: 0

Maybe. Bugs that come from spooky behavior at a distance are notoriously hard to debug, especially in production, and it's worthwile to pay for it to avoid that.

[1]: http://catb.org/jargon/html/N/nasal-demons.html

I don't understand all consequences yet, except one, that the wealthy and powerful object to it because it hurts them and so the Land Value Tax is rarely introduced. Even if it gets introduced, it will abolished soon thereafter.

In other words, I don't think that AI is killing the web.

It's being profit-oriented and running amok in an unleashed way. It's prisoner's dilemma. You know, if you don't do it then someone else will do it and you lose. Enshittification is one consequence. The internet experienced it from the beginning. But only about fifteen years ago companies learnt how to squeeze the last drop out and, like in the tragedy of the commons, everybody is worse off.

And what's the most catastrophic? People are confused. They look at the tools but not at some famous people behind these rampages. Of course as leaders they just optimize the hell out of the internet with the target that their companies thrive. But in doing so they cause heavy damage.

Another way: Let ferment it to the max. If fermentation doesn't consume all the sugar, then it's somewhat stable.

Ancient wines also had resins added. Today these would probably have tasted almost medicinal, but often they are diluted before serving. Wine dilution is still a custom in some parts of Italy. I was invited to a party in Tuscany and they served a lot of Lambrusco amabile and for the children they diluted it and because Lambrusco amabile is rather sweet it was a little bit an oldfashioned soft drink. I tried it, too, and it's refreshing. I don't know whether it's sacrilegous but as one says, in Rome do as Romans do.

https://chriscoyier.net/2025/05/10/the-am-dash/

But that won't help for long. If the Amdash becomes popular, then AI will pick it up, because "am-" is just a text fragment and AI can learn to produce it.

Even worse if a future version of Unicode adopts the Amdash, then nothing will stop AI.

Or the opposite happens as one already said here: Nobody will use the Amdash.

Source: I am the parent of a child with autism.

unsigned means, don't use of an integer MSB as sign bit. __nonstring means, the byte array might not be terminated with a NUL byte.

So what happens if you use integers instead of byte arrays? I mean cast away unsigned or add unsigned. Of course these two areas are different, but one could try to design such features that they behave in similar ways where it makes sense.

I am unsure but it seems, if you cast to a different type you lose the conditions of the previous type. And "should this be legal", you can cast away a lot of things and it's legal. That's C.

But whatever because it's not implemented. This all is hypothetical. I understand GCC that they took the easier way. Type strictness is not C's forte.

This would be only useful in typedefs. An API could declare some byte arrays not strings. But again, whatever.

I imagine that it could work a little bit like unsigned: a modifier to integer types that tells that an integer's MSB is not to be used as a sign bit.

__nonstring__ tells that the last byte of a byte sequence doesn't need to be NUL.

I would find it sensible allowing putting the attribute to a type, but whatever.