<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: New Feature: the Wesabe Automatic Uploader</title>
	<atom:link href="http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/</link>
	<description>The Wesabe blog</description>
	<lastBuildDate>Thu, 14 Jan 2010 18:37:20 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: New Feature: the new Tips tab &#8212; the Wesabe Value Engine &#171; Wesabe: Your Money. Your Community.</title>
		<link>http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4710</link>
		<dc:creator>New Feature: the new Tips tab &#8212; the Wesabe Value Engine &#171; Wesabe: Your Money. Your Community.</dc:creator>
		<pubDate>Wed, 18 Nov 2009 04:02:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4710</guid>
		<description>[...] Your Money. Your Community. The Wesabe blog      &#171; New Feature: the Wesabe Automatic&#160;Uploader News about Jason and&#160;Wesabe [...]</description>
		<content:encoded><![CDATA[<p>[...] Your Money. Your Community. The Wesabe blog      &laquo; New Feature: the Wesabe Automatic&nbsp;Uploader News about Jason and&nbsp;Wesabe [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael G</title>
		<link>http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4324</link>
		<dc:creator>Michael G</dc:creator>
		<pubDate>Wed, 31 Dec 2008 18:55:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4324</guid>
		<description>How about something for us excel lovers? Personally, I&#039;d like to be able to download a csv file from my bank, quickly tag and then upload to wesabe. A few good reasons why - I need to do this anyway to keep my taxes organized. And it would also alleviate any lingering security concerns from fellow paranoids since wesabe would only have transactions, not account info.....</description>
		<content:encoded><![CDATA[<p>How about something for us excel lovers? Personally, I&#8217;d like to be able to download a csv file from my bank, quickly tag and then upload to wesabe. A few good reasons why &#8211; I need to do this anyway to keep my taxes organized. And it would also alleviate any lingering security concerns from fellow paranoids since wesabe would only have transactions, not account info&#8230;..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Ellis</title>
		<link>http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4323</link>
		<dc:creator>Matt Ellis</dc:creator>
		<pubDate>Mon, 28 Apr 2008 14:08:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4323</guid>
		<description>Ah yes. I&#039;ve just watched the video, and re-read the OAuth specs. It had never occurred to me to simply save the returned token and secret, and reuse them later, server side. It would require a long lived token (unusual for a bank - why I hadn&#039;t thought of it!), but that can be mitigated - if we know the consumer key, we can limit access to only those APIs that make sense for that consumer.

That said, we&#039;d still want to expire the token after, say, a month. And that would require the user to re-authenticate.

Thanks
Matt</description>
		<content:encoded><![CDATA[<p>Ah yes. I&#8217;ve just watched the video, and re-read the OAuth specs. It had never occurred to me to simply save the returned token and secret, and reuse them later, server side. It would require a long lived token (unusual for a bank &#8211; why I hadn&#8217;t thought of it!), but that can be mitigated &#8211; if we know the consumer key, we can limit access to only those APIs that make sense for that consumer.</p>
<p>That said, we&#8217;d still want to expire the token after, say, a month. And that would require the user to re-authenticate.</p>
<p>Thanks<br />
Matt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Hedlund</title>
		<link>http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4322</link>
		<dc:creator>Marc Hedlund</dc:creator>
		<pubDate>Sat, 26 Apr 2008 08:07:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4322</guid>
		<description>Hi, Matt,

We actually already use something like OAuth (specifically, Google&#039;s AuthSub) for our Google Spreadsheet Export feature.  You can see a video of how it works here:

http://www.youtube.com/watch?v=h2cV-e8nDSE

I think that, were banks to support OAuth or something similar, a very similar process would work well.</description>
		<content:encoded><![CDATA[<p>Hi, Matt,</p>
<p>We actually already use something like OAuth (specifically, Google&#8217;s AuthSub) for our Google Spreadsheet Export feature.  You can see a video of how it works here:</p>
<p><span style="text-align:center; display: block;"><a href="http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/"><img src="http://img.youtube.com/vi/h2cV-e8nDSE/2.jpg" alt="" /></a></span></p>
<p>I think that, were banks to support OAuth or something similar, a very similar process would work well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Ellis</title>
		<link>http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4321</link>
		<dc:creator>Matt Ellis</dc:creator>
		<pubDate>Fri, 25 Apr 2008 08:00:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4321</guid>
		<description>Hi folks. Interesting comments. Just a quick question about OAuth, though. As I understand it, OAuth gives delegated login via browser redirection. In other words, the customer needs to be present to enter their credentials at the authenticating site (the bank). How do you imagine this to work with the automatic uploader?

Cheers
Matt</description>
		<content:encoded><![CDATA[<p>Hi folks. Interesting comments. Just a quick question about OAuth, though. As I understand it, OAuth gives delegated login via browser redirection. In other words, the customer needs to be present to enter their credentials at the authenticating site (the bank). How do you imagine this to work with the automatic uploader?</p>
<p>Cheers<br />
Matt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Hedlund</title>
		<link>http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4320</link>
		<dc:creator>Marc Hedlund</dc:creator>
		<pubDate>Thu, 24 Apr 2008 23:23:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4320</guid>
		<description>Hey, Ade,

We&#039;ve been going from the most-used banks down, and so far we haven&#039;t reached UK banks, so no.  If you want automated upload from a UK bank, I&#039;d highly recommend our Firefox extension for now:

https://www.wesabe.com/page/firefox

You can use it to record a download once and play it back every six hours from then on.  It doesn&#039;t work with every bank, but it does work with nearly every one, and we have many UK users happy with it.

We will definitely get to automating UK banks -- not sure when, but it&#039;s our third-biggest constituency (after US and Canada), so it&#039;s sure to happen.</description>
		<content:encoded><![CDATA[<p>Hey, Ade,</p>
<p>We&#8217;ve been going from the most-used banks down, and so far we haven&#8217;t reached UK banks, so no.  If you want automated upload from a UK bank, I&#8217;d highly recommend our Firefox extension for now:</p>
<p><a href="https://www.wesabe.com/page/firefox" rel="nofollow">https://www.wesabe.com/page/firefox</a></p>
<p>You can use it to record a download once and play it back every six hours from then on.  It doesn&#8217;t work with every bank, but it does work with nearly every one, and we have many UK users happy with it.</p>
<p>We will definitely get to automating UK banks &#8212; not sure when, but it&#8217;s our third-biggest constituency (after US and Canada), so it&#8217;s sure to happen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ade</title>
		<link>http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4319</link>
		<dc:creator>Ade</dc:creator>
		<pubDate>Thu, 24 Apr 2008 22:53:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4319</guid>
		<description>Hi Marc,

Are ANY UK banks serviced by way of the new Auto Uploader?  If so, which?  If not, why not?

I know the only bank listed in the UK version of M$ Money is Nationwide.  Is this also the case for Wesabe?</description>
		<content:encoded><![CDATA[<p>Hi Marc,</p>
<p>Are ANY UK banks serviced by way of the new Auto Uploader?  If so, which?  If not, why not?</p>
<p>I know the only bank listed in the UK version of M$ Money is Nationwide.  Is this also the case for Wesabe?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Messina</title>
		<link>http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4318</link>
		<dc:creator>Chris Messina</dc:creator>
		<pubDate>Thu, 24 Apr 2008 21:32:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4318</guid>
		<description>Thanks Marc -- I agree that convenience is key. I also figured that it was only a matter of time before you started storing user credentials on your end -- with competition from Mint (who dispensed with the whole password problem by accepting any credentials whatsoever!) you have to keep up with that kind of straightforwardness even if teaches people the wrong behavior. The fact that the industry hasn&#039;t sorted this out yet is a huge opportunity, and I&#039;m happy to hear that you&#039;re continuing to promote OAuth.

I was thrilled to have your participation in the initial work on the OAuth spec and would love to support your work with banks and financial institutions however I can. It really is better for everyone to move in this direction; with choice comes competition, and with competition comes improved service and motivation to serve better. That&#039;s something that I think needs to be considered when putting the idea of data interop and portability into perspective.</description>
		<content:encoded><![CDATA[<p>Thanks Marc &#8212; I agree that convenience is key. I also figured that it was only a matter of time before you started storing user credentials on your end &#8212; with competition from Mint (who dispensed with the whole password problem by accepting any credentials whatsoever!) you have to keep up with that kind of straightforwardness even if teaches people the wrong behavior. The fact that the industry hasn&#8217;t sorted this out yet is a huge opportunity, and I&#8217;m happy to hear that you&#8217;re continuing to promote OAuth.</p>
<p>I was thrilled to have your participation in the initial work on the OAuth spec and would love to support your work with banks and financial institutions however I can. It really is better for everyone to move in this direction; with choice comes competition, and with competition comes improved service and motivation to serve better. That&#8217;s something that I think needs to be considered when putting the idea of data interop and portability into perspective.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Hedlund</title>
		<link>http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4317</link>
		<dc:creator>Marc Hedlund</dc:creator>
		<pubDate>Thu, 24 Apr 2008 20:42:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4317</guid>
		<description>Hey, all,

I definitely agree that the general practice of sharing passwords between services is not the right model for users.  That&#039;s why we offered our uploaders in the first place, and that&#039;s why we&#039;re committed to continuing support for them.  I also would say that the comment from travis above is very representative of what we hear from people -- that they get more value from Wesabe when the process is as easy as possible.  We don&#039;t want anyone to feel that they have to compromise ease of use to use our site to manage their money -- the whole point is to make things easier all around.  So for the users who want auto uploading, I think this feature is a huge benefit.

Chris, thanks much for the comment.  As you know (but others might not), we participated in OAuth&#039;s development and we completely agree this is the right model.  I haven&#039;t been very public about this, but I&#039;ve been pitching OAuth to all of the biggest banks in the US, with the message that it is better for them and their customers.  I&#039;ve gotten very surprisingly positive responses all around.  I think at first many banks saw companies like Yodlee as a threat, and tried to lock them out, but more recently, what we see is banks responding positively to the work we&#039;re doing.  I don&#039;t know what will come of my efforts to pitch OAuth, but I&#039;ll certainly keep trying.</description>
		<content:encoded><![CDATA[<p>Hey, all,</p>
<p>I definitely agree that the general practice of sharing passwords between services is not the right model for users.  That&#8217;s why we offered our uploaders in the first place, and that&#8217;s why we&#8217;re committed to continuing support for them.  I also would say that the comment from travis above is very representative of what we hear from people &#8212; that they get more value from Wesabe when the process is as easy as possible.  We don&#8217;t want anyone to feel that they have to compromise ease of use to use our site to manage their money &#8212; the whole point is to make things easier all around.  So for the users who want auto uploading, I think this feature is a huge benefit.</p>
<p>Chris, thanks much for the comment.  As you know (but others might not), we participated in OAuth&#8217;s development and we completely agree this is the right model.  I haven&#8217;t been very public about this, but I&#8217;ve been pitching OAuth to all of the biggest banks in the US, with the message that it is better for them and their customers.  I&#8217;ve gotten very surprisingly positive responses all around.  I think at first many banks saw companies like Yodlee as a threat, and tried to lock them out, but more recently, what we see is banks responding positively to the work we&#8217;re doing.  I don&#8217;t know what will come of my efforts to pitch OAuth, but I&#8217;ll certainly keep trying.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Messina</title>
		<link>http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4316</link>
		<dc:creator>Chris Messina</dc:creator>
		<pubDate>Thu, 24 Apr 2008 20:36:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wesabe.com/2008/04/23/new-feature-the-wesabe-automatic-uploader/#comment-4316</guid>
		<description>This seems the ideal use case for OAuth between Wesabe and third parties... I bet banks probably haven&#039;t heard much about OAuth, but have you guys done any work to talk these companies about moving to delegated token-based authorization to avoid the need to use, as you pointed out, your actual bank credentials when performing such transactions?</description>
		<content:encoded><![CDATA[<p>This seems the ideal use case for OAuth between Wesabe and third parties&#8230; I bet banks probably haven&#8217;t heard much about OAuth, but have you guys done any work to talk these companies about moving to delegated token-based authorization to avoid the need to use, as you pointed out, your actual bank credentials when performing such transactions?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
