Dwolla never had native support for bitcoin transactions. We've always been used as a gateway between USD -> BTC by exchanges such as MtGox, BitInstant, etc.
This is still the case, and is still very much possible and active.
Paypal only lets you send in up to 250 rows, right? We've set that to 2,000 - and also uncap it for trusted users... At 250 records, the fee difference might not be much, but at 2,000 - it can quickly add up to a nice sizable sum, don't you agree?
No no, it was actually sincere. I think that the UK's financial ecosystem is far more advanced than ours in the US... Money transfers are faster, more secure, and there's more of a general sense of progress...
There are a few services like this out there, but they use the "old rails" (e.g Paypal, ACH, etc), and they charge fees per batch, as well as per transaction. So yes, there are similar things, but all of them are wildly more expensive...
I think @skeletonjelly's point is that the reverse engineering of ObjC reveals much of the original unobfuscated source coude, thus giving away proprietary data?
Well, the real point of what I was trying to say in the article was that Twitter had publicly stated that they're moving to an API oriented architecture - meaning that the web client is merely just another API client. That, coupled with the non-conforming-UX API key revoking acts recently, made me question the legitimacy of their statements...
You know, I carefully read Twitter TOS before writing this article, and there is absolutely no mention prohibiting the reverse engineering, or decompilation of their software.
Unlike others, Spotify for example, who explicitly prohibit such actions in their TOS...
Actually, they do. Maybe not legally, but practically, Twitter owes many of its users to a handful of successful API clients. You can't just "use" developers (or, companies) to build up your user-base, and then as soon as it gets convenient for you, just ditch 'em all together...
I actually just rolled out a new Dev portal at Dwolla. He I it out over at developers.dwolla.com. I tried to make it more of an integration portal, so that there's something for coders, but also for non tech people trying to figure out if Dwolla is right for them.
Mainly tho, I think that the 4sq model of being able to try out every method on the fly is super important to devs...