fun with Capper and OFX financial transaction fetching

Dan Connolly <[email protected]> Sat, 2 Jan 2016 17:39:38 -0600
Newsgroups gmane.comp.capabilities.general
Message-ID <CAD2Yivb5Dk6zWiRORNYdgABvmAqWtdpr9QH=mny6qBBDjoHifw@mail.gmail.com>
Capper is kinda fun to work with. I wish I had seen it sooner! I hope
to see more of this sort of stuff: investment in ocap style on the JS
platform.

The documentation works just fine for starting up (though the config
should probably default to localhost). To put together a non-trivial
app, I had to puzzle over the source of the examples. But it wasn't
too bad.

The main disappointment is that I don't get to use normal closure
style objects. I have to mutate this context.state thing. Oh well.

The good news is I get to use all the npm goodies such as banking (OFX).

I was able to put together Account objects that fetch 60 days of CC
transactions .

https://bitbucket.org/DanC/finquick/src/capper/take2js/README.md
9e09e00

Now I'd like to figure out an alternative to this step in my docs:

  WARNING: This will store your credentials in clear-text in capper.db.

I'm noodling on how to use TOTP or some such to avoid storing
credentials in clear-text.

Then I'm thinking about deployment on sandstorm.

A wish: I'd love to see an authority-neutral module loader a la
makeSimpleAMDLoader.js.

https://github.com/tvcutsem/es-lab/blob/master/src/ses/makeSimpleAMDLoader.js

Then I could start to refactor stuff like http libraries (superagent)
and the banking OFX stuff to use it.

-- 
Dan Connolly
http://www.madmode.com/