Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
A new opiate could, depending on its characteristics, be a most welcome addition. Existing opiates have a lot of drawbacks.
But this? Not nearly as significant as the summary would indicate. On either side of the argument.
I should also note that the various different adapters have some interlock that informs the car how much current can be drawn. And of course the J1772 standard has a facility for this. Additionally, you can force the car to charge at a lower rate by dialing the current down manually.
There also was a report on one of the Tesla forums that a NEMA 14-50 adapter melted while charging at 40A. From the picture it's not clear if it was a fault in the adapter or because it wasn't plugged in properly.
The Model S arrives with two connectors that fit into the connector on the car.. One is an adaptor for a standard SAE J1772 EV charger cable, which makes it possible to charge the Tesla at any Level 1 or Level 2 charging station. You can install one of these in your home if you want, although they aren't cheap. The J1772 plug includes interlocking circuitry that among other things prevents arcing when you disconnect.
The second connector is the so-called universal mobile connector. This is a cable with a plug for the car at one end and a plug that fits various adaptors. A bunch of adaptors are available but the car ships with a NEMA 14-50 (commonly used for RVs) and a standard 3-prong adapter. This thing is quite well made, but there's no way for it to interlock in such a way as to prevent arcing.
There's also a high power wall mount unit available from Tesla. It also has an interlocking scheme.
What a lot of people do - and what Tesla actually recommends - is to install a NEMA 14-50 outlet. They're quite cheap, as in less than $10, and any jackass can install one - or at least thinks they can.
Having spent many years dealing with a wide variety of theatrical lighting equipment that used various NEMA connectors, I'm not a fan of the NEMA 14-50 approach. All it takes is one or two disconnects while the power is flowing to pit both the plug and the socket pretty badly. And that's all it takes to start a fire. This cannot happen with either a J1772 or Tesla charging station.
And even if the outlet is the cause, IMO Tesla does have some responsibility here, because NEMA 14-50 is the approach they recommend.
I did find a recipe for "Saffron, turmeric Roast Turkey with Glutinous fried rice" that looks interesting. I may have to settle for that.
But the geekiest turkey I ever made was from a recipe I saw on TV (which I just looked for but cannot find). The stuffing had over 10 ingredients, which of course took a long time to do. Once the bird is stuffed, you make up a paste of turmeric and some other stuff and slather it all over. Put it in the oven at 500 degrees, wait for the paste to dry, then apply more paste. Keep doing this until the bird is completely enclosed in a thick hard layer. Then let it cook until it's completely black. You then crack it open and serve. The result was excellent, but was way too much trouble to do again.
Additionally, the pilot signal is what tells the car the amount of available amperage, since that's something the car cannot sense, like voltage. I won't bother to go through all of the details of the handshake, but this piece of information is provided by the duty cycle of the 1Khz square wave pilot signal, with 50% indicating 30A available. Not only does this let the car know what power is available so it won't try and draw too much, the amount of power can change over time (when there is, say, a power shortage) and the car responds accordingly.
The plug is also designed so that the signal pins disengage before the power pins, so both ends can sense the impending disconnect and stop the flow of power, preventing arcing.
The plug is also designed to be safe to use in wet conditions. There's also a ground fault detector.
With the exception of the ground fault, which I haven't tried to test for obvious reasons, I can attest to the fact that all of this works flawlessly on the Leaf. The situation with the Tesla Model S is more complex since there's an adapter involved and I haven't been willing to play with it to see what happens, but if anything it should be harder to move the Tesla in park since the emergency break engages automatically.
EVs used to be a big hacked up mess but that time is long since past.
But this doesn't mean Google doesn't also have a lot to answer for. Gmail IMAP compliance in particular is pretty bad, and SMTP handling of error conditions pushes things right to the limits if not past them.
If you, you know, actually read the standard, or even the Wikipedia page, you'll see that DKIM is not intended to be used as a signature mechanism in the same way as S/MIME or PGP. Rather, it's a means to assert responsibility for sending the message, it's done at the domain rather than user level, and verification results are intended to be used for message filtering, not for asserting that so-and-so actually signed the message.
Sure, the underlying technology is based on hashes, signatures, signature verification, and so on but that's because there's no other way to do it. The fact that DKIM allows for the application of relaxed interpretation of both message header and body data kinda tells you it's not intended to be used to provide an absolute assurance that what you got is authentic in every way.
DKIM is also not intended to be the ultimate source of information for filtering. Rather, DKIM results are supposed to be combined with other metrics to form an overall assessment of message validity. And that's a very good thing, since I get all sorts of spammy stuff that makes it through Google, including getting a legitimate DKIN signature attached. Other filtering mechanisms are needed to block such crap.
All that said, it's very disappointing to see yet another case where Google has seen fit to play fast and loose with standards. This is happening much too often.
Every so often I try the various other browsers. So far I've seen no reason to change and lots of reasons not to.
But I thought this was very unusual. Seems it isn't.
FWIW, I used to do a lot of laser spectroscopy work, so this is not entirely familiar territory.
Of course it depends to some extent on how the results are being used. If they are being used for purposes of exclusion of suspects, or as a means of narrowing a search, reliability or admissibility may have yet to be tested. But sooner or later they will be. I just hope it happens before this gets widely accepted and someone gets hurt.
On a personal note, I drink bottled water almost exclusively for health reasons (immune suppressed and bottled water has, on average, lower bacterial counts than tap). But I buy what's cheapest and available, which means I switch brands all the time. Assuming water does account for the majority of the isotopes these tests check, the stuff I'm drinking right now comes from two different sources, one 600+ miles north, the other 200+ miles northeast of here. Since this is in California, that's not exactly narrowing things down.
I liked Finnegan's Wake enough to read it a couple of times. Then again, "de gustibus non est disputandum" is kind of the point here.