tghw

Because of the nature of HTTPS, combined with Websockets, would give you a really easy way to proxy yourself out of restrictive internet situations. Use an HTTPS connection to Google to domain front to an App Engine instance that has this running on it. Now you can TCP to anywhere from anywhere and it just looks like HTTPS traffic to Google.

I'm not saying they shouldn't get a living wage before tips, they should. In fact, if we got rid of the minimum wage exceptions for servers, we would immediately revert tipping to what it was intended to be, incentive for good service.

What's dismaying is how many people in this thread don't even want to have to think about how the person driving them is a human being, often just trying to make ends meet.

Whether they mean to or not, Uber has been making the drivers less and less human. Now it's backfiring.

Lyft includes tipping in the UI, after the ride. As a result, their drivers don't have as much of a reason to hustle for tips.

I'm more dismayed that the thought of giving another human being a little extra money to thank them for good service is so painful to people that they try to avoid it at all costs.

Uber's model feels like it's trying to make the human driver into a robot. Until we have actual robot drivers, I prefer a system that has the tipping built in, e.g. Lyft.

I exclusively use Lyft because they allow tipping. If someone gives me a good, comfortable ride, I want to be able to easily throw a couple of bucks their way. If I'm taking a car service, then I can afford a few extra dollars. Plus, with it being built into the app, there's no need for them to hustle you about it.

Nobody said dead.

The pharma lobby?

I agree that talking about a $0.7X to the dollar pay gap isn't helpful, since it isn't controlled for a number of factors. But there still is a pay gap of 2-20%, , depending on the industry, attributable only to difference in gender.

It's better than it's made out to be, but that there still is a gap is not right.

Except for two things:

1. Women are expected (societally) to be more accommodating and compliant throughout most aspects of their lives, meaning they have less practice and comfort negotiating.

2. Even when women do negotiate, they end up being penalized for it, probably because of the expectations mentioned in point 1. See http://www.newyorker.com/science/maria-konnikova/lean-out-th.... Underlying study is here: https://www.cfa.harvard.edu/cfawis/bowles.pdf

tl;dr If you use Python 3 in ugly ways, it will be much uglier than if you use Python 2 in pretty ways.

- What are you missing that browser plugins add?

- Cards do have stable URLs. Not sure why you think they don't.

- A Github url to a commit will link to that URL. Powerups can be used if you want tighter integration.

- Very few people actually need this. If you do, then you need a fully auditable system.

- Copy paste the card URL. Again, card URLs are stable and Trello will detect that it's a card URL.

- There are fairly extensive keyboard shortcuts: https://trello.com/shortcuts

- Such as?

- Boards -> Lists -> Cards -> Description/Comments/Check Lists/Polls/etc. At least 4 levels.

- Is this a prediction??

- Sounds like a Firefox problem.

- Are you putting logs in the titles of the cards?

- Such as?

- Haven't ever seen an ad in a card.

It sounds like you set out with the intention of not liking it and found (or made up?) reasons.

Final will do it. They allow you to create a card for each payee, which you can cancel at any time.

https://www.getfinal.com/

(I have a card, but am not otherwise affiliated with them.)

Not sure why you're getting downvoted, you're describing git correctly.

If anyone is questioning this, just play with `git rebase -i [some old changeset id]` and you'll see that it's just an ordering of patches.

That's hardly their main focus. Go to https://www.aclu.org/ and click Issues. LGBT Rights are just one of 18 top level issues (many broken down into many more related issues).

I love the EFF, but they don't cover voting rights, disability rights, immigration rights, racial justice, etc.

"Bates found that this rationalization was largely untrue. In fact, he noted, Aetna pulled out of some states and counties that were actually profitable to make a point in its lawsuit defense — and then misled the public about its motivations."

It could be the case, but it seems that, in at least some of the markets, it was not. They were pulling out to try to invalidate the DOJs finding that the merger would produce insufficient competition.

If only ProtonMail could import old mail, I would be giving them money.

Tangential: This is the first time I've seen the .google TLD in use. Looks...weird.

A lot of it has to do with geography. Europe is quite a bit further north, and doesn't experience some of the heat that the US does.

It always helps me to remember that Rome is further north than New York.

How exactly do you close the API to outside requests? It's not hard to reverse engineer most APIs, either by decompiling the app or just watching the wire.

Reading medical study meta-analysis published by The Cochrane Collaboration[0]. There's some fascinating results that run counter to current medical advice.

For example, "Vaccines to prevent influenza in healthy adults" concluded, in part: "Vaccination shows no appreciable effect on working days lost or hospitalisation."[1]

[0] http://www.cochrane.org/evidence [1] http://www.cochrane.org/CD001269/ARI_vaccines-to-prevent-inf...

I'm not sure I like their "we'll do it all for you" approach. It seems like there are a lot of ways to accidentally break config files. In general, I'd rather not anyone touch those without me knowing what it will do.

Fortunately, the certonly script grabs the cert and puts it in an easy location. Updating the config from there is easy enough.

Really?? I found it dead simple to use.

1. Install the app. 2. Run the certonly script, following the prompts. 3. Point the server at the certificates.

The only hitch was stopping Nginx long enough to do the domain verification. A three line bash script fixed that.

You're picking nits. The intent is clear from multiple reproducible sources. For there to be any issue, the developer (or an assignee) would have to file suit, at which point it would be trivial to demonstrate that it was clearly communicated that the old versions assumed a second license. The copyright holder would have a very steep uphill battle to show otherwise.

Dual licensing happens all the time, often with GPL and some other, more restrictive license. He clearly states that until X date, you may only use the code under the Fair Source License. After X date, you may choose which of the two licenses you would like to use.

There's no conflict in adding another license, it's his code, and the license and his directives dictate how people can copy and distribute it. Nor does the fact that there's only one license in LICENSE.txt really mean anything. README.txt is clear about the dual license in its "Licence" section.

Came here to post exactly that article.

I'm a big fan of Fog Creek (having worked there for 7 years). But I'm a little stumped on who this is for.

Without any persistence (Mongo, SQL, Redis, something) this is nothing more than a toy. Right now, the forums suggest setting one up via some PAAS, which obviates the whole "it's only one step" thing. Presumably persistence is on its way, as this is just a beta.

Persistence aside, it's still lightweight for an experienced developer. All of the things listed in Joel's "look what you don't have to do list" exist because they are good practice. In fact, 16 years ago Joel wrote about the 12 things that you need to make good software[0], which, coincidentally, includes almost everything on that convenience list.

On the other hand, if you're just learning to code, not having to provision a server or deal with Git isn't really fixing the hard part. Heroku and GitHub are making that easier and easier. HyperDev drops you right into an active NodeJS project without explaining what package.json is, where you define your views, or even what views are.

This leaves it serving a very narrow demographic, which is often the problem with these sorts of tools. Hopefully Fog Creek will be able to make it more broadly appealing before the shine wears off.

[0] http://www.joelonsoftware.com/articles/fog0000000043.html

1) Check out Meteor. It's very similar and can be self hosted. https://www.meteor.com/

2) You can use your favorite Node SQL package for that. Yeah, the DB has to be hosted somewhere else, but that's getting pretty easy if you're using PAAS services.

3) Yeah, that'd be nice.

What false premise? Fivethirtyeight is not wrong. In this case, with seemingly reliable tests (>90% accuracy), only 27% of positive tests are correct. If you're talking about something that has an invasive next step, like a biopsy, and you decide to increase the number of tests done each year, then you are going to also be increasing the number of unnecessary invasive procedures each year as well.

Take mammograms. It's a fairly non-invasive test for breast cancer. Everyone wants to reduce breast cancer, right? Unfortunately, the data is very much like fivethirtyeight's example. In a 10 year period, 1 in 2 women are harmed by a false positive and 1 in 5 were harmed by an unnecessary surgical procedure. What about the lives saved? None.[0] Screening mammograms only end up harming patients.

While it may make sense intuitively that more screening must be better, the data generally fails to back it up.

[0] http://www.thennt.com/nnt/screening-mammography-for-reducing...

That's exactly my point. Citing the first amendment is a very weak argument, even weaker when he cites it in a situation where it does not apply. It's so weak that it weakens an argument that otherwise is very strong, that the press is so influenced by money that they cannot handle any amount of criticism, even from a cartoon.

Relevant XKCD: https://xkcd.com/1357/