Not if you're a journalist you're not. Parent has a point: if the journalists exceed the limit, have their credentials revoked and start attending as private citizens instead, what's the UW to do about it? Ban communication devices and have them "detained" at a TSA-like security checkpoint at the entrance? Install a Faraday cage around the avenue and hinder the radio and TV stations too? Jam GSM/UMTS/CDMA specifically and hope they don't leak any jamming signal outside and get in trouble with the FCC?

Sorry if this is totally off, but aren't patents supposed to prevent the manufacturing and distribution and/or selling of the patented items, and have nothing to do with the usage? That means this statement is at least misleading, if not down right lying: “When the government grants you the right to a patent, they grant you the right to exclude others from using it.”

To clarify: If I use SSL on my website, I don't think this patent applies to me. I didn't make SSL, and I'm not providing SSL for download. Go sue the OpenSSL guys, or sue Debian, Red Hat and Canonical for distributing your patented thingy, and hope the EFF doesn't chime in.

The big guys who settled are making and selling products that ship SSL within. Except Exxon Mobil - I have no idea what they could sell me with SSL in it, and appear to have settled just because the inconvenience of a lawsuit wasn't worth it. If he isn't asking for crazy amounts, the big guys may not even twitch and just pay up. As in "hey, I see your patent, it doesn't look like it could hold in court, but... you're asking for peanuts, so here you go, please go away". Because in that case the lawyers would cost a lot more just to throw the case out of court, and this guy's company doesn't have any assets that can be reposessed to cover the costs.

Conclusion: he's not going to sue anyone small, and he'll stop when all the big cows have been milked - unless he meets the wrong kind of cow before then.

That's a very interesting point there about overtime. Why would the 13th hour not be classed as overtime? The person is working one hour longer than they would otherwise. Cost of doing business during the night that falls between a Saturday and a Sunday when the clocks go back. And when the clocks go forward, the shift is 11 hours, and that's it. You don't pay the worker for 12 hours. Don't like it this way? Set schedules based on Standard Time, so workers have to come in an hour "earlier" or "later", depending one which way the clocks go.

I wonder what the regulators would have to say about this.

"damage accelerated by Nokia's failure to embrace big trends". So let's embrace something else that isn't a big trend: Windows Phone. Yep... that would work.

There are so many explanations for what's happening to you, all of them not being "hacked", to make your head spin.

Open AP? Check your building surroundings and see if no geekfest planted itself there on count of your free WiFi.

Phone WiFi not working? Check network traffic on the wired side of the house. Multicast streams can drown WiFi - but the wires aren't affected. If it's RTP, check that's using TCP, because UDP is more likely than not multicast, and it will kill your (and your neighbours') WiFi. In my opinion, APs should not forward multicast, but I haven't seen one single AP or router that can block this so far. Any IP cameras around the house?

I've also noticed that you're micromanaging your phone. You have apps over apps over apps to "protect" yourself. Try letting your phone be: does it still happen? Don't install apps for a week after a factory reset (it's not like your phone works for long enough for you to use what you install on it anyway, right?): does it still happen? Reset the AP (pull the plug for 10 seconds). Once it's back up, without changing ANYTHING on your phone, does it start working now? I have a dodgy AP that stops authenticating me for no good reason and the only way to fix it is to reboot it. On another one it's sufficient to "save settings" in the Wi-Fi setup page. Never blame hackers when crap hardware can explain the situation.

Have you done anything related to the above (which would be standard procedore before throwing your hands up in the air in front of all Slashdot to see) before asking TFS? No? Go do that, come back.

And stop being so afraid of your own shadow. Also, if you're this paranoid, don't ever use an open AP. WTF? Not even WEP. It's WPA or bust. Here's a easy to remember password, for your AP, that's not easily bruteforced: Kitty31cat :) Or really any multisyllable word that you split in half by a two digit number (Slash15dot, since it's that kind of time?)

My bank issued me with a device called a Digipass which generates codes like those that have a life span of 36 seconds. The advantage of this is that I don't run out of codes if I have OCD and check my bank statements 100 times a day and I don't need to contact my bank for new codes. The code also expires after successful login, so there's no double teaming. For someone to successfully log into my account, they'd have to be attacking me as I do my transactions. But not even then, as each transfer has to be signed with a Digipass-generated code as well.