killbot5000

Tesla-Yutani

This is pure laziness aka “reduced time to market” on the part of Flock.

It takes time and effort to think through proper secure boot architecture and to implement key management in a way that doesn’t kill developer productivity.

Their product managers, though, should have realized that setting these up in unsecured public spaces means that their threat model really does include local physical access to everything.

Using off the shelf hardware and software stacks all but guarantees attackers have tools at their fingertips to exploit said physical access.

Given all the recent exploits hitting the kernel, there’s a good chance that there exists an exploitable over-the-air vulnerability present in their WiFi/bluetooth stack, too.

I keep waiting for the post explaining that this is a joke

I always wonder who the hell is clicking these ads. I skip all you tube ads (thanks Adblock)… I never click banner ads on principle. I assume anything paying for my eyeball time is a scam.

So who is this shit working on? These companies must have detailed profiles on “people who do what we tell them” as a whole class of people. Scary.

Can someone define “improvement” in this context? This concept feels like a buzz word otherwise.

Is this shocking? Grokipedia is an opaque system designed to confirm the opinions of its owner. Why should we expect any kind of coherent transparency?

As long as there’s a trade off between experimentation and performance, software will always be slightly too slow.

Can’t tell if this is sarcastic

Voting with your wallet can work, but consolidation increasingly makes voting with your wallet a double or triple whammy.

1) alternatives may be more expensive by dollars

2) alternatives may be more expensive by time

3) time/money lost to altered consumption has proportional opportunity cost

Market consolidation reduces the cost of using “bad” services and increases the cost of using “good” services over time.

Or a shot in the back.

Not if your spells cast their own spells.

How does he stay awake??

I’ve always suspected the “index funds are the safest investment” system is ripe for exploitation.

I love go, but I find it did little to make concurrency management easier to reason about. Race conditions are easy to write. Go routines have all the same concurrency problems of threads.

In the parallel HTTP fetcher, the error is discarded. This will likely result in a panic when the response is nil. Also, what if it a server locks up? Or the underlying socket never connects and never times out?

I know it’s a toy example, but one must consider all these things in a real system. Go does have good pathways for these concerns, but it’s also easy to do it wrong. I still have to manually reason about access to variables/struct fields from multiple go routines.

No. Why is this a question?