Part of the problem with current data centers is the density. To make the economics work, you need excessive density, which comes with power, noise, and water requirements.
Smaller servers distributed more widely don’t come with the same requirements. They can’t handle all use cases, but something like a Tinybox can run consumer LLM tasks just fine, a SAN with a small server can provide backup storage or storage for CDNs, etc. No need to turn the house into a full data center.
The key would be to build highly efficient small servers that can work as an appliance. It would need to be very easy to swap them out when one fails.
Again, I’m not sure this has much of a benefit except for providing geographical dispersion. Data centers would still be more cost effective. Maybe it would be helpful for providing local services in small remote areas like islands.
A Bitcoin mining node is the simplest possible way to turn compute into money. Very minimal storage and bandwidth requirements. And yet we still do not see those in houses.
Everything about doing productive computing tasks in houses is more complicated than that! At least it is more profitable, I think?
(I wonder what a rough profit per watt figure is for a datacenter. Very much "it depends" I'm sure.)
The density of data centers provides efficiency gains -- if you take the same workload from a high density nvidia DGX setup in a data center and instead distribute it to Tinyboxes running residentially, you'd have an overall net gain in energy use.
Yes, along with additional costs for managing and servicing a distributed set of devices and extra redundancy needed for higher expected downtime. But maybe the cost is worth it for some application.
(Have 3yo and 1yo, another one the way, goal is 4)
I have often thought that car seats are one of the major drags of modern parenting. This study apparently (I don't have time to read it, too busy with kids lmao!) confirms my suspicions.
It is unfortunate that every policy change around them is trading some amount of convenience for every smaller risk eliminations. It is essentially impossible to say perfectly rational things like "I think children should be put in this slightly riskier type of car seat for convenience reasons."
Even if laws are relaxed, there is the peer/manufacturer pressure. As a real example, I think it is pretty annoying to have my three year old facing backwards. It would be somewhat more dangerous to have them facing forwards, but a substantial improvement in quality of life for me and for the child. The manufacturers compete based on max weight that they support/allow/claim for rear facing, something like 45 pounds. So a family member such as a spouse allegedly has decided that the child ABSOLUTELY needs to be rear facing until they reach that weight. That may not happen until age five! By this time there may be manufacturers inching up to 60 pounds rear facing.
The only possible relief I can envision is that computers become so proficient at driving our cars that there are essentially no accidents. Then we may be allowed to sit unbuckled holding our children!
My child moved to front facing at around 2 or maybe 2.5 at the oldest (had to go back and lock at old pictures to confirm, she’s 12 now). Parents who obsess over things like keeping their kid rear facing until 5 or in a booster seat until 12 are just neurotic, IMHO. They’re probably the same ones who won’t let them ride their bikes around the neighborhood unsupervised or walk/ride the bus to or from school.
I had a vehicle with no back seats when my child was in a car seat. It was great because I could attend to them while driving. Since there were no back seats they could not cite me as it was an exception to the law.
I'm not convinced it's actually safer to have kids in the back. Sure they're safer in an accident, but when I drove another car with rear seats I found myself constantly looking back to deal with the child thus more likely to cause an accident. Yes maybe you should just neglect your child while driving, but they will exact penance if you do so, by non-stop screaming so loud you can't hear emergency vehicles or other possible road hazards.
This common sense mindset would invalidate so many 'safety' laws and I'm all for it.
Studies make so many invalid assumptions (and usually don't even state them) to force the data / statistics to fit clean a/b or null testing.
But to put a dent in the status quo, we really need a greenlight to just dump however many kids in the back again, no matter the number of kids or seatbelts.
And before anyone gut reacts to this- ask yourself why doing that with schoolbuses still isn't a problem?
Probably for the same reason government trucks aren't required to have emissions controls on them, at the end of the day the King will do whatever they like and reason backwards why it applies to the subjects but not the crown.
> I'm not convinced it's actually safer to have kids in the back.
I thought that a major reason for placing children in back seat was because of the air bags in the front seat representing a danger to them when they deploy.
(But maybe kids don't trigger the weight needed to activate the passenger side air bag anymore?)
You can also usually just turn off the passenger-side airbag. I know there's been a button on every car I've owned to do so, for when you've got something heavy in the front seat that isn't a passenger.
I've never had a car where you could disable the passenger-side airbag. We did have a car like that in the 90s, but it didn't come that way from the factory: my mother had a mostly-irrational fear of them (she was on the shorter side, but not so short that it could actually be a danger for her if it deployed), so we somehow got an aftermarket mod that let her disable it when she was riding in that seat.
Of course, she drove that car often enough too; not sure why she felt having the driver-side airbag enabled all the time was safe, but not the passenger-side airbag. (Mom was... often inconsistent with how she reacted to her fears.)
Check the area near the hinge on the front passanger-side door, there should be a labelled thing you can turn to disable it. (using a key or screwdriver, similar to the rear childlocks)
It might be due to me being in Europe, but every car I've ever seen with an airbag for that seat has had it along with a sticker warning about it in the sunvisor area.
Some newer vehicles will automatically disable the front passenger airbag if there is nothing in the seat or if there is weight in the seat but less weight than a typical adult.
Pickup trucks without a backseat have long had the ability to manually disable the passenger airbag.
>
The only possible relief I can envision is that computers become so proficient at driving our cars that there are essentially no accidents. Then we may be allowed to sit unbuckled holding our children!
Laws are about control[ling citizens]. Politicians are not willing to give up control.
This is so bad that it must be intentional, right? Even though these are dirt cheap, they couldn't come up with $100,000 to check for run-of-the-mill vulnerabilities? There must be many millions sold. Quite handy for some intel agencies.
I assume any Wi-Fi camera under $150 has basically the same problems. I guess the only way to run a security camera where you don't have Ethernet is to use a non-proprietary Wi-Fi <-> 1000BASE-T adapter. Probably only something homebuilt based on a single board computer and running basically stock Linux/BSD meets that requirement.
> This is so bad that it must be intentional, right? Even though these are dirt cheap, they couldn't come up with $100,000 to check for run-of-the-mill vulnerabilities?
The camera sells for $17.99 on their website right now.
Subtract out the cost of the hardware, the box, warehousing, transit to the warehouse, assembly, testing, returns, lost shipments, warranty replacements, support staff, and everything else, then imagine how much is left over for profit. Let's be very optimistic and say $5 per unit.
That $5 per unit profit would mean an additional $100,000 invested in software development would be like taking 20,000 units of this camera and lighting them on fire. Or they could not do that and improve their bottom line numbers by $100,000.
TP-Link has a huge lineup of products and is constantly introducing new things. Multiply that $100,000 across the probably 100+ products on their websites and it becomes tens of millions of dollars per year.
The only way these ultra-cheap products are getting shipped at these prices is by doing the absolute bare minimum of software development. They take a reference design from the chip vendor, have 1 or 2 low wage engineers change things in the reference codebase until it appears to work, then they ship it.
Both the parent and you can be right in this case.
The parent rightly suggested that there is the obvious intention to exploit these devices:
> This is so bad that it must be intentional, right? Even though these are dirt cheap, they couldn't come up with $100,000 to check for run-of-the-mill vulnerabilities?
You explained that there could be an economic reason for the appalling absence of security:
> The only way these ultra-cheap products are getting shipped at these prices is by doing the absolute bare minimum of software development.
But the parent's point is more convincing, based on the observable evidence and the very clear patterns of state-sponsored exploitation.
The vendors could set default passwords to be robust. The vendors could configure defaults to block upstream access. But maybe the vendors in this particular supply chain are more like the purveyors of shovels in a Gold Rush.
A less-charitable metaphor is possible where state-sponsored motives are unambiguously known.
Is there a table of supported hardware, that contains info about the USB-connection (or ethernet) on these devices. Like, which have data-lines connected, can the device electrically do host and device mode? Can I use a POE2USBC adapter, that presents itself as a USB-network device to the camera?
Ability to filter on those columns would be great.
Is thingino using the Ingenic linux kernel 3.ancient SDK version, or do they have/use something newer?
It's been long known many older TP-Link IoT devices doesn't require any authentication to connect, as my Kasa HS300 strips. Later models requires the account credential [1], but I'm not surprised that they still left something wide open (e.g., WiFi config endpoint for provisioning). I tend to believe this is just poor software engineering (Hanlon's razor).
My initial read of proximity being sufficient to exploit 3 is incorrect, so yeah as long as you control the Wi-Fi network sufficiently then things should be fine.
reply