Yes, I have to say I see more cynicism in the choice of delivery dates than I did initially - they wanted to capture the New Years Resolutioner market so they basically shipped whatever was done on 30 Dec to make sure they did. Otherwise I guess they wouldn't really start to see a return on investment on nYNAB until this time next year, which could be desperate for a business the size of YNAB.
The migration of YNAB4 data appears to have been hit by massive performance problems, i.e. the sort of thing they presumably hoped to avoid by moving to a platform like Amazon. They will have beta tested this with a chosen few, I'm wondering if they failed to appreciate how large some budget files actually would be.
The lack of notification is just mad, isn't it? No email? WTF? Were they wanting to soft launch it in order to minimise this initial peak of new users, in which case why not do a properly phased introduction (particularly excluding their overseas markets given there is less functionality for us)?
Very odd and to be honest quite typically haphazard for YNAB, I mentioned in my original post the botched launch of YNAB 4. And that's fine for a relatively small company of nice people, which is what they appear to be. No way in hell do I trust bucketloads of financial data to a small company of nice people.
I'm not particularly wild about my YNAB 4 files in Dropbox being subject to the PATRIOT Act (as well as hacking) but I can reconcile that in a number of ways, not least the fact I have two factor authentication on my Dropbox account. (People have found ways of encrypting their Dropbox data as well). The other factor is that Dropbox contains gazillions of files that would be more interesting to a hacker, whereas all that there will be in the YNAB database is everyone's financial transactions. If I wanted to hack a Congressman's financial records to see if there's anything dodgy, yes I could do that via Dropbox but all I'd end up with a tiny text file that said something like this:
{
"deviceGUID": "XXXXXX-XXXX-XXX-XXXX-XXXXXXXXXX",
"budgetDataGUID": null,
"dataVersion": "4.2",
"formatVersion": null,
"startVersion": "A-25455,B-1731,C-332,D-1336,E-5115,F-59,G-326,H-2,I-3",
"endVersion": "A-25456,B-1731,C-332,D-1336,E-5115,F-59,G-326,H-2,I-3",
"shortDeviceId": "A",
"publishTime": "Tue Dec 29 15:08:12 GMT+0000 2015",
"items": [
{
"date": "2015-12-18",
"subTransactions": null,
"matchedTransactions": null,
"amount": -24.99,
"isTombstone": false,
"entityVersion": "A-25456",
"madeWithKnowledge": null,
"isResolvedConflict": false,
"source": null,
"memo": "1 X Skylanders Superchargers: Starter Pack (PS3)",
"cleared": "Uncleared",
"dateEnteredFromSchedule": null,
"checkNumber": null,
"flag": null,
"importedPayee": null,
"targetAccountId": null,
"transferTransactionId": null,
"categoryId": "A31",
"YNABID": null,
"FITID": null,
"payeeId": "XXXXXX-XXXX-XXXX-XXXX-XXXXXX",
"entityId": "XXXXXX-XXXX-XXXX-XXXX-XXXXXX",
"entityType": "transaction",
"accountId": "XXXXXX-XXXX-XXXX-XXXX-XXXXXX",
"parentTransactionIdIfMatched": null,
"accepted": true
}
]
}
(I've XXed out all the GUIDs, even though they don't mean anything outside my budget file!)
Now YNAB will make a much better target, with the ability to scoop up an awful lot of data very quickly. Not to mention without local replication, hold it all to ransom - for example by launching a DDOS attack and threatening not to end it til YNAB forks over a load of cash. (In fact someone on Twitter has just made the same point about Dropbox vs YNAB).
I don't even know if UK banks offer this kind of import facility, do they? I know that Xero can do it for some business bank accounts but for personal accounts I can't imagine it without two factor authentication on the other end. In any case, I can't see YNAB wanting to deal with multiple interfacing methods, unless OFX is a global standard?
Their security statement is here which leads also to the Heroku statement - it's hard to believe they've been naive enough to say 'just share the username and password with anyone who shares the budget' on top of this very robust commitment to security. And of course this is the problem - I think Heroku and Amazon know what they're doing (possibly except when it comes to the payment of UK taxes) but YNAB are batting out of their league with this stuff. One might note a similar feeling about MN during Jeffreygate.