I lost it at "[...] when an All State Insurance franchise did a live demonstration of Interguard’s software to other dealers. The technology started scanning the network and almost immediately found an email with the words “client list” and “résumé”. The demonstrator opened the email in front of a room full of peers to discover his best employee was plotting to move to another company."
Households in IT in Bangalore were shared with around 4 or more afaik when I was living there in 2009. Monthly salaries were around ~300 USD which was not enough for most to comfortably live in their own apartment.
I do not think that we are to take from the article that these home owners left their cars inside their garages until the NSA changed their frequencies. I understood that for a while they were interrupted in what they were planning to do.
I want to send mails from embedded devices, similar to e.g. an ESP8266, with intermittent connectivity and a semi-stable power source. An HTTP API seems simpler for me to interface with than SMTP.
Do you think though that this is Apple actively trying to reduce your ability to repair, or is it that they pursue other goals and the ability to repair is waaay down on the list?
I would assume, from experience in large corporations, that it is the latter.
Two weeks notice during probation period.
-
What's more relevant:
If they actually signed a legal contract they also need to provide him with a written and signed contract termination. As far as I understand a signed contract exists and no written notice has been delivered. The notice period is counted starting from the day of the delivery of that physical mail.
How do you think it is dangerous? ACs do not emit any gases themselves, so except for the CO2 produced by the engine to keep it running it should not be dangerous.
Providing a quiet, disruption-free and hygienic environment for employees to sleep in seems like quite the commitment to make. I'm all for it, and can just the same understand why it would not happen in most environments.
Versioning backups seems like a must. Encrypting malware is a thing and has been for a while, just like rm -rf type mistakes which are subsequently propagated automatically to "backups".
I think this is a good basic and relatively low-tech strategy.
Do you do versioning? As in what happens if your files are silently corrupted e.g. by accident or by malware? Rsync would overwrite your files, and you might even overwrite your off-site backup when you connect it.
My main reason for going beyond such a set-up though is that it takes time, effort and remembering to sync the off-site backup by taking it home, syncing and putting it back. And during that time all your data is in the same place. If something happens to your home during that time (break-in, flooding, fire...) you're out of luck. Unless your rsync'd drives are also encrypted and you just switch one of them with the off-site one for rotation.
Do you need co-location though?
I dropped an HP Microserver at a friend's place, which backs up snapshots of my main backup server at home daily. Seems to work well so far, at quite limited costs. Since my main backup server also backs up his NAS we both win. Since all backups are encrypted there is also little privacy risk from theft (or snooping on one another).