"so what is your twitter username?"
So we had a very kewl twitter meetup last night. The numbers seem to be doubling, and following the twitter growth curve. There was a projector showing the tweets from people there which was fun; "What is your username?" is the default opening line (which actually is a better leveller than your normal "So what do you do?" - which you get at (web2'n'all) networking events.
Following my selfish folksonomy meets structured data in verticals on the edge, I cant help but continue my fandom of Wesabe who covered by Mashable have "provided an API for all the bank accounts they support, meaning you can take your banking data wherever you like, mash it up, automatically download it to Excel, aggregate it on financial sites and the rest. It’s not limited to the US either: Wesabe supports banks and credit card companies in 30 countries. Meanwhile, they claim that the REST API is as secure - or even more secure - than what banks already offer."
From Wesabe's blog, they really are impressive : "We believe that the best way to get to this goal is by putting that powerful data in the hands of every consumer who wants it. If you’ve been using Excel for years and you have your reports just the way you like them, great: the Wesabe API supports Excel downloads and can be called from within Excel using VBScript. If you’ve developed your own tools already, great: you can use our API to automate download of your data to your own system, and take advantage of our automation work and the community editing the people on Wesabe provide. Or, if you use the Wesabe site all the time but really want a report we don’t yet provide, this is a way to get that for yourself (or, we hope from other developers will to share their work). As the database grows, our ability to make better and better recommendations for great values and financial strategies does, too — no matter what tools people are using. In a way, it’s almost inconceivable that a bank would open an API. Banks and credit cards make so much of their money from consumers who are bad at managing their own finances. Why make it easy for people to see the problems they can overcome? That’s why we believe Wesabe has a role to play, advocating for consumers and their finances directly, and that’s why we believe that opening an API is different in our industry than others. We’re freeing a set of data that otherwise might have remained locked away."
As I'm about to get my new engineering team, the acronym API is getting pretty close to the top of priorities; Build it and others can Build it so they come. As Brad Feld aptly notes : "This is not a new idea nor am I suggesting it is. But it’s a phenomenon that has become key to what’s going on around the web today. Some people – like the fine folks at the Programmable Web – are even cataloging this. Remember the phrase “information wants to be free.” Your computer programs do also, and an API is the way to help them."
Following my selfish folksonomy meets structured data in verticals on the edge, I cant help but continue my fandom of Wesabe who covered by Mashable have "provided an API for all the bank accounts they support, meaning you can take your banking data wherever you like, mash it up, automatically download it to Excel, aggregate it on financial sites and the rest. It’s not limited to the US either: Wesabe supports banks and credit card companies in 30 countries. Meanwhile, they claim that the REST API is as secure - or even more secure - than what banks already offer."
From Wesabe's blog, they really are impressive : "We believe that the best way to get to this goal is by putting that powerful data in the hands of every consumer who wants it. If you’ve been using Excel for years and you have your reports just the way you like them, great: the Wesabe API supports Excel downloads and can be called from within Excel using VBScript. If you’ve developed your own tools already, great: you can use our API to automate download of your data to your own system, and take advantage of our automation work and the community editing the people on Wesabe provide. Or, if you use the Wesabe site all the time but really want a report we don’t yet provide, this is a way to get that for yourself (or, we hope from other developers will to share their work). As the database grows, our ability to make better and better recommendations for great values and financial strategies does, too — no matter what tools people are using. In a way, it’s almost inconceivable that a bank would open an API. Banks and credit cards make so much of their money from consumers who are bad at managing their own finances. Why make it easy for people to see the problems they can overcome? That’s why we believe Wesabe has a role to play, advocating for consumers and their finances directly, and that’s why we believe that opening an API is different in our industry than others. We’re freeing a set of data that otherwise might have remained locked away."
As I'm about to get my new engineering team, the acronym API is getting pretty close to the top of priorities; Build it and others can Build it so they come. As Brad Feld aptly notes : "This is not a new idea nor am I suggesting it is. But it’s a phenomenon that has become key to what’s going on around the web today. Some people – like the fine folks at the Programmable Web – are even cataloging this. Remember the phrase “information wants to be free.” Your computer programs do also, and an API is the way to help them."
<< Home