I bet your problem is that someone else has the same email but with a dot in it somewhere. I ran into this problem a few years back-- I had also registered lastname@gmail.com, and I started getting emails for l.astname@gmail.com and a couple other variations.

There was an Asian couple in Virginia, I got their emailed Apple Store receipts. And there was someone in South Africa who was renting out an apartment, so I got all kinds of information from prospective renters like photocopies of passports and pay stubs.

I ultimately had to abandon that address and get a different one.

If I forget my password on my Iphone and guess it incorrectly 11 times in a row it wipes itself out... Sometimes I do forget passcodes.

Yeah, it's crazy. "Let's make some invisible character with a variable width significant."

Like Makefiles do?

• http://stackoverflow.com/questions/2131213/can-you-make-valid-makefiles-without-tab-characters

"Germany Got Debt Relief After WWII, Refuses Same For Greece Today"
http://www.huffingtonpost.ca/2...

Try the settings - standard kernel options for linux don't work for this.

The only options that work today are using driver level code for audio processing or a real time Xenomai task.

Please support Thomas Gleixner via the Linux Foundation to help to fix this limitation of Linux: http://lwn.net/Articles/572740...

Until then, all high performance low latency audio processing in linux needs to not use any user level tasks.

Jeff

... Because I need less than 125 microseconds mixing processing latency (12 samples at 96 kHz) so that in-ear monitor mixing for live performance can be useful - requires a total latency from microphone to wireless receiver to CPU to processing to wireless transmitter to in-ear monitor of less than 5 ms. Until Linux user tasks can be scheduled with this kind of hard real time timing accuracy, mixing real time audio in user tasks doesn't cut it for live audio. So I myself am required to do my mixing and processing for real time audio either in the kernel driver, in a RTLinux task (in kernel space), or in a Xenomai task (see xenomai.org ) running at a higher priority than Linux.

The Tesla is not a car you buy because you can't afford gas. It is a car you try to afford because it is the best car overall: http://www.businessweek.com/ne...

Until relatively recently, these re-directions would adversely affect a debian/ubuntu linux system update procedure. A cron job would apt-get update and pull in new index files. Since the transport was not encrypted, the index files would not be what the apt system were expecting. It would store the content of the redirected web page instead of the proper index files into a cache and then apt-get update would be forever broken until you manually figured out how to delete the corrupted files someplace in /var/*/apt

ISP's and WiFi Access points that do this redirection are the reason why HTTPS everywhere is a good idea.

Additional thought: I wonder if the police would be requesting their own members to be anonymous on the internet?

--jeffk++

But that would be authentication between the client and AP.. How would 802.1x on WIFI work when rcmp.gc.ca is the server that has to authenticate the client?

--jeffk++

Thanks! That would be a fun experiment to see how much businesses would be affected. Can you even put 802.1x in the wireless access points and cell phones?

--jeffk++

They need to submit their request to the International Internet Board of Governors!

--jeffk++

> A complete nightmare, and even if you get it working, you wind up with an unstable system.

It's not as bad as that. I built 2 back back in 2008-2009, and they were rock stable-- kernel panics were extremely rare. They also didn't require much in the way of hackery. I put the EFI boot loader on a thumb drive and kept my OS X drive as free of hacked bits as possible. I wanted to be able to hook it up to a real Mac and boot it without issue, and I achieved this goal. Still, I would never recommend them in a business setting.

One of the machines was my daily driver, and dual booted Windows. The other ran OS X Server and was the fileserver in my house. The specs on the server were enough to get the job done, but my daily driver gave me top of the line Mac Pro performance for about $1200.

The only problem was OS updates-- they usually broke something. I maintained a bootable clone of both machines' boot drives, and waited a few days for other hackintoshers to find and figure out how to fix the issues before installing those updates. Both machines ran Snow Leopard for their entire term of service, which ended last year. They were replaced with refurb Mac minis. The hackintoshing was an interesting experiment, but I wanted a new OS without more hackery, supported hardware, and worry-free updating again. As a side effect, my electric bill fell off a cliff, which was nice.

I think the fish accidentally a word there with its mouthful of teeth!