Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×

Comment Re:Can it be used locally? (Score 1) 64

I have been able to "smarten" dumb appliances by plugging them into smart power switches. For less than $8 each I bought a couple boxes of smart switches from Amazon, then reflashed them with Tasmota -- no more cloud! -- and joined them to Home Assistant. Now any device I want to be smart, I plug it into a smart switch and monitor the power.

One of my scripts monitors the power draw on my dryer, and when it goes above 100W for a minute then drops below 10W for 15 seconds, it knows the cycle is done and alerts us to go down to the basement and take out the clothes before they wrinkle. A similar script monitors the washer.

The refrigerator's plug has a script alert me when the average daily power draw is higher than normal. I added that after my son called me from his most recent vacation and said "my refrigerator is using more power than it should, can you go check it?" Sure enough, their freezer door had been left open by their toddler. Of course the food was already thawing, but we cleaned it out a week before they would have come home to a house full of rotted food stench. And before you ask, yes, when I installed Tasmota I configured the switch to be "always on", so that even if Home Assistant thinks it would be a good idea to shut off the refrigerator's power, it can't.

I also have a small water pump on a smart switch. Normally the pump draws 36W, but when it runs dry it draws 30W. Now if the power consumption drops below 33W and stays there for a few minutes, it shuts off the pump and alerts me that the water is low.

So I get what I need -- timely information about the equipment in my home, automated reactions when things go bad that might keep things from getting worse, and no cloud involvement from any sleazy appliance manufacturers. And an $8 plug is a lot cheaper than paying a $400 premium for a "smart washer".

Comment Re:what about needs to work with local server off (Score 1) 64

Tuya's become a nightmare to deal with. They've decided they fear local integrations because they're losing ad revenue when people don't use the Tuya app. They have been going to progressively greater lengths to prevent device buyers from bypassing the Tuya servers and running their stuff locally.

My understanding is you can no longer register for a free Tuya developer account that lets you set it up with the "Local Tuya" integration for HomeAssistant -- you have to have a paid developer account, if it works at all. And their libraries used to flash right onto an ESP32, but now they're encouraging developers to more secure chips, in an attempt to prevent end users from reflashing their own devices with firmware (like Tasmota) that no longer communicates via Tuya services.

I wouldn't buy anything Tuya with the hopes that it will someday integrate with anything else. If you buy them, expect them only to work with the official apps.

Comment Re:more data (Score 1) 64

PKIs were designed for offline use. There are a couple hundred trusted Certificate Authorities that each issue a "root" certificate. These root certificates are distributed worldwide, in browsers, operating system distros, phones, etc. When you encounter a certificate in the wild, you have to verify the certificate before accepting it, which is done by checking what you can locally: is it expired? Does its DNS name resolve to the name on the cert? Does it have a valid signature? This means checking to see if it was signed by a CA certificate that you already have in your local trust store; if so, you can accept it without going online.

Not to say that the online component of certificate validation isn't important, but it's of varying importance depending on the risk level. When online you should check for certificate revocation, which is to check to see if a previously issued certificate has since been flagged by the CA as compromised and revoked. This can be done by looking for it on a Certificate Revocation List (CRL) published by the signing authority, or by querying the authority's Online Certificate Status Protocol (OCSP) server. But it's an optional step, and can be skipped in low-risk situations (such as being offline.)

Submission + - Pentium 5 - A Rare Look Into The CPU That Could Have Been But Never Was (wccftech.com)

alaskana writes: In late 2022 it was revealed that early samples of what was to be the 'Pentium 5' processor, codenamed Tejas and Jayhawk was in development and made it as far as being released to board partners for evaluation. A few of these samples made it (of course) onto Ebay and then — not surprisingly — into the hands of a YouTuber. To be fair, tech site Anandtech arguably got the first scoop on this P4 successor way back in 2004, but that story seemingly never gained much traction at that time.

Intel Prescott CPUs could hit 5GHz+ but had huge power and temperature numbers, but Tejas was expected to clock higher than Prescott — with Intel chasing the huge 10GHz CPU clocks within 10 years between 2000 and 2011 — but it ended up not happening at all."

In what was supposed to be a continuation of the 'GHz is king' days of the early aughts, the Pentium 5 was in spirit a continuation of the 'faster-is-better' philosophy of the P4 architecture, efficiency be damned. Speeds in excess of 7 GHz(!), and a pipeline upwards of 50 stages were rumored to be targeted by Intel, but reality (and physics) reared their ugly heads as always.

Intel engineer Steve Fischer, who was involved with the project, added: "The thing had a pipeline depth of around 50 stages and an expected clock target at one point north of 7 GHz. I call the thing "the Death Star of processors" and half-jokingly reasoned that consumer acceptance of liquid-cooled chassis would not be a big deal." Intel kicked off Project Tejas in 2003, expected in 2004 and later pushed into 2005 after issues forced Intel to redesign the chip. Before the company could do that, the Tejas Project was shelved on May 7, 2004.

In the end efficiency and parallelization was to be the rule of future CPU development, but the fact that Intel had (at least briefly) had planned on taking the P4 paradigm just a wee bit further with a true Pentium 5 is a fascinating look into the past of a future that never was to be for the venerable Pentium line.


Comment Re: Those things look so bad ass. Please be true. (Score 1) 98

Good public transportation is always empty in Chicago, and it is always a city bus clogging up streets for my Uber.

Public transportation, even if on time, takes 150-300% longer than a car.

It keeps people poor by allowing them to live 90 minutes each way from work instead of making their bosses have to pay them better to afford to live closer.

Comment Re: Drop the gas, use electric (Score 2) 297

Also switched to induction a few years ago and I disagree. With gas you can clearly see the flame, estimate the amount of heat being produced and adjust accordingly. Induction just had some numbers on a display, and heat output varies with the size of the cookware being used. I'm forever fiddling with the controls on my stove, it's always too much heat or too little.

There's a lot to like about induction; the cleanliness, efficiency and lack of pollution but controllability is much inferior to gas.

Slashdot Top Deals

It's a naive, domestic operating system without any breeding, but I think you'll be amused by its presumption.

Working...