Facial recognition is becoming common enough that it’s no longer very surprising if you’re in a crowded public space. Malls argue they need it to catch thieves, airports argue they need it to catch terrorists, and so on and so forth.

Privacy is like Humpty Dumpty, except he’s being poked to death.

https://github.com/avajs/ava

There are still lots of good reasons to shop local, but I’m not sure speed is the best reason.

The most common issue for me is what happened when I bought a custom dog bowl, thinking the ceramic was made by the seller. Later stumbled upon something similar and realized it was just an off the shelf bowl and the dog’s name had been painted on. That not worth nothing, and it was still probably nicer than what I could’ve gotten on Amazon, and maybe I should’ve asked before buying. But there’s just a lot of that, “make a quick buck” type of stuff and it’s not always obvious.

With the latter type, there’s still almost always a line of communication to corporate. And the support staff still try to help. They are decent human beings, even if the end result kind of sucks.

Not really. At minimum, a half-way decent support person would ask a few people internally or search Slack before answering.

In fact, they would have likely already heard about the new product at lunch or something.

Also, here in the U.S., we’ve managed to screw up so badly on data privacy and basic rights that the EU has been systematically replacing their entire tech stack with sovereign components.

However, the article claims that the final distribution doesn’t need to have a bit depth of more than 16. That does not match my experience. I can tell the difference between my renders that are 16 bit vs 24 bit. I cannot tell the difference between 44.1 kHz and higher sample rates, and that’s consistent with the math (Nyquist-Shannon), but bit depth is a different matter. Would be fun to participate in a double-blind test that includes my own tracks and others.

A workaround is to use the Notes app and use the return key to make a new line after each try, rather than deleting. That should give you more consistent results.

You mean like the two E’s in “feel” or the two L’s in “fell”? I just tried and it handles them well. Are you aware of the circling technique? When you want to double up on a letter, you briefly circle it slightly. I believe some keyboards let you hover momentarily without circling.

Try it, swipe F-E-L, it should complete to “fell”, then do the same thing again but form a small, tight circle over the E, it should then complete to “feel”. Works for me every time.

My only advice is to start by approaching the problem. “Hey, do your shoelaces come untied often?”

I once got detention for getting punched in the arm. I was much taller than any of the school bullies, so they mostly didn't start anything with me. But every now and then, they would try. The punch barely hurt and I didn't really care, but another student saw it and reported it. The staff knew what happened, understood that I was the only one that got hit, and then gave us both detention. I couldn't believe it. That angered me 100x more than the bully. Looking back, I assume this policy was intended to deal with cases where it's unclear who hit who or who started it. But I became fixated on how unfair it was. If they wanted to create another troublemaker, they almost succeeded.