afhof

Why did use Lenna?

"Two reason was stated in "A Note on Lena" by David C. Munson. First, the Lenna image contains a nice mixture of detail, flat regions, shading, and texture that do a good job of testing various image processing algorithms. It is a good test image! Second, the Lena image is a picture of an attractive woman. It is not surprising that the (mostly male) image processing research community gravitated toward an image that they found attractive. "

http://www.ee.cityu.edu.hk/~lmpo/lenna/Lenna97.html

Its not so much that the image is pornographic, the interesting part is that most computer graphics group is male. If there was a 50/50 male to female split, I doubt this image would have become the de facto test case.

"The workers work and live in the factory dormitories – allowing flexible time and really quick manufacturing, something which would never happen in US or the Western Europe."

Its not like thats ever happened in the US.

A law that isn't currently enforced is a dangerous one. What would happen if all cops started pulling over anyone driving +5 over the speed limit?

From a completely selfish standpoint, shouldn't you try fixing yourself first rather than "fixing" other people?

Do not do this. This goes in the bucket of ideas-that-sound-good-but-aren't. If screen diffing is how you want to test your program, you should use / write an independent program to do so.

That said, there are some serious problems to using screen diffing. First, it requires manual testing. You will need a pair of human eyes to determine if a change is breaking or not. Second, there are a lot of false positives that make testing slow. When a few pixels are moved on the page, is it okay? Third, there's a _LOT_ of data you will need to look at before you can be confident about the diffs. You will need to do a screen shot for each page for each resolution for each git commit.

The signal to noise ratio is very low for screen diffing. You would be MUCH better served by using (in the case of web apps) Selenium web driver tests to make sure your page works. As a bonus, with automated tests you can use git bisect to quickly find the offending commit!

It would be a lot more convincing if they could say Microsoft Stack Ranks And No One Else Does. Google, for example is a strictly stack ranked company and hasn't folded (at least in my opinion) into a caustic environment as described in this article.

The Youtube lua script in VLC breaks often. If you don't keep your VLC at head it becomes very noticeable.

Arguably these are great advertisements for the places they represent. If you were choosing between places to travel to, I think this would be helpful.

5000 queries a day

https://developers.google.com/google-apps/tasks/pricing

Real property isn't quite the same. With real property the owners have to pay taxes based on the land value which incentivizes owners to make use of the land.

With a short domain name, the owners waste the short name for the cheap price of domain registration ($20 max?).

Before you make a knee-jerk decision about this, read the (very short) bill here: http://www.leginfo.ca.gov/pub/11-12/bill/sen/sb_1401-1450/sb...

----

There seems to be a number of other provisions in this bill that the original article glossed over, specifically surrounding disclose of the number of warrants used. Why law enforcement is so squeamish about releasing numbers is mystifying. Is there some legitimate reason to not be forthcoming?

This is wasteful of people's electricity and inefficient at the same time. Opting people in to wasting their battery life or raising their electric bill is treating users as a means rather than an end.

I think you missed the point: image the filters should be applied before pictures are distributed rather than letting the browser do it. The reason to resize it and sharpen it is because browsers do a poor job resizing, where doing it yourself will result in a better looking photograph.

This shouldn't be automated by a plugin AT ALL, and should be done based on the type of image it is. (icons, clipart, logos, etc. would make poor subjects).

Percentiles I think greatly help the appearance of rankings. Knowing you are in the top 95% vs. knowing you're a measly 2 standard deviations above the mean.

This is isn't specific to Google, and I would go further and say that ISPs are a much juicier target than Google. ISPs have the raw access to all your traffic and wilt more easily when pressed by law enforcement (eg Carnivore).

I don't think there is an easy way to solve this. From law enforcement's perspective, big tech companies have already done the hard work of getting users' data; all they need is a warrant or a NSL or any other magic ticket. That is the problem we should solve.

Disclaimer: I work on Google Analytics.

Yet another case of Betteridge's law.

So if the buyer just left a bad rating, but no words, could she still be sued? One one hand voting seems like an extension of free speech, but on the other it feels that online voting shouldn't be counted as slander / libel.

I dont believe so. Since the heart rate could be much higher, it would alias, and the camera wouldn't be able to tell the difference between normal heart rate and low heart rate.

This is what I suspect could happen, with two possible heart rates matching the same set of samples:

http://upload.wikimedia.org/wikipedia/commons/2/28/AliasingS...

The webcam framerate should be at least double the heart rate to get an accurate measurement, not the other way around.

It seems that the Nyquist-Shannon sampling rate would be too low for the results to be accurate.

Its too bad that most people don't have a basic appreciation of statistics or probability. Its too bad Schneier only spends a tiny paragraph on it: "Even though this will be in the news for weeks, we should recognize this for what it is: a rare event".

The chance that a person will die from a bombing, or be shot, or their plane crash, or a hurricane kill them is so small that there is almost NO reason to be afraid of it. It is far more likely that a person will die of Heart disease or cancer than any of the above. What will almost certainly kill us, we accept. What is almost inconsequential to us, we abhor.

One wonders what Go was doing with that extra 36% time in the previous version. Was it all due to map memory allocation and associated cache misses?

The Drip Stream is kinda cool, since it effectively prevents "everything" from becoming popular, but also makes it easy to bootstrap if there aren't a lot of users playing. I am very interested in how these approaches affect user return rates, since it would be very easy to try a bunch of algorithms on different users and see which gets more people to come back.

I suspect that the kind of scaling Go was intended for was programming scale. A lot of the design of the language seems specific for large scale projects (statically compiling everything, not having unused variables, explicitly naming all imports, fast compiler, test and benchmarking as builtins, code changing via go fix).

These are problems I have seen with larger java projects with unused imports, unused variables, library dependencies, long compile times, etc. I think that Go's niche is for extremely large projects, but it remains to be seen if it will work.

Could you post the exact commands you used? That high connection time for google looks like SSL setup.

You did work together, or more accurately, you did all the work for them. You took the risk of making an app that users like, 9gag saw that the risky work had been done (and that people would use it) and now knows that they don't need you any more.

That said, I am impressed by a person who can get thousands of people to install his/her app. Now that you know how to get people, you can traverse the trademark line more safely in the future.

Borrowing is a such a weak word for stamping their obnoxious logo on unoriginal pics. Its somewhat saddening to me how popular they have become due to their sleaze. (Seriously: Why create anything new when you can rise to popularity on the works of others?)

Don't read too seriously into that, as most users of 4chan are loathe to use reddit (and strongly consider reddit to do the same thing that 9gag does).

This was a bad decision. Api change should never be made in 48 hours for a single customer. These are the kinds of decisions you are stuck with for years. Worse, if you ever want to get rid of it, you can't! Good Apis don't slide the carpet out under dev's feet.

Making knee-jerk, one-off decisions are a sure sign of bad things to come.