Go tell Google, Opera, Apple, Mozilla and Firefox to remove the print option; they're letting their users use the internet wrong! Google Maps; you're doing it wrong! Printable tickets: you're doing it wrong! Purchase receipts: you're doing it wrong! Cheat sheets; you're doing it wrong!
If you use CSS to define the image as a 2x2 inch image, you get 300dpi by making it 600x600 pixels. Your printer should be able to handle this as intended, though your screen will probably not.
You are right that DPI means nothing without dimensions, but dimensions aren't a problem. CSS is perfectly capable of defining sizes by real-world units such as inches or centimeters. On paper and even on screen (assuming your browser doesn't try to outsmart the CSS, as most non-desktop browsers try to do).
Then again, few websites bother at all to define how their website should look printed out. Just look at how utterly unreadable Slashdot looks in the print preview.
Specifying an image for a website to be 300dpi is uncommon, but it's certainly not unreasonable if you care about printability.
I need the image in 300dpi (web development, where print resolution means squat).
Webpages can be printed. If your website has images on it, they may need to be at a higher resolution than displayed on screen, so they will print out well. It always enrages me when people can't imagine use-cases beyond their own experience;)
The worst insult is when somebody submits a bug report, you fix it or ask for more information and then they never reply again. If somebody throws an insult at you, it at least means they cared enough about the project to spend time on it.
Words like "fanboi" and "n00b" aren't proper insults. Whoever uses those kinds of words merely demonstrates their own incomprehension. Otherwise they would have made substantive arguments.
We use the MaxMind database. Lat/Long is not the only information stored in their databases. For instance, it also contains a column that indicates whether the record found is considered accurate to the level of, for instance, a city, a state or an entire country. These records centered on the farm are all clearly marked for "country" (which is why they point to the center of the country in the first place). The problem here isn't the database, it's people using a fraction of the database without understanding what the information actually means.
I'd torture them until they'll tell me whatever lies they think will make me stop, regardless of whether they actually know anything at all. My family would be dead and I'd have wasted precious time chasing down dead-ends, but I'd feel good having acted out my vengeance.
What kind of encryption did they use for the passwords? If they did the minimal thing of a plain MD5, these passwords might as well have been unencrypted.
Apart from the obvious use of these email addresses to spammers, the combination of a username and email address will probably let some people's email be abused for purposes beyond spamming. I.e. celebrities or political/business leaders.
It may be prettier when all the bits are in order, but it's not necessarily the best way for a CPU to process those bits.
This used to make a significant difference on old CPU's, where having the lowest byte first meant you could start some types of calculations before having read the highest byte from memory. I don't think it makes much difference nowadays, but it wasn't illogical when they first though of it.
Same for the arbitration clause. In many countries this clause would boil down to "try arbitration first, then if arbitration isn't to your liking, go to court anyway".
For both; just store the password in a cookie or local storage and wait for the next network-connected visit. As for the correcthorsebatterystaple generator; without reading the JavaScript, it could be entirely non-random for all you know. Ofcourse, this goes for code that claims to produce random data. Atleast with JavaScript you have the option of verifying the code.
These problems are not limited to just these two, but to the very concept of password checker and/or generator websites, including my own. In the end, ALL these sites are a matter of trust. This goes doubly so for offline password tools, since these have a lot more access.
Slashdot Mirror
I'm guessing the privacy of these individuals will outweigh your FOIA request, so good luck with that.
They announced the model 3 over 10 years ago already? Wow, seems like it was only a month.
Go tell Google, Opera, Apple, Mozilla and Firefox to remove the print option; they're letting their users use the internet wrong!
Google Maps; you're doing it wrong!
Printable tickets: you're doing it wrong!
Purchase receipts: you're doing it wrong!
Cheat sheets; you're doing it wrong!
If you use CSS to define the image as a 2x2 inch image, you get 300dpi by making it 600x600 pixels. Your printer should be able to handle this as intended, though your screen will probably not.
You are right that DPI means nothing without dimensions, but dimensions aren't a problem. CSS is perfectly capable of defining sizes by real-world units such as inches or centimeters. On paper and even on screen (assuming your browser doesn't try to outsmart the CSS, as most non-desktop browsers try to do).
Then again, few websites bother at all to define how their website should look printed out.
Just look at how utterly unreadable Slashdot looks in the print preview.
Specifying an image for a website to be 300dpi is uncommon, but it's certainly not unreasonable if you care about printability.
because it means he's finally gotten with a girl.
It probably means the doctor is about to suggest an alternative treatment.
I need the image in 300dpi (web development, where print resolution means squat).
Webpages can be printed. If your website has images on it, they may need to be at a higher resolution than displayed on screen, so they will print out well. ;)
It always enrages me when people can't imagine use-cases beyond their own experience
The worst insult is when somebody submits a bug report, you fix it or ask for more information and then they never reply again.
If somebody throws an insult at you, it at least means they cared enough about the project to spend time on it.
Words like "fanboi" and "n00b" aren't proper insults.
Whoever uses those kinds of words merely demonstrates their own incomprehension.
Otherwise they would have made substantive arguments.
http://www.merriam-webster.com...
It's a scavenging birds of prey, it's an airplane crash, no it's... supermanager
We use the MaxMind database. Lat/Long is not the only information stored in their databases. For instance, it also contains a column that indicates whether the record found is considered accurate to the level of, for instance, a city, a state or an entire country. These records centered on the farm are all clearly marked for "country" (which is why they point to the center of the country in the first place). The problem here isn't the database, it's people using a fraction of the database without understanding what the information actually means.
I'd torture them until they'll tell me whatever lies they think will make me stop, regardless of whether they actually know anything at all.
My family would be dead and I'd have wasted precious time chasing down dead-ends, but I'd feel good having acted out my vengeance.
It isn't free; the people had to pay a construction fee.
If I pay for a beer before I drink it, that doesn't make it free beer.
What kind of encryption did they use for the passwords?
If they did the minimal thing of a plain MD5, these passwords might as well have been unencrypted.
Apart from the obvious use of these email addresses to spammers, the combination of a username and email address will probably let some people's email be abused for purposes beyond spamming. I.e. celebrities or political/business leaders.
Would that be so much worse than a birth certificate check in bathrooms?
There's a difference between having questionable values and forcing those questionable values on other people through law.
Even if you need a cryptographic strength random number generator, the added cost amounts to a few hours of labour at most.
As for the user interface; this thing is so stupidly simple you could even use it upside down. Literally. Nobody would notice.
It may be prettier when all the bits are in order, but it's not necessarily the best way for a CPU to process those bits.
This used to make a significant difference on old CPU's, where having the lowest byte first meant you could start some types of calculations before having read the highest byte from memory. I don't think it makes much difference nowadays, but it wasn't illogical when they first though of it.
I wonder how they do their homework.
Same for the arbitration clause.
In many countries this clause would boil down to "try arbitration first, then if arbitration isn't to your liking, go to court anyway".
Should we keep capitalizing "Web" to avoid people from fearing a giant spider that can weave one as wide as the world?
...And if they succeed they have to stop?
Because calling somebody a jerk is somehow nicer than helping people improve their spelling?
Users have the right to block banners.
Websites have the right to block users who block banners.
Deal with it.
You wouldn't be saying such nonsense if you actually understood what source code is.
Does this mean they're finally up to standards compliance again, instead of being the IE6 of this decade?
For both; just store the password in a cookie or local storage and wait for the next network-connected visit.
As for the correcthorsebatterystaple generator; without reading the JavaScript, it could be entirely non-random for all you know.
Ofcourse, this goes for code that claims to produce random data. Atleast with JavaScript you have the option of verifying the code.
These problems are not limited to just these two, but to the very concept of password checker and/or generator websites, including my own.
In the end, ALL these sites are a matter of trust. This goes doubly so for offline password tools, since these have a lot more access.