I wouldn't be surprised if the "driver" was considered a "minor", and the person in the driver's seat was considered to be in an overseeing position with overall responsibility for ensuring that an accident did not occur. Obviously, that would require that the "adult" have the ability to take over safely and at least get the car pulled over to the shoulder or to evade a problem. More to the point, the "adult" would have to be paying attention to some degree.
I doubt that anyone is going to allow the driver to be completely off the hook for this, although they could simply set it up so that the owner was responsible if they were not keeping their car patched.
You are assuming there is a driver seat. The rules are for self-driving cars, and will need to consider vehicles with no adult humans on board whatsoever. How these rules define the liability issues will define the industry, and whether the US has autonomous or semi-autonomous vehicles.
I imagine if Google gets liability for their cars, allowing autonomous vehicles, you won't have a choice about keeping your car patched and screwing with the process the equivalent or cutting another drivers break cables.
Its a very common acronym for Bring Your Own Drinks around here, where you bring your own booze and a restaurant charges a corkage fee. I imagine it does adversely affect security.
The implication is that we should dial back fishing in order to let the stocks replenish.
Which means, hypothetically, you need to take all the fishing boat owners in, say, Boston Harbor and say "30% of you have to stop fishing".
Thats one way of fixing the problem. The other is fishing smarter and more sustainably. Dumping the massive factory ships in favour boats that can use more sustainable processes (eg. throwing back egg bearing females alive) will actually increase employment (but make the industry less profitable and the product more expensive in the short term).
If the users are Microsoft customers, and if Microsoft has deliberately set things up to obstruct these legal requests, Microsoft will be in the poo.
If the users are Deutsche Telekom customers, with DT operating Microsoft's software, then Microsoft are in the clear. Until they are compelled to install a back door for the NSA in their software, at which point users will be worse off since it will no longer even need a rubber stamped warrant to access the data.
Combine that with other studies which demonstrate that increased compensation lowers productivity, where the sweet spot seems to be 'enough so that pay ceases to be an issue'. This has been known for ages and reproduced in repeated studies and tests, but strangely always ignored in the corporate world where the people in power usually got there because of greed.
Go has eschewed error handling at the end of a scope using exceptions in favor of placing the error handling after nearly every statement. Do you accept the criticism that having all of the the error handling interleaved with the main program flow can negatively affect readability and comprehension? If the problem exists, are there techniques developers should be using to avoid it? Are there plans to replace the 'if err != nil {... }' boiler plate after each statement with syntactic sugar?
We employ remote workers around the globe, and pay competitive local rates to get the skills we need. We don't need labor, we need people with skills and a clue. For our positions, you are not competing with somebody in Timbuktu. If you and Fred from Timbuktu are both capable enough, we will likely make you both offers because you are that rare. And while Fred from Timbuktu is fine, Tim from Delhi is at a disadvantage because Tim doesn't have as good time zone overlap with our existing teams.
As nice as communism sounds, there's an inherent problem with rentals.
Anyone who's been a landlord knows that people don't take care stuff they don't own. Rental cars are abused, apartments are damaged and left uncleaned, taxis are smelly, public toilets are filthy and broken down.
I can't think of any rental system off the top that consistently presents clean and well-maintained equipment without enormous amounts of time and effort.
And anyone who's been a landlord knows that you have enough margin to cover these costs (unless 'slum lord' is your business model).
There is no reason this shouldn't work. Just think of it as a rental company that leases their equipment from 3rd parties. This business model has been in place for decades in high value items (private planes, probably shipping and trucking) and no reason it can't translate construction. And to make it more profitable (and follow the existing business models further), the next obvious step is to share machinery with operators. A construction company can become an engineer and a handful of full time workers, bringing in owner operators when heavy machinery is needed. People do all this right now. Technology makes it easier to manage. The increase in efficiency becomes profit for the middleman.
This is happening right now in Thailand. The transmission infrastructure is bad to rural Thailand, and over the last decade regional solar sites have been popping up all over. Cheap power during the day when you need it, expensive and inefficient power from the grid at night when all the air conditioning is off and people are sleeping.
It would be pointless. The company gets no benefit from replying to you, only liability. The same reasons companies don't give out genuine references, or even have a policy that they don't give them out at all beyond confirming that you did work there and for how long for.
There might be three standards, but if the article is to be believed they aren't exactly competing.
One (Qi) is supported by several major handset manufactorers. Another is in bed with Starbucks (USA?). The third doesn't even get a mention beyond that it exists. Given that Starbuck's products don't need wireless charging it would seem any war has already been won by Qi.
My bank now offers a storage space that is supposed to automatically receive bills and similar crap (for now.pdf bank statements land there, which is pretty cool if I somehow need to find that old stuff) ; files can be stored as well, uploaded to the web interface, no other means available. That seems to be a good place to store keys. Else I'd be thinking of paper notes in a bank safe (and/or the kind of attorney that does things on your behalf when you're dead or incapacitated, in growing order of cost)
If the keys are encrypted, maybe. The bank is using this to store bills and bank statements. This storage doesn't need to be secure, it just needs to be more secure than your letter box. The bank doesn't need to keep the storage private from its employees, as its employees already have access to your bank statements and bills. About the worst thing you could upload there is your internet or phone banking password in cleartext, as it would be visible to exactly the people who know how to best exploit it.
The flaw in your design is that when the PC dies, you can no longer decrypt the backup because you just lost the private key.
I see it as a requirement rather than a flaw. If my data can be decripted after I have lost my key, then other people had copies of my key. It is a well known and documented fact that we can't trust everyone with access to the other copies of my key.
You never see my requirements or feature requests or responses on user serveys, or those from people who ask me for help, because your product doesn't meet my needs and gets discounted in the first round (along with almost all of your competitors).
Some online backup companies in the past have solved this by having you store your private key in yet a 3rd party "escrow" location, so you don't have the only copy and yet the company with your backup data does not have the private key either. In essence that is what Backblaze does, just in an "easy to use" way. We store the private encryption keys on one particular server, completely separate from your data. The data is all on "pods". Is it as secure? I don't think anybody can claim 100 % security, we do the very very best job we can.
Yes, the escrow solution has exactly the sames flaw as Backblaze's model. Security is fundamentally flawed as soon as users lose control of their key. All that effort ensuring keys are never writen to disk provides some protection against hackers, but can be completely bypassed by authority. The list of people and organizations that can gain or already have such authority is always surprisingly large. You are doing the very very best job you can for the model you have chosen to implement.
Fixing key loss problems requires guiding or ensuring that the user to keeps copies of their key. Maybe you can even offer to keep a copy for nieve users, or make some pocket money selling keyfobs, but if you start from the position of compromiable keys you can't support people with a healthy dose of paranoia. And that is becoming more and more of us. We are stuck with encrypting *before* we use your service, which makes your service less usable and less attractive.
I always find it sad when people advocate blacklists to protect their sensitive data. 'Encrypt your most sensitive data first'. It doesn't work, as it assumes you know what your most sensitive data actually is and don't make mistakes. You need to protect *all* your data by default, and open up data you determine to be not sensitive when necessary ('Share this photo with friends', 'Sync with Contacts').
"Search and stream torrents. Towards anonymous streaming."
Because of the focus on streaming? Streaming simply doesn't work across of this planet and for less popular content, unless you are YouTube and have invested in a global network of proxies. When I read streaming, I translate it to broken. I look at the front page, see what seems to be a tightly integrated app designed for first world consumers of popular content, and move on.
But since you prompted me to look deeper, yeah, it looks very interesting. It might even be useful for getting that obscure movie from the one seeder in Brazil into my media player in my backwater on the other side of the planet.
I don't understand why publishers are so interested in preorders.
Publishers in all industries like preorders because it creates a spike of sales on release day. This is required to get on best seller lists, because they are usually about total sales over the last week or month.
The people who will be running the show in 20 years from now are not on Facebook. For a while now, the people running the show have been groomed for power. If you are a senator wanting to continue your dynasty, you send junior to private and exclusive schools and now days certainly don't let them near the Internet using their real name or real face. That embarrassing photo of your son would not only throw away everything you have invested, but also torpedo your own position of privilege. Not all trust fund kids are Paris Hilton.
Well done. I've not heard Python descripted as 'scriping language du jour' for a decade. I tend to date the time when Python started getting taken seriously at version 1.5.2, April 1999.
Of course, if real code is written in C/C++, then no true scotsman would ever consider scripting languages the right tool for the job:)
There are many services that tackle parts of Skype's functionality, but I have yet to see one that tackles them all. Not only does Skype to chat and client-to-client video conferencing, but it also gives you access to a global POTS gateway both outgoing and inbound, and is available to customers outside of the USA. Viber, Line, WeChat, Google and tox don't have the functionality to take away Skype's business. So we remain stuck with Skype, despite their ever worsening service and dubious allegence.
I thought this was a Slashdot story from years ago when China was supposed to ditch Windows...so here we are again and China still has no viable homegrown distro. I thought years ago they phased out Windows and used GNU/Linux. Not so. I know a Chinese insider who tells me that the Government handed out bales of cash to develop a GNU/Linux distro of their own and all Red Flag Linux is, is Fedora with a some Catonese/Mandarin. It was a scam of public funds. They really did not develop their own GNU/Linux distro properly. was interested because, in a racist way, I thought--wow, Asians doing GNU/Linux, it must be AWESOME and kick the other distro's ass. Asians are hard working and fastidious and the distro will intall without a hitch and it will be great. Not really. One of the issues with investing in China when it comes to business are corrupt officials and lack of accountability. In China, you pay off the right people, you do what you want--until you get caught and are made an example of for the press. Linus Torvalds mentioned something about how GNU/Linux could not really come out of places like India and China as the peole are far too concerned about trying to survive, and Linux is something that came about 'just for fun'.
Ubuntu Kylin is pretty viable. Ubuntu 14.04 specially localized for China, produced by Canonical in partnership with one of the (many) ministries. By bringing in the experts, you avoid all the problems you cite, and it is open source so a Chinese group can take the drivers seat and salvage any lost pride whenever it is viable.
China is huge and the government is huge. IIRC they have had several customized linux variants in development simultaneously (of which we generally know of Red Flag because it had the coolest name).
The other gaping hole is that Amazon are going to screw their product suppliers so much that there won't be any supply.
"At which point the screws can be tightened indefinitely. And after a while, there will be no more Charlie Stross novels because I will be unable to earn a living and will have to go find a paying job."
Yeah, it would be a fantastic business model for Amazon to kill off the supply of quality books.
If this is because they're upset at Microsoft for dropping XP support so quickly, then what are they going to? What OS has a longer support cycle than XP's 12.5 years?
Red Hat's is 10 years. AIX is 5-7. HP-UX is 8. Ubuntu LTS is 5 years. Mac OS is 4-ish. Solaris is likely the closest at 12 years... But its still less. Maybe they'll roll their own support?
Every Open Source opearting system has support for as long as you want to keep making fixes for it. It isn't like China lacks people capable managing this process and patching the code. And if they somehow can't, it isn't like Canonical or Red Hat or a hundred other companies wouldn't do it for them for peanuts compared to Microsoft licences.
Right, few people care about the init scheme. systemd would have had much less of a battle for acceptance if it was just an init scheme. The major objections seemed to be about all the other stuff it takes over and plans to take over.
Slashdot Mirror
I wouldn't be surprised if the "driver" was considered a "minor", and the person in the driver's seat was considered to be in an overseeing position with overall responsibility for ensuring that an accident did not occur. Obviously, that would require that the "adult" have the ability to take over safely and at least get the car pulled over to the shoulder or to evade a problem. More to the point, the "adult" would have to be paying attention to some degree.
I doubt that anyone is going to allow the driver to be completely off the hook for this, although they could simply set it up so that the owner was responsible if they were not keeping their car patched.
You are assuming there is a driver seat. The rules are for self-driving cars, and will need to consider vehicles with no adult humans on board whatsoever. How these rules define the liability issues will define the industry, and whether the US has autonomous or semi-autonomous vehicles.
I imagine if Google gets liability for their cars, allowing autonomous vehicles, you won't have a choice about keeping your car patched and screwing with the process the equivalent or cutting another drivers break cables.
Its a very common acronym for Bring Your Own Drinks around here, where you bring your own booze and a restaurant charges a corkage fee. I imagine it does adversely affect security.
We know how to fix this problem.
The implication is that we should dial back fishing in order to let the stocks replenish.
Which means, hypothetically, you need to take all the fishing boat owners in, say, Boston Harbor and say "30% of you have to stop fishing".
Thats one way of fixing the problem. The other is fishing smarter and more sustainably. Dumping the massive factory ships in favour boats that can use more sustainable processes (eg. throwing back egg bearing females alive) will actually increase employment (but make the industry less profitable and the product more expensive in the short term).
If the users are Microsoft customers, and if Microsoft has deliberately set things up to obstruct these legal requests, Microsoft will be in the poo.
If the users are Deutsche Telekom customers, with DT operating Microsoft's software, then Microsoft are in the clear. Until they are compelled to install a back door for the NSA in their software, at which point users will be worse off since it will no longer even need a rubber stamped warrant to access the data.
Combine that with other studies which demonstrate that increased compensation lowers productivity, where the sweet spot seems to be 'enough so that pay ceases to be an issue'. This has been known for ages and reproduced in repeated studies and tests, but strangely always ignored in the corporate world where the people in power usually got there because of greed.
Talk on this - https://www.youtube.com/watch?...
Go has eschewed error handling at the end of a scope using exceptions in favor of placing the error handling after nearly every statement. Do you accept the criticism that having all of the the error handling interleaved with the main program flow can negatively affect readability and comprehension? If the problem exists, are there techniques developers should be using to avoid it? Are there plans to replace the 'if err != nil { ... }' boiler plate after each statement with syntactic sugar?
We employ remote workers around the globe, and pay competitive local rates to get the skills we need. We don't need labor, we need people with skills and a clue. For our positions, you are not competing with somebody in Timbuktu. If you and Fred from Timbuktu are both capable enough, we will likely make you both offers because you are that rare. And while Fred from Timbuktu is fine, Tim from Delhi is at a disadvantage because Tim doesn't have as good time zone overlap with our existing teams.
As nice as communism sounds, there's an inherent problem with rentals.
Anyone who's been a landlord knows that people don't take care stuff they don't own. Rental cars are abused, apartments are damaged and left uncleaned, taxis are smelly, public toilets are filthy and broken down.
I can't think of any rental system off the top that consistently presents clean and well-maintained equipment without enormous amounts of time and effort.
And anyone who's been a landlord knows that you have enough margin to cover these costs (unless 'slum lord' is your business model).
There is no reason this shouldn't work. Just think of it as a rental company that leases their equipment from 3rd parties. This business model has been in place for decades in high value items (private planes, probably shipping and trucking) and no reason it can't translate construction. And to make it more profitable (and follow the existing business models further), the next obvious step is to share machinery with operators. A construction company can become an engineer and a handful of full time workers, bringing in owner operators when heavy machinery is needed. People do all this right now. Technology makes it easier to manage. The increase in efficiency becomes profit for the middleman.
This is happening right now in Thailand. The transmission infrastructure is bad to rural Thailand, and over the last decade regional solar sites have been popping up all over. Cheap power during the day when you need it, expensive and inefficient power from the grid at night when all the air conditioning is off and people are sleeping.
It would be pointless. The company gets no benefit from replying to you, only liability. The same reasons companies don't give out genuine references, or even have a policy that they don't give them out at all beyond confirming that you did work there and for how long for.
There might be three standards, but if the article is to be believed they aren't exactly competing.
One (Qi) is supported by several major handset manufactorers. Another is in bed with Starbucks (USA?). The third doesn't even get a mention beyond that it exists. Given that Starbuck's products don't need wireless charging it would seem any war has already been won by Qi.
We are way ahead of you: http://www.bbc.com/news/techno...
My bank now offers a storage space that is supposed to automatically receive bills and similar crap (for now .pdf bank statements land there, which is pretty cool if I somehow need to find that old stuff) ; files can be stored as well, uploaded to the web interface, no other means available.
That seems to be a good place to store keys. Else I'd be thinking of paper notes in a bank safe (and/or the kind of attorney that does things on your behalf when you're dead or incapacitated, in growing order of cost)
If the keys are encrypted, maybe. The bank is using this to store bills and bank statements. This storage doesn't need to be secure, it just needs to be more secure than your letter box. The bank doesn't need to keep the storage private from its employees, as its employees already have access to your bank statements and bills. About the worst thing you could upload there is your internet or phone banking password in cleartext, as it would be visible to exactly the people who know how to best exploit it.
The flaw in your design is that when the PC dies, you can no longer decrypt the backup because you just lost the private key.
I see it as a requirement rather than a flaw. If my data can be decripted after I have lost my key, then other people had copies of my key. It is a well known and documented fact that we can't trust everyone with access to the other copies of my key.
You never see my requirements or feature requests or responses on user serveys, or those from people who ask me for help, because your product doesn't meet my needs and gets discounted in the first round (along with almost all of your competitors).
Some online backup companies in the past have solved this by having you store your private key in yet a 3rd party "escrow" location, so you don't have the only copy and yet the company with your backup data does not have the private key either. In essence that is what Backblaze does, just in an "easy to use" way. We store the private encryption keys on one particular server, completely separate from your data. The data is all on "pods". Is it as secure? I don't think anybody can claim 100 % security, we do the very very best job we can.
Yes, the escrow solution has exactly the sames flaw as Backblaze's model. Security is fundamentally flawed as soon as users lose control of their key. All that effort ensuring keys are never writen to disk provides some protection against hackers, but can be completely bypassed by authority. The list of people and organizations that can gain or already have such authority is always surprisingly large. You are doing the very very best job you can for the model you have chosen to implement.
Fixing key loss problems requires guiding or ensuring that the user to keeps copies of their key. Maybe you can even offer to keep a copy for nieve users, or make some pocket money selling keyfobs, but if you start from the position of compromiable keys you can't support people with a healthy dose of paranoia. And that is becoming more and more of us. We are stuck with encrypting *before* we use your service, which makes your service less usable and less attractive.
I always find it sad when people advocate blacklists to protect their sensitive data. 'Encrypt your most sensitive data first'. It doesn't work, as it assumes you know what your most sensitive data actually is and don't make mistakes. You need to protect *all* your data by default, and open up data you determine to be not sensitive when necessary ('Share this photo with friends', 'Sync with Contacts').
"Search and stream torrents. Towards anonymous streaming."
Because of the focus on streaming? Streaming simply doesn't work across of this planet and for less popular content, unless you are YouTube and have invested in a global network of proxies. When I read streaming, I translate it to broken. I look at the front page, see what seems to be a tightly integrated app designed for first world consumers of popular content, and move on.
But since you prompted me to look deeper, yeah, it looks very interesting. It might even be useful for getting that obscure movie from the one seeder in Brazil into my media player in my backwater on the other side of the planet.
I don't understand why publishers are so interested in preorders.
Publishers in all industries like preorders because it creates a spike of sales on release day. This is required to get on best seller lists, because they are usually about total sales over the last week or month.
The people who will be running the show in 20 years from now are not on Facebook. For a while now, the people running the show have been groomed for power. If you are a senator wanting to continue your dynasty, you send junior to private and exclusive schools and now days certainly don't let them near the Internet using their real name or real face. That embarrassing photo of your son would not only throw away everything you have invested, but also torpedo your own position of privilege. Not all trust fund kids are Paris Hilton.
Well done. I've not heard Python descripted as 'scriping language du jour' for a decade. I tend to date the time when Python started getting taken seriously at version 1.5.2, April 1999.
Of course, if real code is written in C/C++, then no true scotsman would ever consider scripting languages the right tool for the job :)
There are many services that tackle parts of Skype's functionality, but I have yet to see one that tackles them all. Not only does Skype to chat and client-to-client video conferencing, but it also gives you access to a global POTS gateway both outgoing and inbound, and is available to customers outside of the USA. Viber, Line, WeChat, Google and tox don't have the functionality to take away Skype's business. So we remain stuck with Skype, despite their ever worsening service and dubious allegence.
I thought this was a Slashdot story from years ago when China was supposed to ditch Windows...so here we are again and China still has no viable homegrown distro. I thought years ago they phased out Windows and used GNU/Linux. Not so. I know a Chinese insider who tells me that the Government handed out bales of cash to develop a GNU/Linux distro of their own and all Red Flag Linux is, is Fedora with a some Catonese/Mandarin. It was a scam of public funds. They really did not develop their own GNU/Linux distro properly. was interested because, in a racist way, I thought--wow, Asians doing GNU/Linux, it must be AWESOME and kick the other distro's ass. Asians are hard working and fastidious and the distro will intall without a hitch and it will be great. Not really. One of the issues with investing in China when it comes to business are corrupt officials and lack of accountability. In China, you pay off the right people, you do what you want--until you get caught and are made an example of for the press. Linus Torvalds mentioned something about how GNU/Linux could not really come out of places like India and China as the peole are far too concerned about trying to survive, and Linux is something that came about 'just for fun'.
Ubuntu Kylin is pretty viable. Ubuntu 14.04 specially localized for China, produced by Canonical in partnership with one of the (many) ministries. By bringing in the experts, you avoid all the problems you cite, and it is open source so a Chinese group can take the drivers seat and salvage any lost pride whenever it is viable.
China is huge and the government is huge. IIRC they have had several customized linux variants in development simultaneously (of which we generally know of Red Flag because it had the coolest name).
The other gaping hole is that Amazon are going to screw their product suppliers so much that there won't be any supply.
"At which point the screws can be tightened indefinitely. And after a while, there will be no more Charlie Stross novels because I will be unable to earn a living and will have to go find a paying job."
Yeah, it would be a fantastic business model for Amazon to kill off the supply of quality books.
If this is because they're upset at Microsoft for dropping XP support so quickly, then what are they going to? What OS has a longer support cycle than XP's 12.5 years?
Red Hat's is 10 years. AIX is 5-7. HP-UX is 8. Ubuntu LTS is 5 years. Mac OS is 4-ish. Solaris is likely the closest at 12 years... But its still less. Maybe they'll roll their own support?
Every Open Source opearting system has support for as long as you want to keep making fixes for it. It isn't like China lacks people capable managing this process and patching the code. And if they somehow can't, it isn't like Canonical or Red Hat or a hundred other companies wouldn't do it for them for peanuts compared to Microsoft licences.
My landlord owns the fixtures. I own the lightbulbs.
Line took over nearly completely from WhatsApp in my region.
Right, few people care about the init scheme. systemd would have had much less of a battle for acceptance if it was just an init scheme. The major objections seemed to be about all the other stuff it takes over and plans to take over.