suckaplease

RunTitle | Austin, TX | Full Stack Dev http://www.runtitle.com

We're building a data business (high margins), with large barriers to entry, are well-capitialized and have a first-mover advantage.

It's not sexy whatsoever by SV standards (consumer/mobile/food delivery?!), but it is a credible challenge to an industry that has not changed since its inception in the 1890s, and empowers one of the largest sectors of the US economy (7.3% of US GDP).

If you are interested in changing how the oil & gas industry acquires the data they require to operate in the United States, let us know: dev@runtitle.com

Django/Rails, Elasticsearch, AWS

That's a pretty slick way to implement the principle of least privilege in your app. Thanks for sharing.

Apple Thunderbolt!

I faced a similar dilema just over a year ago and made a similar decision. I've not regretted it one bit. It's amazing how much of the fear melts away instantly when you commit to something and realize that most of your limits are self imposed.

Great post, thanks.

They wouldn't fix a dead pixel on my retina MBP even though it went out just 3 months after I purchased it!

Wow, I'm always excited to see Rubyists promoting things being explicit in code. That's my primary gripe with Ruby projects, too much magic fairy dust and freebies that generates complexity. I'll keep this tip in mind when I play around w/ Rail/Grape next time.

1) The social auth tool we're using only allows you to have one set of permissions, so we're using the default set for our overall application. If you see my earlier comment I did update it to be a little less ambitious on the permissions.

2) The list of likes comes directly from FB

3) There is an endpoint provided by the Facebook Open Graph to delete a like. However, you have to be whitelisted by FB in order to call that endpoint.

4) Yeah, the thought was that you'd come here to unlike pages. If you made a mistake in unliking a page that you want to continue supporting you can go back there on FB and re-like it. The reason we removed the button after the action is that it's crazy confusing to explain to someone how to unlike a page using the default FB like implementation (the only implementation) and I'm sure that's by design. If the button stuck around after the action, I'm sure that there would be a lot of unintended re-likes.

Thanks, we're trying! Our goal is to help consumers voice their complaints to large companies (that aren't always listening too well). Please give us more feedback!

Thanks!

Out login system only supports one set of permissions and we're using the default set for our primary application.

However, I hear what you're saying and I'm deploying a reduced set now.

Thanks!

Thanks for doing this. We should identify the other companies that have an opt-out clause. I hate the fact that we have to sign our rights away just to use the best tools that are out there.

What happened to the open-web??

It must be back up, it works for me.

I think you have to actually cancel your account in order to not have your content sold out from under you.