Interesting, but:
There are two kinds of users in this scenario. Those who don't care (99%) and those who do.
If you count yourself among the latter group, as I do, then it's always solid advice to choose actions which clarify your intentions.
In this case:
- don't use iCloud
- don't use iCloud sync for the app you use for private data
- do explicitly choose to save the file locally
- don't enable new features like Continuity that clearly change the file
persistence and availability model without considering your old patterns
The author is rightly sore that his bits got pushed to Apple due to his oversight. He's wrong to place the blame fully on Apple, but it's hard to be fair when you're angry. And I'm glad he wrote it up because it should encourage people to think carefully about where and to whom they trust their data. Though most people I know sync their private data to Dropbox, Ffs, so...thinking !=
thinking, I guess.
My secure notes strategy is vim with encrypted files on an encrypted partition. It could still leak, and I'd be angry, but there are at least three vendors involved that would have to alter their products behaviours before I was hugely surprised. TextEdit on HFS+ on OSX with iCloud enabled is just one vendor, who can't always cater to my 1% of 1% expectations.