venison - sweet pickled rhubarb, charred jalapeño mayo, cilantro - $15
I want this.
next time you have to configure ssh keys and shit to work with heroku, dont forget to get the accounts plugin https://github.com/ddollar/heroku-accounts
This has to be seen to be believed
Solving a Rubik’s cube is hard enough. Solving it while juggling it is some Next Level Shit (tm)
Did you know that when you click on links in Twitter, a series of redirects happen before you end up on the page you requested? On twitter.com, the tweet might say cnn.com, but in fact that’s a ruse: the real URL in the tweet points to http://t.co, which is Twitter’s own URL shortener. That URL might even point to a bitly link, which ultimately points to the publisher. That’s two redirects right there. That might not seem like much but the pain is felt on a mobile device. Also consider that a site might want to redirect to a mobile-friendly version of its site and you are now looking at 3 or more full roundtrips on the network before you are even serving the content of the page. That’s a lot of wasted time.
What I propose is this: if I access Twitter via a mobile device, show me a timeline with shortened links already pointing to the mobile version of a site, if it exists. That way, Twitter can still count clicks, and the publisher serves the right version of the site right off the bat.
All Twitter needs to do is visit the link themselves under a mobile-browser user agent (Mozilla/…iPhone….), watch how it redirects, and then have the t.co link point to whatever URL it ultimately resolves to.
This would probably not be great for Bitly, as Twitter would effectively take them out of the transaction. It would probably put them out of business, but in this case I don’t feel especially sympathetic.
I want to share a piece of advice with you to start 2013: consider auditing all the apps you have authorized on Facebook and Twitter. I don’t want to cause unnecessary alarm, but it’s just something worth considering, and it takes two seconds. A little background:
Every time you sign up for a new website by hitting the “Sign Up With Facebook”/”Sign Up With Twitter” button, or every time you accept an invitation to try out a new app on Facebook, you are giving the app maker access to information from your profile, including your status updates, photos, likes, shared locations, etc. And long after you stop using that app, the app maker still has access to it. And what’s worrying is that you don’t know if they are continuing to access it.*
By removing/revoking access to the apps you don’t use, you can make sure that Random App Maker doesn’t have access to your tweets, status updates, etc, going-forward. And since we need to exercise increasing caution in what we share and with whom, it’s no bad thing to clean house periodically. Plus, it’s super easy. On Facebook, go here:
On Twitter, go here: https://twitter.com/settings/applications
* A while back Facebook said it would be changing this policy to short-lived access period, but I haven’t seen any mention of it lately, so I don’t know what the story is.