... should the surface reflect significantly more than a current roadway does. There's a non-trivial amount of glare that comes from existing road materials, the question is whether this surface has *more* reflection than that...
He's missing the point. Everyone knows that the post office handles all your mail, but it's still not allowed to tell the police what you're receiving without a warrant. The existence of a record does not imply the availability of that record to law enforcement or the government.
Not knowing the likelihoods is not the same as claiming that the likelihoods are equal.
If you present me with a biased coin that you've made, I don't know whether when we toss it, it is more likely to come up heads, or more likely to come up tails. Pointing that out doesn't mean that I think they're both equally likely, just that I have no way of knowing at this stage which is more likely. Notable points:
1. There is a correct answer. 2. You know what it is. 3. I don't know what it is. 4. I don't believe that they're equally likely, but I can't tell which is more likely.
Not particularly - then the hash becomes the new password. You'd need a client side hash with a nonce, and even then, the server needs a way to be able to validate the client-generated hash without storing the password in plaintext.
But similarly, you haven't heard the average person talking about wanting native apps either.
Developers and tech bloggers haven't realised that they need to balance conflicting desires (universal availability and version uniformity vs offline access and access to local hardware/services/data) which would induce preferences either way. What you are seeing is the tech community noticing the features they are missing, building them, and throwing away the features they already have in the process, then repeating again in the other direction.
The average person has no idea about any of this, and doesn't care as long as they can still send selfies and cat emojis to their friends. If a native app allows them to do it, they will use that; if a web app does, then that's where they will go. As long as they can click an icon and send the picture, it's good enough for them.
What is the difference between "business rules that need to be validated and checked" and "sanitize your inputs"?
(Hint: "this field should not contain semicolons" is just as much a sanity check/validation as "this field contains a latitude entry and thus should be between -90 and 90".)
Average speed on uphill sections vs downhill sections? Fastest point on route? Hardest (max heartrate) section on route? Number of stops? Duration walking vs running? Distance to exhaustion, time to exhaustion? (When you can not complete the route as planned.) Average intensity (heartrate)?
What credit? They make a clone of a Palm Treo or cheap WinMob phone, and put good marketing around it.
We had touchscreen phones before the iPhone. We had full-web-enabled phones before the iPhone. We had easily-usable email on phones before the iPhone. We had the choice of on-screen keyboards and hardware keyboards (oops!) before the iPhone. We had apps on phones before the iPhone. We had app stores before iPhone. We had music players built into phones before the iPhone. We had handwriting input before the iPhone. We had bluetooth connectivity before the iPhone. We had wifi-enabled phones before the iPhone.
The one thing we didn't have readily accessible before iphones was multi-touch - and if that's the secret sauce that made smartphones come of age, then so be it.
But I (and many others) assert that it was better marketing, not a superior phone, that was the key differentiator of the iPhone.
Advertisers aren't offering to pay for my attention or my bandwidth....
...but AM I compensated for either, no...
I'm a user and defender of ad-blocking (as you will see elsewhere in this conversation), but this argument is slightly fallacious.
The advertiser is compensating you for your attention and bandwidth by purchasing content that you wish to view/read.
In an non-advertising supported model, you would be required to pay something to get access to the content, in the advertising-supported model, this cost would be paid on your behalf by the advertisers.
There is an open question on whether the amount of content you are getting in compensation is in appropriate proportion to the amount of your attention and bandwidth (and security/privacy risk) being taken up, but the idea that there is no compensation provided is not quite right.
There is no "acceptable advertising", to many of us. We're tired of space in our brain being rented out...
Your options are a pay-wall or ads.
Your logical fallacy is the "false dichotomy". There's also the begging button, hobby sites, merchandising, product placement, and any number of other means of funding sites.
"Product placement" sounds an awful lot like renting out brain space for "acceptable advertising" to me...
And your begging button and merchandise will probably also have to be featured somewhere prominent on your site to get any of your readers clicking on them, so that will probably involve taking some brain space on the screen to promote ("advertise") these features/products.
Yes, and those households, cities, and countries usually don't have entire police departments going around trying to prevent murder, larceny and rape. The low incidence rate probably means that most of the intervention is responsive, not preventative.
Slashdot Mirror
Even when that 7-digit user is the new *OWNER* of /. ???
Alternate title: "India insists on network neutrality"
And WiTricity...
... should the surface reflect significantly more than a current roadway does. There's a non-trivial amount of glare that comes from existing road materials, the question is whether this surface has *more* reflection than that...
This is, again, why I have an iPhone.
FTFY.
Nnnnnnooooooooooooooooooooooooooooooooooooo (breathe) ooooooooooooooooooo!
He's missing the point. Everyone knows that the post office handles all your mail, but it's still not allowed to tell the police what you're receiving without a warrant. The existence of a record does not imply the availability of that record to law enforcement or the government.
This is essentially a distro, of android-x86. That would be like asking what licence Fedora was under... Different parts are under different licences.
Yep. Trolling by Betteridge effect
Welcome to 2008?
Not knowing the likelihoods is not the same as claiming that the likelihoods are equal.
If you present me with a biased coin that you've made, I don't know whether when we toss it, it is more likely to come up heads, or more likely to come up tails. Pointing that out doesn't mean that I think they're both equally likely, just that I have no way of knowing at this stage which is more likely. Notable points:
1. There is a correct answer.
2. You know what it is.
3. I don't know what it is.
4. I don't believe that they're equally likely, but I can't tell which is more likely.
Not particularly - then the hash becomes the new password. You'd need a client side hash with a nonce, and even then, the server needs a way to be able to validate the client-generated hash without storing the password in plaintext.
And the Australian allocation is half of the US band: 915MHz to 928MHz as per http://www.acma.gov.au/Industr...
(The US 900MHz ISM band is 902 to 928 MHz).
But similarly, you haven't heard the average person talking about wanting native apps either.
Developers and tech bloggers haven't realised that they need to balance conflicting desires (universal availability and version uniformity vs offline access and access to local hardware/services/data) which would induce preferences either way. What you are seeing is the tech community noticing the features they are missing, building them, and throwing away the features they already have in the process, then repeating again in the other direction.
The average person has no idea about any of this, and doesn't care as long as they can still send selfies and cat emojis to their friends. If a native app allows them to do it, they will use that; if a web app does, then that's where they will go. As long as they can click an icon and send the picture, it's good enough for them.
What is the difference between "business rules that need to be validated and checked" and "sanitize your inputs"?
(Hint: "this field should not contain semicolons" is just as much a sanity check/validation as "this field contains a latitude entry and thus should be between -90 and 90".)
Who said anything about databases?
You need to sanitize the inputs before you:
I don't care about your fucking database and your fucking parametrized statements, you still need to verify that your inputs are sane.
Agreed - they have the right.
However, the question was "why were they doing it?", not "were they doing something wrong?"
Average speed on uphill sections vs downhill sections?
Fastest point on route?
Hardest (max heartrate) section on route?
Number of stops?
Duration walking vs running?
Distance to exhaustion, time to exhaustion? (When you can not complete the route as planned.)
Average intensity (heartrate)?
Lol, Turnbull was the communications minister who said that data retention was pointless!
http://www.theguardian.com/aus...
https://newmatilda.com/2015/10...
https://newmatilda.com/2015/10...
http://www.smh.com.au/federal-...
But then again, he has done nothing to roll anything back now that he's in charge...
The feature also exists on Android devices (at least my Samsung Note4 from December last year), called "smart network switching".
What credit? They make a clone of a Palm Treo or cheap WinMob phone, and put good marketing around it.
We had touchscreen phones before the iPhone.
We had full-web-enabled phones before the iPhone.
We had easily-usable email on phones before the iPhone.
We had the choice of on-screen keyboards and hardware keyboards (oops!) before the iPhone.
We had apps on phones before the iPhone.
We had app stores before iPhone.
We had music players built into phones before the iPhone.
We had handwriting input before the iPhone.
We had bluetooth connectivity before the iPhone.
We had wifi-enabled phones before the iPhone.
The one thing we didn't have readily accessible before iphones was multi-touch - and if that's the secret sauce that made smartphones come of age, then so be it.
But I (and many others) assert that it was better marketing, not a superior phone, that was the key differentiator of the iPhone.
I'm a user and defender of ad-blocking (as you will see elsewhere in this conversation), but this argument is slightly fallacious.
The advertiser is compensating you for your attention and bandwidth by purchasing content that you wish to view/read.
In an non-advertising supported model, you would be required to pay something to get access to the content, in the advertising-supported model, this cost would be paid on your behalf by the advertisers.
There is an open question on whether the amount of content you are getting in compensation is in appropriate proportion to the amount of your attention and bandwidth (and security/privacy risk) being taken up, but the idea that there is no compensation provided is not quite right.
"Product placement" sounds an awful lot like renting out brain space for "acceptable advertising" to me...
And your begging button and merchandise will probably also have to be featured somewhere prominent on your site to get any of your readers clicking on them, so that will probably involve taking some brain space on the screen to promote ("advertise") these features/products.
Yes, and those households, cities, and countries usually don't have entire police departments going around trying to prevent murder, larceny and rape. The low incidence rate probably means that most of the intervention is responsive, not preventative.
Richard Vaughan's "No Evil Robots"
Stop Killer Robots