That's why, when I (soon!) become a genocidal conqueror, I will be asking people for their voting records before I line them up against the wall.

Curses! WTF is this "secret ballot" my advisors are bringing up? *sigh* There goes my invasion plan. (If I can't have the executions, then I don't see why to bother.)

And let's also hope that nobody ever actually commits rape and gets caught and convicted.

Censorship is always a two-edged sword. I have never heard of any form of censorship where you couldn't rightly cite some examples where it's a good idea, but freedom-lovers can play the examples game too.

Loose lips sink ships, but the king is taxing us unfairly. Which side are you on?

how about since you don't care about it and others seem to care about it, we do what people who care about it want?

he's right, when i take a little adderall it makes me sleepy, i can zone out and have symptoms like im sedated, i take what i feel is my dose i become focused and productive and organzied, if i take too much then i get like super add or how normal people behave with a little dose of adderall

Are you sure about that? We have a local news segment here in silicon valley on channel 4 (nbc?) called people behaving badly, and because he films people in public spaces, he does NOT need you to sign a waiver to use your image on TV, the guy who does the segment held a little ama on the news channel on the weekend where he discussed in length how public pictures are not prohibited by privacy laws.

this included places like crosswalks, front yards, side of the freeway, people in their cars, etc.. i haven't seen any open air place yet that he has had to blur images of people.

you can also toggle the num lock key for the same effect.

For the first two, obviously, you either persuade them or you find someone else to work for / rent from. Freedom of association means that they have no obligation to hire you or rent out their property to you, regardless of the reason. Hiding information about your past which you know would be considered relevant amounts to fraud.

If your treatment by a police officer or any other representative of the government acting in an official capacity is influenced by outdated posts on social media sites, or anything else apart from your current standing under the law, you've got bigger issues. In any case, odds are that a law permitting you to delete your information from the Internet, even if it could somehow be implemented effectively, would not prevent the police from learning about your youthful indiscretions.

The /proc directory is a virtual filesystem; nothing in there survives rebooting. If you want the sysrq keys to remain enabled after a reboot you need to write to that file from an init script.

There's nothing wrong with wanting it gone, perhaps, but what's wrong about enforcing that desire by law is that it amounts to trying to censor factual information about the past. You don't have to tell anyone about your more embarrassing historical moments, but it's wrong to forcibly prevent others from sharing what information they possess.

The right answer here is to simply recognize that people change, that it's normal to have some things in one's past that may be embarrassing (or even outright illegal), that everyone goes through this period of growing up, and that what one said or did as a child—or for that matter, as a younger adult—does not necessarily correlate with one's views or behavior in the present.

I've never had a keyboard phone fail

A beer spilled on my Treo 650, killing a couple of keys. I was able to buy a replacement keyboard off a random eBay seller and swap it in without much trouble (after which the phone was as good as new), but it was an annoyance all the same.

I suspect a newer touchscreen phone would've been less vulnerable to that kind of failure. Can't say that I've tested the theory yet, even though I usually have a beer in one hand and my phone in the other (to log the beer) whenever a beerfest is on.

As usual, I prefer to blame the victims (us).

On a desktop personal computer, it would never occur to you to think "Oh, I just assume I'll get software maintenance from my ISP," and if anyone ever actually said that then you would point your finger at them and laugh and their over-the-top stupidity.

But change the form factor of the personal computer to handheld and suddenly we don't do the pointing and laughing. On the very face of it, it's JUST AS STUPID. So WTF?

Users are not exercising their common sense. They simply aren't. You can make excuses for not using common sense and explain why we did this very obviously stupid thing, but don't pretend it's not happening. Every morning you're getting up and putting a "kick me" sign on your back. You know that you're doing it and you know what consequences will invariably flow from it.

"I don't have any other signs to put on my back! All the signs on the market say 'kick me!'"

"Just because I wear a 'kick me' sign that doesn't mean anyone really has license to kick me! They shouldn't be doing that to me!"

Ok, go on and say those things. You even have some valid points, and the things you're saying might even be technically correct. But that doesn't mean you don't sound stupid, because you don't have not getting kicked in your requirements! WTF, people?!

Stop thinking of handhelds as some weird special case where ALL your experiences with software maintenance magically don't apply! THAT'S STUPID! So yeah, I'm a victim-blamer. You know when you buy your PC from your ISP or from a manufacturer who has a history of preventing maintenance, what's going to happen. And when people pretend they don't know the invariable consequences of buying PCs from ISPs, the stupidity takes on a flavor of dishonesty. Mmmm, yum!

All the embedded links are relative, actually. The browser shows them as file:// URLs because they're in a local file. They do appear to be session-specific, and don't work for me, either, now that my session has timed out. I'd probably have to download the pages all over again to get updated links.

Here is the script:

(Leading spaces were replaced with underscores to preserve layout.) The file "cookie-header.txt" needs to contain the contents of the header, including the "Cookie:" prefix, as transmitted by your browser. You can get this by using Wireshark and the "Follow TCP Stream" function, among other methods.

They would sync their encrypted password database to the mobile device. Alternatively, the password manager could generate the long password itself on the device if that is where the account is being created.

The fundamental problem with this scenario is that you're proposing to place your trust in a public PC you can't control. At a minimum, that particular login session must be consider potentially compromised no matter what authentication scheme you use. Having said that, there are some options if you're forced into this scenario. An OTP hardware token would be preferred; at least that way an attacker can only hijack the current session, rather than having the means to sign in as you in the future. If you do use a traditional password then it must be considered compromised and should be changed from a secure PC as soon as possible.

The problem you're referring to relates to application-level keys which are meant to identify the developer of the application rather than the user. The only real solution in such cases is to make your app communicate with one of your own servers, which holds the API keys and performs API access on behalf of the app. Any keys distributed with an app (whether open source or proprietary) must be considered compromised.

In this case the API key is user-specific, not app-specific, so there is no distribution issue. The user logs in and generates an API key, which the application then stores for future use. The API key is the application's password, permitting limited access to the user's account. (For example, it should not be possible for an app to change the account password or generate additional API keys using an API key.)

Google Docs is an app whether it's running natively under Android or from inside Chrome. The browser doesn't replace any apps; it's just another platform for apps to run on—one with a lot of historical baggage, overhead, and limitations compared to the native APIs. It's good to provide a mobile-optimized web site rather than requiring visitors to install an app, but a native app will always have the potential for more sophisticated integration, in terms of both functionality and the native look-and-feel of the host operating system.