shiflett

8 ms·

1.
by shiflett 6d ago
I think they were speaking as a user. These tools create inferior products. (Still not technically objective, but true nonetheless.) That doesn't mean companies should necessarily avoid them. As a user, I always want the best possible
2.
by shiflett 12y ago
FWIW, neither of those accounts are the original @kathleen.
3.
OpenID Connect(openid.net)
5 points by shiflett 13y ago|0 comments
4.
by shiflett 13y ago
Direct link if you're in a hurry: http://pmarchive.com/
5.
by shiflett 13y ago
I'm surprised you blame us for the way Jeff is perceived. The only thing I think we could have maybe done better is omit the links to his actual replies. In retrospect, that might have been better. Our link text is pretty benign, e.g., "The
6.
by shiflett 13y ago
It's cool. Like I said, I'm sure you're not alone. Also, you make a very good point. We never expected to have to pause, but we should have put more focus on making sure people never felt their data was trapped, even in the very beginning.
7.
by shiflett 13y ago
Mapalong is still in private beta, but it's otherwise alive and well. It's a huge bummer that you think otherwise. I'm sure you're not alone. We have had to pause development, but not only is your data still there, you can still use it. New
8.
by shiflett 13y ago
We're in #openrecipes on Freenode if anyone would like to join us.
9.
Punchfork shutdown inspires Open Recipes(blog.fictivekin.com)
111 points by shiflett 13y ago|57 comments
10.
by shiflett 14y ago
It's more complicated than that. The last line has to match two out of three (for example, city and ZIP), and then it can try to do some reverse analysis on what you've written for the address line. (Even that's an oversimplification; it's
11.
by shiflett 14y ago
Broder (the NYT reporter) cites a $101,000 car, but the Model S pricing doesn't come close: http://www.teslamotors.com/models/options It could be an honest mistake, but it seems more likely the inflated price is meant to solicit comments
12.
by shiflett 14y ago
We can tell you we're not, but that doesn't actually confirm anything. (We're really not, though.) To be safe, you should consider the SHA-1 hash of your LinkedIn password to be public, even if it's not one of these 6.5 million.
13.
by shiflett 15y ago
A few corrections. IE is not preferring anything in your example. The default quality is 1.0, and since no quality is indicated for any type, they all share the highest preference. Although IE's Accept header is technically useless, it's mo
14.
by shiflett 15y ago
This is a better attempt to describe the ideal internship from both sides: http://stream.thisisapipe.com/post/5786867144/unclaimed-inte... http://stream.thisisapipe.com/post/6740079459/internships-pa...
15.
by shiflett 15y ago
Actually, you should also always indicate the character encoding, for reasons I explain here: http://shiflett.org/blog/2005/dec/google-xss-example
16.
by shiflett 15y ago
Here are two relevant posts from a startup that migrated from CouchDB to MongoDB: http://seancoates.com/blogs/gimme-bar-no-longer-on-couchdb http://seancoates.com/blogs/gimme-bar-on-mongodb
17.
by shiflett 15y ago
Safer? The risk is that 303 is misinterpreted, and this risk is why we have always used 302. I'd need evidence before taking a chance based on someone's recollection of an older version of Firefox. RFC 2616 mentions early misinterpretations
18.
by shiflett 15y ago
This post seems to be based on the belief that everything adheres to the spec. Historically, 302 has always been interpreted like 303 is defined, and never like 302 is defined. For example: "If the 302 status code is received in response to