> If local, they have to back them up [...] it IS safer for those people to have their data in the cloud.
Only true if Joe Sixpack is willing to pay for his cloud services. All your Picasa pictures, Youtube movies and Gmail messages are explicitly not insured. They'll do their best, of course, but you're free to point me where in the terms of service they define their guaranteed backup retention policies for the user.
> when Joe Sixpack's tablet dies and he buys a new one, with cloud services all his data is still there same as ever.
Yes, assuming he buys a compatible tablet from the same vendor. I'd like to see you use your iCloud data on an Android tabled. Same caveat: as long as you don't pay you have no rights.
> it is easier and more functional
Yes, as long as you have a connection and aren't running into some volume or bandwidth cap. I don't see many users wanting to upload their 15-megapixel raw images to Picasa.
You mean, like, I dunno... a concurrent versioning server? A shared development server?
This whole cloud thing is nought but marketingspeak from companies who see money in large-scale, thin-provisioned hosting. As usual, the inept CTOs are gobbling it up like crazy.
Even, maybe especially, if the coating is purely cosmetic, there is bound to be a market of people who want to change their mind all the time.
If the nanocoating has a high enough refresh time, though, imagine a world where any surface can be used as a screen. The possibilities are endless. Unfortunately the marketeers will think exactly the same thing.
Which is why I said "close to a godwin" - and yes, I'm well aware that it was the Americans imprisoning countless innocent asians based on nothing but the color of their skin.
Someone bought a domain and decided to not continue the services the previous owner offered. People start talking about how it's a shame such an old and symbolic domain now vanishes. Someone says it isn't a big deal to people who've never heard of it, and someone else compares that to WW2 atrocities - let me call them 'questionable american policies' if you prefer.
On the one hand, I kindof agree with the cold engineering take on it. On the other hand, I'm well aware that I'll suddenly like it a whole damn lot less when it turns out to be someone I care about. Being able to project 'who I care about' to 'who someone else cares about' is of course where the sociopath has trouble.
If your "deeper" code chokes on your data, it hasn't been coded correctly, and neither has your data insert mechanism. You never, ever, ever trust input. Ever. You validate and clean input as it comes in, before it goes into the database. If you're going to do things to data you get out of the database that could be dangerous - say, eval() it, you check it again when you fetch it.
Yes, that makes proper programming look like a lot of error handling. That's because IT IS, because that's the only way to prevent that kind of shit from happening. Live with it.
Also, XSS attacks through database-stored content, while also preventable by validating data input, does not fall under the header of SQL injection, and thus aren't expected to be stopped by bind variables.
You can't be 100% secure, but you can at least do your god damn best. Being open to SQL injections is not doing your god damn best, it's saying "fuck this security thing, money belongs in my pockets and fuck the customers up the arse".
As an aside, I also had a gawker account. The inconvenience for me was limited to being forced to change my password on their site. It's not as if the password I use on junk sites like gawker is the same I'm using for my email or banking.
True enough, but I also fear that such reasoning leads to complacence, which is also not good. Maybe we need the occasional lunatic on both sides to keep things working.
If you need it for the job, the company will provide it. If you don't need it for the job, pay for your own damn bandwidth and keep your crap off the company network.
Slashdot Mirror
> If local, they have to back them up [...] it IS safer for those people to have their data in the cloud.
Only true if Joe Sixpack is willing to pay for his cloud services. All your Picasa pictures, Youtube movies and Gmail messages are explicitly not insured. They'll do their best, of course, but you're free to point me where in the terms of service they define their guaranteed backup retention policies for the user.
> when Joe Sixpack's tablet dies and he buys a new one, with cloud services all his data is still there same as ever.
Yes, assuming he buys a compatible tablet from the same vendor. I'd like to see you use your iCloud data on an Android tabled. Same caveat: as long as you don't pay you have no rights.
> it is easier and more functional
Yes, as long as you have a connection and aren't running into some volume or bandwidth cap. I don't see many users wanting to upload their 15-megapixel raw images to Picasa.
You mean, like, I dunno... a concurrent versioning server? A shared development server?
This whole cloud thing is nought but marketingspeak from companies who see money in large-scale, thin-provisioned hosting. As usual, the inept CTOs are gobbling it up like crazy.
Uhh... on average? probably not ten minutes.
It *is* in a carrier on my belt, though, so while I'm probably safe from brain cancer I'm gonna be needing a new, non-glowing hip at some point.
Even, maybe especially, if the coating is purely cosmetic, there is bound to be a market of people who want to change their mind all the time.
If the nanocoating has a high enough refresh time, though, imagine a world where any surface can be used as a screen. The possibilities are endless. Unfortunately the marketeers will think exactly the same thing.
You should try innocent US baby sushi before you judge them.
Which is why I said "close to a godwin" - and yes, I'm well aware that it was the Americans imprisoning countless innocent asians based on nothing but the color of their skin.
Civil rights? Freedom of speech?
Someone bought a domain and decided to not continue the services the previous owner offered. People start talking about how it's a shame such an old and symbolic domain now vanishes. Someone says it isn't a big deal to people who've never heard of it, and someone else compares that to WW2 atrocities - let me call them 'questionable american policies' if you prefer.
Where did the civil rights issue come in?
Hmm, that's very close to a godwin, that is. Comparing WW2 atrocities with the shutting down of an internet domain, old though it may be? Really?
You put a webcam in front of the non-networked monitoring display.
"not connected to a network" versus "not connected to the Internet".
Just wait for the next tsunami/earthquake combo.
Serverfarmville.
Fifty-something, iirc.
> Microsoft patents aren't valid anywhere else (95% of the globe)
Agreed.
> just the phones sold in the USA
I dunno, where does it say that? It would be a very Microsoft thing to do, to negotiate a US based tax on all phones sold worldwide.
Right now that would probably entail buying Microsoft. What could possibly go wrong?
Why was it unconstitutional? From what I understand, warrantless searches are unconstitutional; and that's exactly what these patdowns are.
open (media world), not (open media) world.
On the one hand, I kindof agree with the cold engineering take on it. On the other hand, I'm well aware that I'll suddenly like it a whole damn lot less when it turns out to be someone I care about. Being able to project 'who I care about' to 'who someone else cares about' is of course where the sociopath has trouble.
No, I was going to point out that throwing more hardware at badly written software is *exactly* what happens in large swathes of the real world.
If your "deeper" code chokes on your data, it hasn't been coded correctly, and neither has your data insert mechanism. You never, ever, ever trust input. Ever. You validate and clean input as it comes in, before it goes into the database. If you're going to do things to data you get out of the database that could be dangerous - say, eval() it, you check it again when you fetch it.
Yes, that makes proper programming look like a lot of error handling. That's because IT IS, because that's the only way to prevent that kind of shit from happening. Live with it.
Also, XSS attacks through database-stored content, while also preventable by validating data input, does not fall under the header of SQL injection, and thus aren't expected to be stopped by bind variables.
> it caused a great inconvenience for me.
Oh, you poor widdle thing.
You can't be 100% secure, but you can at least do your god damn best. Being open to SQL injections is not doing your god damn best, it's saying "fuck this security thing, money belongs in my pockets and fuck the customers up the arse".
As an aside, I also had a gawker account. The inconvenience for me was limited to being forced to change my password on their site. It's not as if the password I use on junk sites like gawker is the same I'm using for my email or banking.
True enough, but I also fear that such reasoning leads to complacence, which is also not good. Maybe we need the occasional lunatic on both sides to keep things working.
Taking Darwin on the road, in this day and age? Doesn't he rattle incessantly?
Good stuff, though, this can only be applauded.
I've had modpoints continuously all week, and today of all days I have none :-(
Rapture probably took 'em to heaven.
Bullshit from some "visionary".
If you need it for the job, the company will provide it. If you don't need it for the job, pay for your own damn bandwidth and keep your crap off the company network.