1,710 karma · joined November 23, 2015
[ my public key: https://keybase.io/marvinpinto; my proof: https://keybase.io/marvinpinto/sigs/MoNfexCD-_Gl-ahhLO9iLcSdBpgOe4NKbRWcKKT_K-M ]
[1]: https://pouchdb.com/2015/05/18/we-have-a-problem-with-promis...
Their web interface has just.. not cut it for me. Too resource intensive and not enough control over how/when I am interrupted. This was why I gravitated to the IRC gateway in the first place. Oh well.
I think it might be because you have third-party cookies disabled [1], and the Google Auth client uses an iframe with cookies to do its thing. I replicated it myself by disabling third-party cookies and the results were similar to what you described.
I'll look into what I can do about this on my end tomorrow. Thank you again for your time!
If you would still like to give it another shot I would appreciate it :)
Two-way messaging and call proxying is likely the next big features we'll be rolling out.
We went with the Twilio Connect route initially as a low-risk approach to see if there's an appetite for a something like this. Sadly it has not been a great user experience and we're definitely going to reconsider it (Twilio Connect).
As you might have guessed, we haven't actually decided on pricing yet but I wanted to put something on that page so that people can get a feel for how much it would cost them.
And yeah, the system we were using for auth (Cognito) did not at that time have an adequate 2FA solution, which was why we went with Google. Now that they do, we'll likely use that which would allow people to also signup with a username/password (in addition to Google, etc).
This runs locally and it has the ability to read gpg-encrypted credentials (using gpg-agent).
This of course gets complicated with TOTP tokens but I'll cross that bridge when needed :)
I also tried to make the plugin system as friendly as I could so people for people to add their own financial instutions. I'm optimistic someone will contribute a plugin one day :)
[0]: https://chrome.google.com/webstore/detail/chrome-capture/gga...
This in itself has saved me so much time that I can deal with manually editing the occassional duplicate entry (internal account transfers). I also keep all my ledger data in git so it's very easy to see what has changed, etc.
Have you looked at the reckon gem[0] for auto-classification? That is basically what this program uses.
It does not use any public or private banking APIs.
Hope that helps!
To work around this I tried to make it as developer-friendly as I could so we'll see!
[1]: https://github.com/xenolf/lego
[2]: https://disjoint.ca/til/2016/03/26/lets-encrypt-tls-certific...