Jonathan Wight

@schwa Whenever sync fails though they catch the blame. They got sick of that and the desire to control the whole thing overwhelmed them.

@ntakayama @schwa not being able to answer “why isn’t it working” is super frustrating.

@tapbot_paul @ntakayama DayOne syncing was apparently down for a day earlier this week…

@schwa @tapbot_paul My motto as an indie developer: never run my own servers. It limited me in many ways but I got to sleep soundly.

@ntakayama @tapbot_paul How are you sleeping now?

@schwa @tapbot_paul Like a baby

@schwa Can be dangerous to build a business on third party platforms. Who do you trust? Dropbox Datastore? Gone. Parse? Gone.

@schwa Until late last year, Dropbox API had no way to prevent dupes from conflicts. All we could do to change that was to beg.

@schwa CloudKit seems pretty good. But remember iCloud v1? Steaming pile of crap. Our trust in Apple to sync was... low.

@schwa I think that today Dropbox and iCloud are both in pretty good shape. But these decisions were made long before they were.

@schwa I think @1Password has handled this better than anyone. They haven't dropped any sync options, but have added their own for teams.

@schwa BTW, I left Day One six months ago, so I don’t speak for the company on any of this.

@bdolman I understand there are good technical reasons for the switch but users have great reasons to dislike this decision.

DayOne or TextExpander content is by nature sensitive. But sure roll your own sync servers, put it behind https and call it “secure”.

@schwa What makes you think Dropbox or iCloud have a strong security model?