While there at it, can they make some that slip over popular andriod phones? By the look of the design, it seems like it'd be pretty easy to make versions that fit other popular phones, and keep using the same bluetooth keyboard (fyi, it extends the length of the phone a bit, so this isn't a question of how much non-screen real estate exists at the bottom of the phone).

Slightly off topic... anyone know of a good keyboard case for a galaxy S4? The only one's I've found add incredible bulk, have poor reviews, make camera use very awkward, and just don't seem usable. I miss my evo shift keyboard, and G1 before that :-(

about 800 rpm at 60mph.

rarely, but frequently enough that tire chunks are commonly seen on the highway (mostly from 18 wheelers)

WTF that has to do with this is beyond me, except that you didn't take two seconds to think about it (or google it) before posting and made a really bad guess :-)

Assuming it had significant gyroscopic effects, that would be just as bad as not being able to turn! Most bends in roads are banked, and many are banked a lot. Go into one of those with a strong horizontal gryo and your car would be on two wheels.

It's really not that hard. I've been through it on big projects with extensive history and multiple sync'd outside projects with internal patches and the whole 9 yards.

Start with what you own. If you don't own it, leave it be. Do all files in one big patchset. That'll be the point in time where stuff before and after won't diff very nicely, It sucks, but a year from now, it won't really matter.

Include a per-commit check. That way, no new problems get introduced.
Include the header. One does HAVE to use vim or emacs, but the mode lines I supplied work with those two. If your group has another common editor, add its mode lines if it supports it. It's just a helpful extra, and is safely ignored by other editors. And if none of you use vim or emacs, disregard those lines.

If someone has a branch that was cut prior to the big reformatting patch, they'll have to deal with it at merge, or rebranch or rebase. Sucks, but it's a one time thing.

The alternative sucks more - having code with mixed standards. How do multiple groups deal with that? Your patches are going to be even worse! Someone uses their editor to indent a block or copy/paste it, and all those mixed tables and spaces go to whatever they're using, causing all lines to diff poorly, instead of just the little pieces they touched. It's awful, as you noted.

Your specific problem you referenced was users that were using an outdated 6 year old .vimrc that had been mailed around, and it caused problems with your code because of the difference in coding standards. ADDING THE MODE LINE FIXES THAT!

The rest of it sounds like you just don't want to be bothered to clean up the problem, and just want to complain and blame others. It's trivial to fix. It comes with a small cost (one time giant ugly patchset), but it's easy. And you don't need that one time giant patch.. you could let them be fixed as changes are made, but I wouldn't recommend that as every future patchset will be more complicated than it needs to be. Just get it all out of the way in one go and move on.

For integration with external code/repositories, work within the standard of the governing body. If they have a well defined standard, you can even add the pre-commit checks to your personal repository if you want. In general, this doesn't matter as much as the above, cause either your guys are behaving well and working with the external group, or they're not - manage accordingly.

That DOES solve the case in point. AT&T are just finger pointing and trying to latch on to a cash cow, while gaining an unfair advantage in customer pricing.

True net neutrality helps the little guys everywhere. Netflix noted that on the service side, as others have here, that if big companies have to pay for connectivity to the last mile to the users, small services will be hurt. It also makes absolutely no sense (services already pay for their internet access; customers already pay for theirs; there's lots of middle men, and those guys are trying to get around each other and get profit from customers on the other side).

The other side is that a competing ISP would also have trouble. If AT&T, for example, was charging all websites for their bandwidth to the end users, then at some point they really don't have to charge the end users anything. Where's the balance? How would a new ISP charge his customers?

The ISP tiered pricing is simply wrong if their network can't handle their customers requests. The cheapest possible plans often get you very good download speeds (ex. 15Mbps for the first 12months at $14.99/month for time warner). That's the problem right there. Their standard fee for that is $35/month, and $15 will only get you 2Mbps... which is still plenty for most people.

I'm all for cheaper and faster internet access, but if it's a problem for them, then they should put the squeeze on their customers, not the services their custom wants. Netflix is a selling point for the ISP; something they should, if anything, be paying MORE for to get improved quality for their customers.

The only reason they should want to squeeze netflix is, IMO, because it competes with their other services - TV. That's anti-competitive through and through.

You should/could also slap some mod lines at the start of your files. Ex:
# ex: set tabstop=4 expandtab smarttab softtabstop=4 shiftwidth=4:
# -*- Mode: tab-width: 4; indent-tabs-mode: nil; basic-offset: 4 -*- #

You could also just run it through a tidy program and a site-specific config if you really want to be a formatting nazi.

You're doing it wrong.
One way is for Service A to establish a trust with Service B (ex. using SAML), and have the user at Service B authorize that usage. Service A and B agree on a unique key for that exchange (ex. private/public certs), and Service A issues those commands to Service B using its user + that authorized cert to perform on that users behalf.
Of course, if Service B offers no such ability, then you'll need some sort of kludge like you suggested, but that doesn't make it right. Even so, they should protect those credentials in a much more sophisticated way than just another table in the same DB with an encrypted version of the Service B credentials (ex. a key server appliance).

Bump.
Seems like this is a flaky domain with some messed up settings. There's a very good chance comcast cached an NXDOMAIN. Wouldn't be too surprised if something similar had happened with his little personal site. Many DNS servers serving large volumes of users ignore low TTL's and cache longer than normal. It only hurts edge cases they don't care much about since large established sites do not rely on fast DNS updates for things like load balancing or failover.

Use another DNS server is still a good suggestion.
Without a more extensive test (1 in a few hundred random sites is not a statistically good sample size... could have hit the same random one out of a million, for example), this doesn't really say much.

The poster put enough time into this that it shouldn't be difficult / much more time intensive to expand the test and provide a larger list of good/bad domains. Those could also be weeded out to find those that are generally flaky or configured poorly. If any remain, then test those.

His buddies personal site didn't work for an hour or so, and some random chinese site doesn't reliably resolve... that's not enough to start the scare tactics (...that there about a million or more websites similarly affected").

What is the alternative, assuming you don't have the understanding and ability to verify it? Are you making your own? Good luck.

BS. "sensitive stuff" here is an encrypted blob. It does not live solely on Dropbox servers. A physical lockbox (your analogy, not mine) would be a single physical item. Leaving said item at some shady place means that, at the very least, they could destroy it. Physical locks are also much easier to bypass if you don't care about destroying the box, as opposed to brute forcing a well designed encryption scheme.

If you re-read my post, you'll see that i don't use those services.

You asked (in the post I replied to), "What if he doesn't trust the implementation of the encryption in the password manager?"
There's a long list of options that anyone should be able to easily discern if they are at the point they don't trust a particular implementation, and that was my point. What was wrong with all of the other options I supplied (which should have been obvious next steps)?

And the original post asked what we use. What do you use?

These "what if's" are getting a bit silly. I'm not saying he should trust that implementation, but if he has reason not to, I'd hope that he's also smart enough (or believes he is) to pick an encryption scheme he does trust. We're really just talking about how paranoid someone wants to get with passwords that will be used on a lot of hosts, many of which are problem secured weakly. IE. seems like you're trying to create a flow chart out of this thread :-)

* 1password +dropbox or similar stuff? - don't trust dropbox
* 1password + your own sync or backup? - don't trust 1password encryption
* clipperz + your own sync or backup (btw, clipperz is open source)? - not sure what you/he may not trust
* name-your-own-encryption + a text file? - maybe you don't trust your own network connected OS
* any of those, put inside a vm?
* any of those, put inside a vm using full disk encryption in the vm?
* ... with the vm files mounted via loopback encrypted again?
* any of those on separate hardware (Raspberry Pi, an old android phone, HDMI dongle PC, etc)? ... this list can keep getting longer and longer.

The orig question was "what do you use?", not "what should I use if I'm a paranoid schizophrenic that doesn't trust anything, especially the aliens that keep talking to me in my sleep?"

To answer the orig question: I use an encrypted text file. I occasionally check out some of the offerings out there like lastpass, keepass, clipperz, etc, and even recommend those to others, but my simple encrypted text file has served me well for a long long time, and it is by far the fastest interface there is (vim). There is a security risk with it - one could do memory scraping while it's open to read the buffers, or use a key logger to snag the password for the master key, etc; and there's portability issues - it's trivial for me to get access setup once I'm on a linux OS anywhere in the world, but I don't always have that on me, and that hasn't been a problem.

Ad-supported music is not a crappy source of revenue. Ad-supported internet streaming music IS a crappy source of revenue.

Every user you add, adds to the bandwidth, cpu, power, etc requirements for internet based streaming. There's also a very direct and easily tracked log of exactly how many streams to how many distinct devices were happening at the same time, and when.
The old radio broadcast reaches fewer people with one tower, but seems to be doing ok still, even with far fewer listeners these days. That *was* very big business.

IMO, the "fix" is to cut out the middle men, starting with the streaming services. With things like AWS (Amazon Web Services) and the like, there is no reason that a generic streaming software VM couldn't be used individually be all artists, with metadata pushed to distributed lists. IE. why do bands use myspace/facebook/etc for their pages?!?! I think it'll get there someday, but there's way too many people pushing to be middle men, all the while complaining about the middle men.

Wow, people are slow. Ban them from future flights on your airline if they violate policy.
That can be temperred in various ways: 3 strikes rule; time based ban (ex. banned for N months); pay a big fine to re-instate priviledges; etc.
It'd even be more flexible, and probably more effectiive, than this law.
BTW, how do you expect them to enforce this law? They'll probably just end up asking the person to stop using their phone, and nothing will be done about it... no different than if it were just their policy.

Are you fucking kidding me?!?

So we're all in agreement now that there is no technical reason to ban cell phone usage (ex. using data services during the entire flight is fine);
And you're fine with people talking, or kids screaming;
And you're simply more annoyed by phone calls because you can't listen in to the other side of the conversation as easily (as and aside, if they were on speaker phone, would you be ok with it?);
So you think it's perfectly fine to legislate away the (potentially) more annoying voice phone calls?

Don't get me wrong... if an airline wants to make it a company rule, or even a per-flight rule or per-ticket-class rule, that voice calls are not allowed on their flights, fine. I'd probably even look for and prefer those flights. But how does that justify a law?

Reminds me of smoking bans (which I am against), but at least they have some semblance of credibility in that the health of the staff is being protected. Otherwise, they're just as stupid. Bars were allowed to ban smoking in their establishments without the smoking ban law, and the market should have decided - you don't have to go to a bar; you don't have to go to a bar that allows smoking; there's a grey area for people working there (I don't think they have to work there, so the ban is wrong, but at least I can appreciate that argument). There's no legal justification for banning voice calls on planes while allowing text and data.

Completely agree.

Maybe if the difference you could save were significantly higher than $1, it may be more interesting. Ex. if you could do this on amtrack going cross country and swap along the way to save $100 on the trip, but it's just $1 on the daily commute. If you are that strapped for cash, you'd get a buck faster by just asking people for a dollar, or save more by just hopping the turnstyle (as phmadore points out below).

If they're going to talk arbitrage of these tickets, they should at least include senior discounts into the mix. Swapping with one of them would save you even more. How about city workers or college students (anyone with a heavy discount... I'm assuming they do that there, since they do it in other places)? They could even lease their cards on the days they don't use them, and that'd surely save more than $1.

Lastly, the price difference is silly. You want to encourage people to use mass transit, especially for long trips where they'd otherwise be driving into the city. Why charge them more!?!

IMO, there's also another glaring flaw in Johnson's premise that students gave better student evaluations of teachers who graded more leniently. There is a HUGE assumption there that the various teachers running the same classes were all equal in their quality of teaching. Why is it so difficult to believe that some teacher was able to reach and educate more of his students than someone else?

Statistically, I understand there should be some sort of even distribution, but the sample size (in number of teachers per course) is not large enough to be of statistical value.

One year, I had an art history teacher whose class was at 7:30am, in a dark lecture room, with a dim projector on the whole time, and spoke through an ancient 3" amplified speaker with an voice that was already monotone and droned on and on and on. I got a D-. The next year, I did more research on the available teachers, and found the one that engaged the most and who had more people getting higher grades. He was fun, taught in a well lit class in mid-day, involved us in projects to learn (ex.create an interactive presentation of some artist with a group of other students for homework, as opposed to filling in the blanks on a test in a dim room with projected images), and I got an A+, go figure.

I'll admit his tests were slightly easier (fewer exact date type questions (what year was this created, versus during what time period), multiple choice on name questions, rather than having to fill it in spelled perfectly, etc), but I also learned a LOT more, and neither graded on a curve.

I also take some offense to applying various curves or rankings etc to students. Given a class of 30 people, it's almost guaranteed that you'll have some years where half the class are "A" students, and some years where there's hardly a one, and that's assuming that the teaching and material are equal.

Overall, I'd agree that there is grade inflation. Jacking with the grades isn't going to fix all the underlying problems, and it will create other problems. He notes that one of the most likely reasons are student evaluations - so untie those from teacher review (instead, to review a teacher, do so as one should for reviewing any employee... go watch them while they're actually working, and only use the reported figures to identify people that should be reviewed first or may need help).