|
|
Subscribe / Log in / New account

Security quotes of the week

The Cellmate chastity lock works by allowing a trusted partner to remotely lock and unlock the chamber over Bluetooth using a mobile app. That app communicates with the lock using an API. But that API was left open and without a password [...] it may require the intervention of a heavy-duty bolt cutter or an angle grinder to free the user.
Zack Whittaker at TechCrunch

We have knowingly and willingly built the architecture of a police state, just so companies can show us ads.
Bruce Schneier

to post comments

Security quotes of the week

Posted Oct 15, 2020 5:30 UTC (Thu) by NYKevin (subscriber, #129325) [Link] (8 responses)

I never cease to be amazed by the increasingly ridiculous set of things that now have microprocessors or microcontrollers inside of them. Seriously, given all the other hilariously insecure IoT devices, how could anyone possibly think that this was a Good Idea? It's almost as ridiculous as that time they tried to sell a $400 device that did nothing more than squeezing a bag of juice into a cup.

Security quotes of the week

Posted Oct 15, 2020 15:08 UTC (Thu) by mathstuf (subscriber, #69389) [Link]

> a $400 device that did nothing more than squeezing a bag of juice into a cup.

But it was *verified* pulp that was used. You wouldn't want to use dirty off-brand pulp would you? And based on AvE's teardown, they were *losing* money at that price point based on the components they put in that thing (it was all in the subscriptions).

Security quotes of the week

Posted Oct 15, 2020 16:55 UTC (Thu) by rgmoore (✭ supporter ✭, #75) [Link] (6 responses)

Juicero was an interesting idea that failed, but the failure had nothing to do with whether it had an onboard microprocessor. The device was intended as a loss leader, with the real money coming from selling subscriptions to the juice packets. It was intended to be the juicing equivalent of the K-cup coffee makers back when the K-cup was still under patent so they could get away with overcharging for the cups. It failed for the same reasons that many startup companies fail, basically boiling down to really bad management, but the underlying concept wasn't inherently ridiculous.

Full disclosure: I am a minor investor in a different juicer company, so I know at least a little bit about the industry. There is a market out there for expensive juicers that produce premium juice. I think Juicero's biggest mistakes were A) trying to make a big splash instead of trying to establish a small but profitable business and B) not knowing the market well enough.

Security quotes of the week

Posted Oct 18, 2020 0:23 UTC (Sun) by anselm (subscriber, #2796) [Link] (4 responses)

There is a market out there for expensive juicers that produce premium juice.

My local supermarket carries packets of premium juice at twice the price (or more) of the el-cheapo packets of standard juice. The premium juice from the supermarket is very nice indeed. Now even with the surcharge for premium juice, the equivalent of $400 will buy a whole lot of premium-juice packets in the supermarket. Furthermore, the premium juice packets for the juicer will probably not be significantly cheaper or nicer than the premium juice packets from the supermarket, either, plus I'd be locked in to whatever the juicer company will deign to offer me. It sounds like a bad idea whichever way you cut it.

Security quotes of the week

Posted Oct 18, 2020 2:54 UTC (Sun) by pabs (subscriber, #43278) [Link] (3 responses)

What are juice packets?

Juice packs

Posted Oct 19, 2020 19:03 UTC (Mon) by pr1268 (guest, #24648) [Link] (1 responses)

Ars Technica article about Juicero from April 2017 (with images). The company folded about five months later.

Juice packs

Posted Oct 19, 2020 23:37 UTC (Mon) by pabs (subscriber, #43278) [Link]

So the "Juice packs" are bags of pre-cut fruit. Hmm.

Juice packets are *not* network-related

Posted Oct 19, 2020 19:33 UTC (Mon) by pr1268 (guest, #24648) [Link]

P.S. "Juice packets" are not related to network packets! 😃

Security quotes of the week

Posted Nov 2, 2020 17:06 UTC (Mon) by immibis (subscriber, #105511) [Link]

> the failure had nothing to do with whether it had an onboard microprocessor.

Do you think it may have had something to do with how much that microprocessor did? It would refuse to run if it couldn't read a QR code and send it over Wi-Fi.


Copyright © 2020, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds