A completly different direction for a suggestion, but...
Have you tough about setting up some server ? (On you own home server. I'm sure as a/. geek you have on of those. Just hoping that your basement and your mom's house have a good connection).
Some Dovecot or Courrier-Imap to hold the her e-mail folders ?
- Migrating is basically just drag-droping the local folders into the imap server's folder ?
- In case of Thunderbird going berzerk you can still re-download everything from the Imap server.
- In case of something that your mom ends up liking more than Thunderbird, it's basically just about pointing that tool to the same home imap server.
- The above use Maildir, which a lot simpler to backup/restore than mbox. and are lot less corruption sensitive (as they are 1 file per mail, 1 directory per folder. instead of 1 file per folder)
Drawbacks : whenever network drops between your mom's apartment and the your basement's server, she only get the latest pre-failure snapshot.
---
And on a un-related note, Mozilla are considering making a plug-in based mail storage, which could make using Maildir directly in Thunderbird possible (once all the remaining bugs are closed). That would also make her mails better to backup and less corruption prone, and also a tiny bit easier to move across different maildir-based clients.
- Everything even remotely container-related (Cgroups & Co) is missing. No LXC/Docker*/systemd-nspawn/etc. for you. - Filesystems are limited to either mount an NTFS directory as a data dir, or a special NTFS directory with some metadata as a POSIX-compliant root. You can't get any other typical Linux filesystems, even the popular one, so forget about modern facilities like free snapshotting, and most of the weird stuff is either poorly supported (different visibility of mounts) or missing (layers).
And these are the first two out of the top of my head.
(We could add : no DRM gfx stack, you're limited to X forwarding over SSH, so no wayland compositing either)
(Also, in the perspective of what Microsoft wanted to achieve before pivoting to WSL: it still can't run the Android user-space successfully. So, still no app ecosystem on Windows 10 phone that isn't a joke. But at least they got WSL to run on ARM too).
Basically, all you get is enough API to work with cli tools and daemons.
But hey, at least WSL doesn't work with systemd so at least this will keep the Devuan whiners crowd happy~~~
Well actually, Debian do call their "GNU/Linux", for the very practical reason that they also try other combinations such as Debian GNU/kFreeBSD, Debian GNU/Hurd, etc.
(And if you squint at it you'll notice that none of the Linux distribution in the microsoft app store actually still has bits from Linus' kernel. Per Stallman's classification, those should be called GNU/NTkernel, it's still your garden variety distro, but running agaisnt the WinNT kernel and it's ability to also speak a minimalist subset of Linux kernel API. So they are thing called "Linux" distro that litteraly contain no bits of the actual Linux kernel)
I've studied old greek in high school, thus a long time ago. Most of my sources are printed on paper (and collection dust out of my reach somewhere back at my parent's)
As an online encyclopedia that usually is valued a lot by those who think wikipedia is utter garbage, I would point to Britanica.
Among all the paper source I've had, the mythology books by Robert Graves were among my favorite (and will cover way much more than simple trivial elements like what are Greek god's traditional epithets).
And you know you could use this question as an opening to go talk to that cute geeky shy girl from humanities.
Yeah, and once Facebook crumbles : where are you going to run to ?
Instagram ? WhatsApp ?
At most, Mark is going to say "meh", and make a mental note to make another attempt at buying Snap, to be ready for the up-coming next crumbling after the facebook's one.
The problem is that the car is basically built around the battery.
I agree, we could even say, that you basically are buying a giant battery from Tesla, and for that price, they throw in a car bolted on it for cheap. (Given the relative price).
It's even more noticeable with manufacturer where the car and the battery can by sold separately (e.g.: Renault - the 45kWh battery costs around 10k EUR)
It is installed into the vehicle partially with adhesives,
Maybe in the latest models? (the platform used to build model 3 upon, maybe ? I haven't been following that in details)
But older platfroms where designed with battery swapping in mind, I've read. Supposedly, once the shield is disassembled, the battery module should be coming out relatively easily). I'll have to find back 3rd party sources.
Similarly a lot of other cars have also been planned with battery swapping. Most manufacturer though the idea seemed logical.
which is why Tesla probably never actually swapped a single customer battery.
I though it was the general lack of interest from the public which caused manufacturers of e-cars such as Telsa to drop the idea of battery swaps.
Already back the first Tesla, but nowadays nearly all electric vehicle (except for the cheapest alternative entry-level in the range) have batteries that enable the driver to driver for at least 2-3 hours in a row. By which time taking a break is *extremely strongly* recommended. (Or even mandatory for professional drivers in some European jurisdictions - such as FR and CH, at least). And thus leaving the car plugged-in for half an hour or an hour while taking a leak, having a coffee, eating something or even taking a power-nap is perfectly acceptable for most drivers of e-cars, thus the general lack of interested for swap by owners.
Only the marginal "drive 8 hours straight without a stop ! go pee in a plastic bottle !!!" insane crowd would be clamoring for fast swaps.
Here's Elon Musk wrap-up about the abandoned battery swap : they invited 100 clients to test the battery swaps, only 5 them did swap battery and each only swapped once, no-one trying again. (Okay, it's not a third party's analysis, it's Elon himself and he might be telling whatever is needed to make the investors happy and confident).
But, you can find similar analysis about consumer battery swap from every single other company which did consider the idea. Renault-Nissan CEO similarly reporting they're dropping swaps, also due to lack of interest from the public. General sum-up about the trend.
Note that this is specific for consumer cars.
In some professional settings, battery swaps make actually entirely sense. Buses and vans are such things : it makes more sense to swap the driver and the batteries while the remaining of the giant vehicle is used on the next shift (with a fresh rested new driver and a new fully charged battery pack). Instead of having the drivers napping in a hammock and the giant fricking vehicle staying plugged into a charger.
(They didn't actually swap the battery in their stage demonstration, either; Tesla has literally never shown a single battery swap.)
Did they do an actual full blown battery swap ? Probably not. (Elon doesn't even mention how the disconnect/reconnect the batteries from the liquid cooling loop. Redundant Zero-spill Quick-disconnect valves, perhaps ?) But they proved that it's not impossib
In the context of abortion, it merely means "to stop the pregnancy". (Hence RMS' joke about proper ways to stopping a program and government allowing/forbidding the mention of it).
That you consider this a "child killing" is merely a reflection of the specific way "the point at which life begins" happens to be defined in the peculiar mythology you decided to believe in. Please keep in mind that not everyone took the same decision as you.
Hades is the Greek god of the underworld. Pluto is the Roman version.
And in old greek, Plouton is one of Hades' epithets - i.e.: adjectives often used together with His name to describe Him. (Just like Zeus Himself is usually "all-seeing" or the "storm gatherer", etc.)
It means "the rich / the rich-giver", because Hades is the god of the underworld and earth itself (as opposed to Posseidon who's got the seas and Zeus who's in charge of the sky), and that's where most of mines are and on what crops grow. (Might also have been because, except for heros, most mortals - both good and bad ones - end up in Hades' realm - different sections of the underworld serve as both hell *and* heaven, unlike in christian mythology - so He ends up with the most follower).
Over time, this has shifted to his euphemistical name (the thing mortals use to name him as to not anger Him) He became known "The Rich / The Rich Giver". (Just like in christian mythology, Satan is called often "the devil" instead of by his name).
And then again, over time this became used as His official name. That's what the Romans eventually picked-up in Latin.
Fun fact, the Latin "Jupiter" (in nominative case) has a similar construction : it's the contraction of "Zeus + pater" ("the father" - obviously once you look at the genealogy of most of the Greeko-Roman pantheon). But when declined in other cases, only the name is kept, e.g.: Jovis (genetive case).
So for some period of time "Pluto" is also what the Greel go of the underworld was called, and even for some period of time it was His actual name.
Also why is Google trying to re-invent PGP and S/MIME, badly ?
These already work nicely for confidential information : only the person holding a private key for which a message was encrypted can every see the actual message.
If an encrypted message ends up in the wrong hands, that mistaken destinary will NOT be able to open it anyway due not missing the private key.
The only difference is that a *decrypted* message could be copied-and-pasted from and a user could end up repackaging the information in another (non encrypted) message. Whereas here, GMail's confidential mode pretends to do something to prevent copy-paste and printing... and in practice is completely failing at it just as suggested.
You cannot trust somebody else's computer to do what you want to do. No matter how much clever javascript you put into your stupid stuff, at best you're still vulnerable to good old "analog hole" (i.e.: take a picture with a camera as suggested), at worse the target browser can be told to ignore any anti-printing hooks (e.g.: just hold "shift" while right-clicking, you'll get the default browser alt menu, no mater what the javascript tries to overload).
The only thing that you can trust is that, thanks to correctly executed cryptography, your message reaches its intended destination without any unwanted 3rd party able to peer along the way. Once the intended person has de-crypted it, you cannot control anything. PGP (such as GPG, EnigMail Thunderbid plugin, Mailvelope browser plugin, etc.) and S/MIME have solved this a long time ago (with difference in the way trust is handled)
No need for google to invent a poorer solution... Oh yes, I get it. Current working solution happen to *also* prevent Google from peering into your e-mail, so they cannot contextualize and get less efficient at selling your eyeballs to advertisers, and earn less money. That's why they need a poorer solution than PGP and S/MIME.
The battery catching fire is an interesting point. I'd be interested to know if the emergency responders initially followed the published guidelines for cooling the battery or if they stopped when they stopped seeing flames.
As far as I've understood, the crash was this time so violent, that it damaged the integrity of the battery pack.
There might still be some conductors shorted by the deformation here and there, in such was the thermal fuse wouldn't break. The shorted cell keeps warming and eventually get hot enough to burst into falme re-starting the fire.
A damaged battery on any gadget (not only specificially electric cars) should be considered as a potential hazard and should immediately by removed and put in a secure place (= a place where the pack wouldn't damade anything if/when it reignites).
(that Li-ON is even less stable than some of us may have realized)
what ? who youldn't ? where they born after the 2000s ? Weren't they paying attention with the Samsung Galaxy recently ? If anything, Sony's problem with bad quality batteries back them (and reconfirmed recently with Samsung) would have told us already that battery LiIon/LiPo battery have a certain tendency to blow up whenever you look wrong at them.
Disconnecting and removing Lithium battery from a damaged device should be standard practice.
And if a Tesla car had such a violent crash that the battery pack integrity seems compromised, not disassembling and removing them is inviting for such troubles.
N2 at normal pressure isn't soluble enough in blood, so it won't reach the nerves in enough quantity and won't have any effect. The single effect it has, is that by putting more than the normal fraction of N2 in the air, you give less remain room for O2. And the body doesn't pay attention to O2 levels (otherwise you couldn't go in a mountain without feeling painful suffocation. Instead you only feel tiredness), so the victim will run out of O2 without noticing. (Body only pays attention to build-up of CO2)
N2 is only soluble at high pressure that's why it's dangerous for divers (normal fraction of N2 times the increased pressures = pressure high enough to get soluble in the blood in significant quantity, divers gets high on N2) (also, divers goes up to fast without decompression steps, N2 decompresses, suddenly isn't soluble anymore at that lower pressure, this excendant N2 forms bubbles, these bubbles cause damage).
Example: let's say you're going to one of those restaurants where you pay a 'penalty' for no show (but you, the person instructing the Duplex don't know this); the human mentions this to the Duplex. Is this a valid contract? Who knows?
How does a business that makes you pay a penalty for no show would *actually make you pay* the penalty *when you don't show* ?! I'm genuinely interested ?
Do they request your credit card information at the moment of the table reservation, the same as hotels with similar penalty do ? Do they ask for these it *over the phone* ? (remember, the whole purpose of Google Duplex is to give a computer-to-human interface for booking business that still lack any modern reservations system and still rely solely on a human answering the phone) That would be a gigantic security failure. (And even technical impossibility: lots of modern European Chip-and-PIN credit card cannot be billed without a second form of confirmation. If it's not a terminal asking for a pin code, nor a website implementing 3DSecure - then either the credit card company calls you directly to confirm or you need to use the card's smartphone app to confirm the transaction out-of-band)
(Which, by the way gives a clear path google : - simply refuse to book restaurants that ask credit cards information on the phone. Which again, makes sens from a security and technical point of view. or alternatively : - give a special credit card number which is operated by google, and insured against fraud and even insured against "no show" as part as a paid-for service to monetize Duplex)
You just burn it and write "System ABC, release XYZ" - done.
Serious question : How often do you need go back to a specific version of a certain GNU/Linux distro ?
In most of the use cases I've been through, I generally need "whatever is the most up-to-date and patched release of distro 'Xyz' or LTS version of distro 'Abc' ", so generally, fetching an up to date installation iso (usually the minimalist Net install that will then pull the uptodate installer and package from the net) and writing it to a bootable USB key is the way to go.
I've rarely needed to keep archives of older installation media.
So I was wondering what your uses cases are.
---
As opposed to Windows world, where you need to have the specific major version (10, 7, or even older stuff like XP) for which said machine has a valid license, and full service pack release only happen every now an then, so it makes sense to carry around a collection of the latest service pack for each recent major Windows version.
Which by itself might be of interest for some attacker who would use this information (and combine it with others) to start-up a process of ID theft or social engineering.
Also you might have had to register your phone number as a 2FA or fall-back on some websites that still rely on such an insecure solution for 2FA. So quickly steeling/borrowing your phone to impersonate you on such a website might be another motivation.
You're not as juicy as a target as dumb people who'll keep their passwords in an un-encrypted "Note", but you might still interest a few.
The problem, is that the phone has tons of juicy bits that you have to leave on the phone.
- The credentials used by that app that you bank forces you to install as a 2factor.
- The database of received messages where any new incoming SMS will show up, if your bank still uses that as a 2factor
- Some direct payment app that you need because it's used a lot around where you live (also around where I live, the app is using a common standard and each bank is providing a compatible app. You actually do NOT need to rely on a 3rd party like VISA or Mastercard, which might be an interesting argument by people who insist in using it).
- tons of personnal information which part of a normal functioning phone (contacts database) that you need to have around if you don't want to memorize and type every single phone number, but that could become handy for ID theft and/or social engineering.
etc.
In short people who don't use their smartphone a glorified keypad-dumb-phone/gaming console tend to have tons of bits of information that sound really tasty to any attacker that would want to access them. (And as lots of other/.ers and even professional cryptographers have shown : there's no way to open an access only for the law-enforcement while at the same time locking out all the potential criminals).
So you need a way to lock your data safely on the phone to prevent abuse. That's why, a lot of people have a strong desire to keep their phone locked even if they have "nothing to hide". (Because they have tons of legal infromation that they genuinely need "to hide" against potential attacker. And be damned the (comparatively fewer) cases where it blocks law enforcement).
Just let Google Duplex handle all flirting and dating smalltalk tasks,
Made me think of this video (around 2:45, the guys uses a "wingman" app to help on his date).
Of course, the creepiest part is a few of the current "big AI companies" probably have the kind of data resource to attempt training this kind of stuff for real. (And some like Uber are already training simple systems to spot one-night-stands in their database).
ChromeOS uses the Linux kernel (and very often a modern one, thanks to Google putting some efforts with hardware manufacturer). Debian GNU/Linux also relies on a Linux kernel, hence the name.
Linux has been having containerization capabilities for quite some time (back when LXC started the whole craze that lead to modern-day Docker).
The "sandboxing" is probably just a different container running from the same kernel, with no ressource costs at all.
They're probably doing the same kind of things that crouton has been doing, but with full kernel's containerization instead of only chroot.
But for what fraction of those "decades" have you been able to buy a compact GNU/Linux laptop in major electronics store chains?
Approximately since the ASUS eeePC started the "sub-notebook with Linux in your local store" craze (followed imediatly by Acer. And then countless no-name Asian manufacturer spitting crappier machines) , that subsequently jump-started the whole wave of Chromebooks, once google decided to address the "userfriendly so even your grandma can use it" part and the "minimal quality so the machine isn't full crap".
p.s. I thought it was a GPLv3 violation to "TiVoize" Linux. Does this mean Chrome OS was using GPLv2?
The Linux kernel (the thing written by Linus Torvalds) is still GPLv2 because:
- Linus doesn't want to enforce anti-TiVoization (he's more on the programatic vs. ideological scale than RMS. He's fine with locked devices that still provide source code for curious users. RMS is the one who doesn't like something that can be considered as "someone else's computer")
- The current kernel license is litterally "GPLv2 only", not "GPLv2 or any future version". All the authors that have contributed to Linux have agreed to release their patches under the same "GPLv2 only" license, and the kernel doesn't use "attribution" (the author of some piece of code remain the owner of that piece of code. The propriety of bits of the kernel don't automatically shift to Linus). Switching to GPLv3 would require contacting every single last author that has still owning bits in the kernel and ask them to accept re-licensing to either "GPLv2+" or "GPLv3" (or GPLv3+). Not realistically feasible.
There are huge swaths of GNU userland (e.g.: most of the parts that the FSF is taking care of) and other userland components that have switched to GPLv3. But typical chrome book doesn't use that many of them (e.g.: there's no GCC compiler installed).
ChromeBook aren't TiVoized, they are made user-friendly/idiot-proof (that's why top poster said "hiding", not "blocking you from").
- A dev can install whatever they want if they turn the dev mode on.
- But a clueless use should be able to revert back to original factory state with a couple of key press. (And that's where the problem lies currently. Is way to easy for a clueless roommate/child to wipe a dev's chromebook)
- These thing use Coreboot open firmware. It's opensource. For a power use, it's not that complicated to reflash them to a new custom firmware that will accept any full-blown GNU/Linux installation without making it too easy to self-destruct.
(But I think a lot of devs, prefer to have the light "chromebook" experience and only open a sandbox for their linux-ing needs).
Most likely point of failure is the local internet connection at the venue, not the server.
I'm merely pointing at what I'm hypothesizing is the invoked reason (so they can slap "Blockchain" to their idea and attract VCs).
Of course it's blindly simple to make a robust and mostly offline system for a music festival. (With a fall back to "customer service" queue).
And the most likely point of failure in practice is the actual physical processing of guests at the gate (bags checks, pat downs, depending on the local culture). The personnel at the gate will start complaining not being able to process guests fast enough / The guests will start protesting that they wait way too much, long before any half decent ticketing system is overwhelmed.
There have been airlines that shut down all flights because their ticketing systems had issues. {...} For most cases, I don't see any real benefit from this product that can't already be done via existing and simpler methods at the same or greater speed and cost...
Yup indeed, we're talking about concert tickets here and as you point out they are much more simple to implement in a robust.
Not a system where even the Internal Affairs Dept. of the Democratic Republic of Bannanistan should be able to append suspected terrorist to "no-fly" lists and send requests to your Airline Company to deny boarding to that suspect in almost real-time.
More a system where in worst case you can dump the whole list of currently valid S/N on the checking devices themselves (but most often, as I've usually seen, have a local (optionally off-line) server with a local cache of the DB talking to the checking devices offline).
Send the few problematic cases to the special "customer service" queue.
Slashdot Mirror
Storing mail in its own mbox format is a weakness. Calling it standard mbox is still wrong.
Eventually, Maildir will be coming to Thunderbird.
A completly different direction for a suggestion, but...
Have you tough about setting up some server ? /. geek you have on of those. Just hoping that your basement and your mom's house have a good connection).
(On you own home server. I'm sure as a
Some Dovecot or Courrier-Imap to hold the her e-mail folders ?
- Migrating is basically just drag-droping the local folders into the imap server's folder ?
- In case of Thunderbird going berzerk you can still re-download everything from the Imap server.
- In case of something that your mom ends up liking more than Thunderbird, it's basically just about pointing that tool to the same home imap server.
- The above use Maildir, which a lot simpler to backup/restore than mbox. and are lot less corruption sensitive (as they are 1 file per mail, 1 directory per folder. instead of 1 file per folder)
Drawbacks : whenever network drops between your mom's apartment and the your basement's server, she only get the latest pre-failure snapshot.
---
And on a un-related note, Mozilla are considering making a plug-in based mail storage, which could make using Maildir directly in Thunderbird possible (once all the remaining bugs are closed).
That would also make her mails better to backup and less corruption prone, and also a tiny bit easier to move across different maildir-based clients.
- Everything even remotely container-related (Cgroups & Co) is missing. No LXC/Docker*/systemd-nspawn/etc. for you.
- Filesystems are limited to either mount an NTFS directory as a data dir, or a special NTFS directory with some metadata as a POSIX-compliant root. You can't get any other typical Linux filesystems, even the popular one, so forget about modern facilities like free snapshotting, and most of the weird stuff is either poorly supported (different visibility of mounts) or missing (layers).
And these are the first two out of the top of my head.
(We could add : no DRM gfx stack, you're limited to X forwarding over SSH, so no wayland compositing either)
(Also, in the perspective of what Microsoft wanted to achieve before pivoting to WSL: it still can't run the Android user-space successfully.
So, still no app ecosystem on Windows 10 phone that isn't a joke. But at least they got WSL to run on ARM too).
Basically, all you get is enough API to work with cli tools and daemons.
But hey, at least WSL doesn't work with systemd so at least this will keep the Devuan whiners crowd happy~~~
---
* : apparently, the latest linux docker on the latest WSL insider built could successfully run hello-world. By basically skipping and/or ignoring most of the missing stuff. It's basically a glorified chroot. You're still better off installing the windows version of docker and use WSL to control it with the CLI (and the long term path would probably be having the Windows docker able to start a separate WSL context for each container).
But gravity, it's only a theory !
Teach the controversy!
#IntelligentFalling
---
(Sorry couldn't resist to make the joke)
Well actually, Debian do call their "GNU/Linux", for the very practical reason that they also try other combinations such as Debian GNU/kFreeBSD, Debian GNU/Hurd, etc.
(And if you squint at it you'll notice that none of the Linux distribution in the microsoft app store actually still has bits from Linus' kernel.
Per Stallman's classification, those should be called GNU/NTkernel, it's still your garden variety distro, but running agaisnt the WinNT kernel and it's ability to also speak a minimalist subset of Linux kernel API.
So they are thing called "Linux" distro that litteraly contain no bits of the actual Linux kernel)
I've studied old greek in high school, thus a long time ago.
Most of my sources are printed on paper (and collection dust out of my reach somewhere back at my parent's)
As an online encyclopedia that usually is valued a lot by those who think wikipedia is utter garbage, I would point to Britanica.
Among all the paper source I've had, the mythology books by Robert Graves were among my favorite (and will cover way much more than simple trivial elements like what are Greek god's traditional epithets).
And you know you could use this question as an opening to go talk to that cute geeky shy girl from humanities.
What did we do before facebook?
A significant part was doing MySpace.
Why do we have to run to anything?
Mostly because of FOMO.
Yeah, and once Facebook crumbles : where are you going to run to ?
Instagram ?
WhatsApp ?
At most, Mark is going to say "meh", and make a mental note to make another attempt at buying Snap, to be ready for the up-coming next crumbling after the facebook's one.
The problem is that the car is basically built around the battery.
I agree, we could even say, that you basically are buying a giant battery from Tesla, and for that price, they throw in a car bolted on it for cheap.
(Given the relative price).
It's even more noticeable with manufacturer where the car and the battery can by sold separately (e.g.: Renault - the 45kWh battery costs around 10k EUR)
It is installed into the vehicle partially with adhesives,
Maybe in the latest models? (the platform used to build model 3 upon, maybe ? I haven't been following that in details)
But older platfroms where designed with battery swapping in mind, I've read. Supposedly, once the shield is disassembled, the battery module should be coming out relatively easily). I'll have to find back 3rd party sources.
Similarly a lot of other cars have also been planned with battery swapping. Most manufacturer though the idea seemed logical.
which is why Tesla probably never actually swapped a single customer battery.
I though it was the general lack of interest from the public which caused manufacturers of e-cars such as Telsa to drop the idea of battery swaps.
Already back the first Tesla, but nowadays nearly all electric vehicle (except for the cheapest alternative entry-level in the range) have batteries that enable the driver to driver for at least 2-3 hours in a row. By which time taking a break is *extremely strongly* recommended. (Or even mandatory for professional drivers in some European jurisdictions - such as FR and CH, at least). And thus leaving the car plugged-in for half an hour or an hour while taking a leak, having a coffee, eating something or even taking a power-nap is perfectly acceptable for most drivers of e-cars, thus the general lack of interested for swap by owners.
Only the marginal "drive 8 hours straight without a stop ! go pee in a plastic bottle !!!" insane crowd would be clamoring for fast swaps.
Here's Elon Musk wrap-up about the abandoned battery swap : they invited 100 clients to test the battery swaps, only 5 them did swap battery and each only swapped once, no-one trying again. (Okay, it's not a third party's analysis, it's Elon himself and he might be telling whatever is needed to make the investors happy and confident).
But, you can find similar analysis about consumer battery swap from every single other company which did consider the idea.
Renault-Nissan CEO similarly reporting they're dropping swaps, also due to lack of interest from the public.
General sum-up about the trend.
Note that this is specific for consumer cars.
In some professional settings, battery swaps make actually entirely sense.
Buses and vans are such things : it makes more sense to swap the driver and the batteries while the remaining of the giant vehicle is used on the next shift (with a fresh rested new driver and a new fully charged battery pack).
Instead of having the drivers napping in a hammock and the giant fricking vehicle staying plugged into a charger.
(They didn't actually swap the battery in their stage demonstration, either; Tesla has literally never shown a single battery swap.)
https://www.youtube.com/watch?...
- 1.16 : bolt un-screwer visible.
- 1.30 : lower shield + battery assembly being visibly lowered.
- 2.00 : lower shield + battery assembly being visibly raised.
Did they do an actual full blown battery swap ? Probably not. (Elon doesn't even mention how the disconnect/reconnect the batteries from the liquid cooling loop. Redundant Zero-spill Quick-disconnect valves, perhaps ?)
But they proved that it's not impossib
To "abort" means to "stop". That's it.
In the context of abortion, it merely means "to stop the pregnancy". (Hence RMS' joke about proper ways to stopping a program and government allowing/forbidding the mention of it).
That you consider this a "child killing" is merely a reflection of the specific way "the point at which life begins" happens to be defined in the peculiar mythology you decided to believe in. Please keep in mind that not everyone took the same decision as you.
Hades is the Greek god of the underworld. Pluto is the Roman version.
And in old greek, Plouton is one of Hades' epithets - i.e.: adjectives often used together with His name to describe Him. (Just like Zeus Himself is usually "all-seeing" or the "storm gatherer", etc.)
It means "the rich / the rich-giver", because Hades is the god of the underworld and earth itself (as opposed to Posseidon who's got the seas and Zeus who's in charge of the sky), and that's where most of mines are and on what crops grow. (Might also have been because, except for heros, most mortals - both good and bad ones - end up in Hades' realm - different sections of the underworld serve as both hell *and* heaven, unlike in christian mythology - so He ends up with the most follower).
Over time, this has shifted to his euphemistical name (the thing mortals use to name him as to not anger Him) He became known "The Rich / The Rich Giver". (Just like in christian mythology, Satan is called often "the devil" instead of by his name).
And then again, over time this became used as His official name. That's what the Romans eventually picked-up in Latin.
Fun fact, the Latin "Jupiter" (in nominative case) has a similar construction : it's the contraction of "Zeus + pater" ("the father" - obviously once you look at the genealogy of most of the Greeko-Roman pantheon). But when declined in other cases, only the name is kept, e.g.: Jovis (genetive case).
So for some period of time "Pluto" is also what the Greel go of the underworld was called,
and even for some period of time it was His actual name.
Also why is Google trying to re-invent PGP and S/MIME, badly ?
These already work nicely for confidential information :
only the person holding a private key for which a message was encrypted can every see the actual message.
If an encrypted message ends up in the wrong hands, that mistaken destinary will NOT be able to open it anyway due not missing the private key.
The only difference is that a *decrypted* message could be copied-and-pasted from and a user could end up repackaging the information in another (non encrypted) message.
Whereas here, GMail's confidential mode pretends to do something to prevent copy-paste and printing... and in practice is completely failing at it just as suggested.
You cannot trust somebody else's computer to do what you want to do. No matter how much clever javascript you put into your stupid stuff, at best you're still vulnerable to good old "analog hole" (i.e.: take a picture with a camera as suggested), at worse the target browser can be told to ignore any anti-printing hooks (e.g.: just hold "shift" while right-clicking, you'll get the default browser alt menu, no mater what the javascript tries to overload).
The only thing that you can trust is that, thanks to correctly executed cryptography, your message reaches its intended destination without any unwanted 3rd party able to peer along the way. Once the intended person has de-crypted it, you cannot control anything.
PGP (such as GPG, EnigMail Thunderbid plugin, Mailvelope browser plugin, etc.) and S/MIME have solved this a long time ago (with difference in the way trust is handled)
No need for google to invent a poorer solution... Oh yes, I get it. Current working solution happen to *also* prevent Google from peering into your e-mail, so they cannot contextualize and get less efficient at selling your eyeballs to advertisers, and earn less money. That's why they need a poorer solution than PGP and S/MIME.
The battery catching fire is an interesting point. I'd be interested to know if the emergency responders initially followed the published guidelines for cooling the battery or if they stopped when they stopped seeing flames.
As far as I've understood, the crash was this time so violent, that it damaged the integrity of the battery pack.
There might still be some conductors shorted by the deformation here and there, in such was the thermal fuse wouldn't break.
The shorted cell keeps warming and eventually get hot enough to burst into falme re-starting the fire.
A damaged battery on any gadget (not only specificially electric cars) should be considered as a potential hazard and should immediately by removed and put in a secure place (= a place where the pack wouldn't damade anything if/when it reignites).
(that Li-ON is even less stable than some of us may have realized)
what ? who youldn't ?
where they born after the 2000s ? Weren't they paying attention with the Samsung Galaxy recently ?
If anything, Sony's problem with bad quality batteries back them (and reconfirmed recently with Samsung) would have told us already that battery LiIon/LiPo battery have a certain tendency to blow up whenever you look wrong at them.
Disconnecting and removing Lithium battery from a damaged device should be standard practice.
And if a Tesla car had such a violent crash that the battery pack integrity seems compromised, not disassembling and removing them is inviting for such troubles.
N2 at normal pressure isn't soluble enough in blood, so it won't reach the nerves in enough quantity and won't have any effect.
The single effect it has, is that by putting more than the normal fraction of N2 in the air, you give less remain room for O2. And the body doesn't pay attention to O2 levels (otherwise you couldn't go in a mountain without feeling painful suffocation. Instead you only feel tiredness), so the victim will run out of O2 without noticing.
(Body only pays attention to build-up of CO2)
N2 is only soluble at high pressure that's why it's dangerous for divers (normal fraction of N2 times the increased pressures = pressure high enough to get soluble in the blood in significant quantity, divers gets high on N2) (also, divers goes up to fast without decompression steps, N2 decompresses, suddenly isn't soluble anymore at that lower pressure, this excendant N2 forms bubbles, these bubbles cause damage).
Example: let's say you're going to one of those restaurants where you pay a 'penalty' for no show (but you, the person instructing the Duplex don't know this); the human mentions this to the Duplex. Is this a valid contract? Who knows?
How does a business that makes you pay a penalty for no show would *actually make you pay* the penalty *when you don't show* ?!
I'm genuinely interested ?
Do they request your credit card information at the moment of the table reservation, the same as hotels with similar penalty do ?
Do they ask for these it *over the phone* ? (remember, the whole purpose of Google Duplex is to give a computer-to-human interface for booking business that still lack any modern reservations system and still rely solely on a human answering the phone)
That would be a gigantic security failure.
(And even technical impossibility: lots of modern European Chip-and-PIN credit card cannot be billed without a second form of confirmation. If it's not a terminal asking for a pin code, nor a website implementing 3DSecure - then either the credit card company calls you directly to confirm or you need to use the card's smartphone app to confirm the transaction out-of-band)
(Which, by the way gives a clear path google :
- simply refuse to book restaurants that ask credit cards information on the phone. Which again, makes sens from a security and technical point of view.
or alternatively :
- give a special credit card number which is operated by google, and insured against fraud and even insured against "no show" as part as a paid-for service to monetize Duplex)
You just burn it and write "System ABC, release XYZ" - done.
Serious question : How often do you need go back to a specific version of a certain GNU/Linux distro ?
In most of the use cases I've been through, I generally need "whatever is the most up-to-date and patched release of distro 'Xyz' or LTS version of distro 'Abc' ",
so generally, fetching an up to date installation iso (usually the minimalist Net install that will then pull the uptodate installer and package from the net) and writing it to a bootable USB key is the way to go.
I've rarely needed to keep archives of older installation media.
So I was wondering what your uses cases are.
---
As opposed to Windows world, where you need to have the specific major version (10, 7, or even older stuff like XP) for which said machine has a valid license, and full service pack release only happen every now an then, so it makes sense to carry around a collection of the latest service pack for each recent major Windows version.
the only thing on it is contact list
Which by itself might be of interest for some attacker who would use this information (and combine it with others) to start-up a process of ID theft or social engineering.
Also you might have had to register your phone number as a 2FA or fall-back on some websites that still rely on such an insecure solution for 2FA.
So quickly steeling/borrowing your phone to impersonate you on such a website might be another motivation.
You're not as juicy as a target as dumb people who'll keep their passwords in an un-encrypted "Note", but you might still interest a few.
The problem, is that the phone has tons of juicy bits that you have to leave on the phone.
- The credentials used by that app that you bank forces you to install as a 2factor.
- The database of received messages where any new incoming SMS will show up, if your bank still uses that as a 2factor
- Some direct payment app that you need because it's used a lot around where you live
(also around where I live, the app is using a common standard and each bank is providing a compatible app. You actually do NOT need to rely on a 3rd party like VISA or Mastercard, which might be an interesting argument by people who insist in using it).
- tons of personnal information which part of a normal functioning phone (contacts database) that you need to have around if you don't want to memorize and type every single phone number, but that could become handy for ID theft and/or social engineering.
etc.
In short people who don't use their smartphone a glorified keypad-dumb-phone/gaming console tend to have tons of bits of information that sound really tasty to any attacker that would want to access them. /.ers and even professional cryptographers have shown : there's no way to open an access only for the law-enforcement while at the same time locking out all the potential criminals).
(And as lots of other
So you need a way to lock your data safely on the phone to prevent abuse.
That's why, a lot of people have a strong desire to keep their phone locked even if they have "nothing to hide".
(Because they have tons of legal infromation that they genuinely need "to hide" against potential attacker. And be damned the (comparatively fewer) cases where it blocks law enforcement).
Just let Google Duplex handle all flirting and dating smalltalk tasks,
Made me think of this video (around 2:45, the guys uses a "wingman" app to help on his date).
Of course, the creepiest part is a few of the current "big AI companies" probably have the kind of data resource to attempt training this kind of stuff for real.
(And some like Uber are already training simple systems to spot one-night-stands in their database).
ChromeOS uses the Linux kernel (and very often a modern one, thanks to Google putting some efforts with hardware manufacturer).
Debian GNU/Linux also relies on a Linux kernel, hence the name.
Linux has been having containerization capabilities for quite some time (back when LXC started the whole craze that lead to modern-day Docker).
The "sandboxing" is probably just a different container running from the same kernel, with no ressource costs at all.
They're probably doing the same kind of things that crouton has been doing, but with full kernel's containerization instead of only chroot.
But for what fraction of those "decades" have you been able to buy a compact GNU/Linux laptop in major electronics store chains?
Approximately since the ASUS eeePC started the "sub-notebook with Linux in your local store" craze (followed imediatly by Acer. And then countless no-name Asian manufacturer spitting crappier machines) , that subsequently jump-started the whole wave of Chromebooks, once google decided to address the "userfriendly so even your grandma can use it" part and the "minimal quality so the machine isn't full crap".
So since slightly more than 1 decade.
p.s. I thought it was a GPLv3 violation to "TiVoize" Linux. Does this mean Chrome OS was using GPLv2?
The Linux kernel (the thing written by Linus Torvalds) is still GPLv2 because:
- Linus doesn't want to enforce anti-TiVoization (he's more on the programatic vs. ideological scale than RMS. He's fine with locked devices that still provide source code for curious users. RMS is the one who doesn't like something that can be considered as "someone else's computer")
- The current kernel license is litterally "GPLv2 only", not "GPLv2 or any future version". All the authors that have contributed to Linux have agreed to release their patches under the same "GPLv2 only" license, and the kernel doesn't use "attribution" (the author of some piece of code remain the owner of that piece of code. The propriety of bits of the kernel don't automatically shift to Linus). Switching to GPLv3 would require contacting every single last author that has still owning bits in the kernel and ask them to accept re-licensing to either "GPLv2+" or "GPLv3" (or GPLv3+). Not realistically feasible.
There are huge swaths of GNU userland (e.g.: most of the parts that the FSF is taking care of) and other userland components that have switched to GPLv3. But typical chrome book doesn't use that many of them (e.g.: there's no GCC compiler installed).
ChromeBook aren't TiVoized, they are made user-friendly/idiot-proof (that's why top poster said "hiding", not "blocking you from").
- A dev can install whatever they want if they turn the dev mode on.
- But a clueless use should be able to revert back to original factory state with a couple of key press.
(And that's where the problem lies currently. Is way to easy for a clueless roommate/child to wipe a dev's chromebook)
- These thing use Coreboot open firmware. It's opensource. For a power use, it's not that complicated to reflash them to a new custom firmware that will accept any full-blown GNU/Linux installation without making it too easy to self-destruct.
(But I think a lot of devs, prefer to have the light "chromebook" experience and only open a sandbox for their linux-ing needs).
Most likely point of failure is the local internet connection at the venue, not the server.
I'm merely pointing at what I'm hypothesizing is the invoked reason (so they can slap "Blockchain" to their idea and attract VCs).
Of course it's blindly simple to make a robust and mostly offline system for a music festival. (With a fall back to "customer service" queue).
And the most likely point of failure in practice is the actual physical processing of guests at the gate (bags checks, pat downs, depending on the local culture).
The personnel at the gate will start complaining not being able to process guests fast enough / The guests will start protesting that they wait way too much, long before any half decent ticketing system is overwhelmed.
There have been airlines that shut down all flights because their ticketing systems had issues. {...} For most cases, I don't see any real benefit from this product that can't already be done via existing and simpler methods at the same or greater speed and cost...
Yup indeed, we're talking about concert tickets here and as you point out they are much more simple to implement in a robust.
Not a system where even the Internal Affairs Dept. of the Democratic Republic of Bannanistan should be able to append suspected terrorist to "no-fly" lists and send requests to your Airline Company to deny boarding to that suspect in almost real-time.
More a system where in worst case you can dump the whole list of currently valid S/N on the checking devices themselves
(but most often, as I've usually seen, have a local (optionally off-line) server with a local cache of the DB talking to the checking devices offline).
Send the few problematic cases to the special "customer service" queue.