20,431 karma · joined March 11, 2008
Runscope (Co-founder, acquired 2017)
Twilio (first Developer Evangelist)
IFTTT
Xamarin
twitter.com/johnsheehanjohnsheehan at gmail
And you can follow @hurlit for updates
If you have any other feedback items, feel free to post them here or on https://github.com/twilio/hurl and we'll take a look at them. Pull requests are even better.
If you have a phone number you want to use to make calls from in a country we don't offer local numbers, you can verify it to use as a caller ID then call to any of our supported countries[3].
[0] http://www.twilio.com/CA/pricing [1] http://www.twilio.com/eu-beta-signup [2] http://www.twilio.com/faq/international [3] http://www.twilio.com/pricing/international-calling-rates
As hackers we're idealistic about how things work, expecting the world to follow logical patterns. But trust me, the press does not work remotely close to how one would hope. If you cannot stomach that, outsource it.
For TechCrunch, don't let them set the embargo time. Set one yourself, offer it to them as an exclusive. If they pass it up, move on. If they don't run it at the time you set, have a back up plan in place. TC will not make or break you. Do not allow yourself to be at their mercy. They have way more experience than you do. Act like you belong and control your own destiny.
Now to be a Debbie Downer, if you have VS installed, this addon is pretty good http://visualstudiogallery.msdn.microsoft.com/0855e23e-4c4c-...
For mobile you can embed the key and secret, because they only work in combination with someone authenticating their account to use your app https://www.dropbox.com/developers/start/authentication#ios
- It's too low level for quick stuff
- It handles HTTP basic auth wrong
- It throws an exception, AN EXCEPTION, for any response that isn't 2xx
- Async is an ugly mess
- In love with streams
- Horribly inconsistent across framework profiles
- ServicePointManager.Expect100Continue
- Inconsistent header handling and restrictions
- Terrible cookie APIThe new System.Net.Http.HttpClient in .NET 4.5 is closer to Requests and not entirely bad, if a little rigid.