Yes, for now, real travel requires a "real" car. However, most car trips are short commute and shopping mall trips with 1 person in the car. Where electric would be more efficient than gas.
Electric will come when it's the most attractive alternative financially, i.e. when gas prices go high enough.
"sending them abroad to learn the latest hacking techniques, while lavishing privileges on their families at home to keep them loyal", where the privileges probably mean the precious privilege of being alive.
From TFA: A solution might be to break the data up into fixed sized frames but this would make it more difficult to reconstruct the data if there was packet loss.
And even then, the data rate would leak some information about the content.
The only trivial solution for zero leakage is to either use constant rate encoding, or use some kind of padding to make the data rate constant. Non-trivial solutions would include some random data rate variations to obfuscate the data rate of actual payload content. Unfortunately, all these methods will waste bandwidth.
Actually, a lot of previously free Spotify users I know are now either paying for it, or considering paying for it. The big reason: Spotify mobile (which never was free).
10€/month is close enough to free for a lot of people.
(also most people I know wouldn't know what a 'torrent' is)
Off-topic: my bank asks for the Lth, Mth and Nth characters of my password, which is better than asking for the whole lot. Is it possible to have a system like that without storing the password encrypted (rather than hashed)?
If someone can get in a bank's server to read those passwords, there are probably worse things he could do than just take the passwords...
A fully autonomously driving vehicle would be a nice target for all kinds of nasty hacking. Combine that internet connectivity and a nasty worm, and we'll see an amateur re-shoot of Maximum Overdrive on Youtube shortly.
Yes, this is a perfectly good reason to keep dumping all that CO2 in the atmosphere. After all, we cannot be 100% sure that it will have the adverse effect that all those doomsday prophets keep predicting.
Btw. I just found out that all this talk about peak oil is complete nonsense. There's no way that oil will ever run out.
You only need one cookie for all features if your site is competently designed: the one for tracking the user's session. Everything else should be stored on the server side anyway because you should never trust the client
There are perfectly valid reasons (not involving cross-site tracking) to use more than one cookie. If a session identifying cookie is used to identify an user account and grant privileges, it's usually a good idea to make that cookie disappear when the user closes his browser (i.e. a 'session' cookie). However, the user may have additional preferences on the site which are not personally identifiable, but for which it makes sense to store and use the setting even when the user is not logged in, for example, language selection on multilingual sites. Trusting the client is also a non-issue for things that are mapped to a single item from a set of possible choices (as long as the code implementing the parsing is reasonably sane).
(And for the Accept-Language header, try explaining to a client how they can change it. Or how to install a browser where they actually can change it.)
And while we're on the subject, it takes only fractionally longer for most users to make a POST request than to just do an HTTP GET, so unless your site is stupid and slow or your users are then you don't need ANY cookies. A quality CMS will degrade. If yours doesn't then it isn't.
Clicking on a link in a browser will cause a HTTP GET. Maintaining a session with URL parameters makes the URLs much less user friendly, and opens up a possibility for trivial social engineering exploits (e.g. lol paste your url here I'll have a look!).
The problem with the whole credit card system for online payments is that you will need to give your secrets out to anyone who you want to pay, and trust that they handle those secrets properly. It just doesn't work.
All of this and the Fins are bitch wanting wtf, 100 Euros per customer? I would have to look at these fucking Fins and say; "Look douchebags, if you are going to force me to give up the protections on this system and open it up to whatever, then we are going to sue the fucking shit out of you when the entire game platform goes into the toilet because nobody plays the fucker due to all the cheaters on it. So, please, is your country worth that much even? Do I get to kick you all out if I win the lawsuit if you can't pay it? Granted, you people are fucking RETARDS, and obviously don't understand WTF a gaming system is and keeping one up, running and secure from ratfuck cheaters and whatnot. But I am willing to overlook that, providing you pull your collective heads out of your asses.
To make a car analogy, Sony pulling the Other OS feature is similar to someone having bought a car with an AC unit, and getting their car back from the yearly servicing finds out that AC has been disabled because it interferes with the airbag system.
In both cases, it's about safety and security, but it's the fault of the manufacturer in the first place. The car manufacturer could argue that 'most people are not using the AC anyway, and it's still a perfectly good car', but they would still have to either compensate their customers or fix those cars.
This is not about evil hackers at all, this is about a corporation selling something, then changing the deal afterwards.
Where this is a problem is if you're a small shop with a single DB server, and the zone holding your DB server goes down-- in that case you're kind of SOL.
Even using traditional methods (i.e. non-cloud), a small shop would be unlikely to have enough redundancy when there's a datacenter-wide issue.
But when it's your gear, you have some control over the situation. When it's "in the cloud", you sit and get yelled at by the CXO and sweat if you'll still have a job while cloud provider X works to fix the problem.
Try to focus on fixing something yourself while being yelled at. Now how annoying is that?
Yeah we totally need the European government making decisions for us all...
The mobile phone manufacturers managed to come up with the standard all by themselves. Admittedly, it was after a slight hint from EU that if the industry won't standardize itself, a standard will be forced...
Slashdot Mirror
Smartphones aren't good for gaming for one simple reason: the controls suck.
+1 for this.
Yes, for now, real travel requires a "real" car. However, most car trips are short commute and shopping mall trips with 1 person in the car. Where electric would be more efficient than gas.
Electric will come when it's the most attractive alternative financially, i.e. when gas prices go high enough.
In the US, the constitution grants everyone the right of getting shot.
According to some, it's not a right but a privilege.
They are not put to a prison camp. If their offspring defects, that privilege is revoked.
RTFS.
"sending them abroad to learn the latest hacking techniques, while lavishing privileges on their families at home to keep them loyal", where the privileges probably mean the precious privilege of being alive.
That can't possibly be true. Back in the 70s the media was telling me that oil would be gone by the year 2000.
You're right, oil will never end! Never!
From TFA: A solution might be to break the data up into fixed sized frames but this would make it more difficult to reconstruct the data if there was packet loss.
And even then, the data rate would leak some information about the content.
The only trivial solution for zero leakage is to either use constant rate encoding, or use some kind of padding to make the data rate constant. Non-trivial solutions would include some random data rate variations to obfuscate the data rate of actual payload content. Unfortunately, all these methods will waste bandwidth.
Actually, a lot of previously free Spotify users I know are now either paying for it, or considering paying for it. The big reason: Spotify mobile (which never was free).
10€/month is close enough to free for a lot of people.
(also most people I know wouldn't know what a 'torrent' is)
Off-topic: my bank asks for the Lth, Mth and Nth characters of my password, which is better than asking for the whole lot. Is it possible to have a system like that without storing the password encrypted (rather than hashed)?
If someone can get in a bank's server to read those passwords, there are probably worse things he could do than just take the passwords...
Just choose the "I don't know this guy" option, and off he goes. Problem solved.
When dealing with people, you will have to learn how to say no.
... the software publishers will just compile their stuff for ARM. How hard can that be?
However, the article you link to is crap.
A fully autonomously driving vehicle would be a nice target for all kinds of nasty hacking. Combine that internet connectivity and a nasty worm, and we'll see an amateur re-shoot of Maximum Overdrive on Youtube shortly.
Yes, this is a perfectly good reason to keep dumping all that CO2 in the atmosphere. After all, we cannot be 100% sure that it will have the adverse effect that all those doomsday prophets keep predicting.
Btw. I just found out that all this talk about peak oil is complete nonsense. There's no way that oil will ever run out.
Breaking news: Anonymous meditation causes superconductivity.
He's more trustable than an AC.
Some of Mr. Gibson's opinions are a bit excessive (like the whole 'stealth ports' thing), but he usually gets the facts right.
I think the point is you have to make the sculpture or painting to do something, or be usable for something to make it patentable.
You only need one cookie for all features if your site is competently designed: the one for tracking the user's session. Everything else should be stored on the server side anyway because you should never trust the client
There are perfectly valid reasons (not involving cross-site tracking) to use more than one cookie. If a session identifying cookie is used to identify an user account and grant privileges, it's usually a good idea to make that cookie disappear when the user closes his browser (i.e. a 'session' cookie). However, the user may have additional preferences on the site which are not personally identifiable, but for which it makes sense to store and use the setting even when the user is not logged in, for example, language selection on multilingual sites. Trusting the client is also a non-issue for things that are mapped to a single item from a set of possible choices (as long as the code implementing the parsing is reasonably sane).
(And for the Accept-Language header, try explaining to a client how they can change it. Or how to install a browser where they actually can change it.)
And while we're on the subject, it takes only fractionally longer for most users to make a POST request than to just do an HTTP GET, so unless your site is stupid and slow or your users are then you don't need ANY cookies. A quality CMS will degrade. If yours doesn't then it isn't.
Clicking on a link in a browser will cause a HTTP GET. Maintaining a session with URL parameters makes the URLs much less user friendly, and opens up a possibility for trivial social engineering exploits (e.g. lol paste your url here I'll have a look!).
Whoa, replicators made out of those would be very cool!
The problem with the whole credit card system for online payments is that you will need to give your secrets out to anyone who you want to pay, and trust that they handle those secrets properly. It just doesn't work.
All of this and the Fins are bitch wanting wtf, 100 Euros per customer? I would have to look at these fucking Fins and say; "Look douchebags, if you are going to force me to give up the protections on this system and open it up to whatever, then we are going to sue the fucking shit out of you when the entire game platform goes into the toilet because nobody plays the fucker due to all the cheaters on it. So, please, is your country worth that much even? Do I get to kick you all out if I win the lawsuit if you can't pay it? Granted, you people are fucking RETARDS, and obviously don't understand WTF a gaming system is and keeping one up, running and secure from ratfuck cheaters and whatnot. But I am willing to overlook that, providing you pull your collective heads out of your asses.
To make a car analogy, Sony pulling the Other OS feature is similar to someone having bought a car with an AC unit, and getting their car back from the yearly servicing finds out that AC has been disabled because it interferes with the airbag system.
In both cases, it's about safety and security, but it's the fault of the manufacturer in the first place. The car manufacturer could argue that 'most people are not using the AC anyway, and it's still a perfectly good car', but they would still have to either compensate their customers or fix those cars.
This is not about evil hackers at all, this is about a corporation selling something, then changing the deal afterwards.
Where this is a problem is if you're a small shop with a single DB server, and the zone holding your DB server goes down-- in that case you're kind of SOL.
Even using traditional methods (i.e. non-cloud), a small shop would be unlikely to have enough redundancy when there's a datacenter-wide issue.
But when it's your gear, you have some control over the situation. When it's "in the cloud", you sit and get yelled at by the CXO and sweat if you'll still have a job while cloud provider X works to fix the problem.
Try to focus on fixing something yourself while being yelled at. Now how annoying is that?
Yeah we totally need the European government making decisions for us all...
The mobile phone manufacturers managed to come up with the standard all by themselves. Admittedly, it was after a slight hint from EU that if the industry won't standardize itself, a standard will be forced...
Still, even the most unfortunate people can afford beer. So why not a Spotify subscription?