hey all, author of the previous post (<a href="https://news.ycombinator.com/item?id=22595782" rel="nofollow">https://news.ycombinator.com/item?id=22595782</a>) here, and I'm happy to answer any questions about the system! I think the author isaac is here too.
Interesting, I learned this technique of having a third, synchronization intermediary with offlineimap and this helpful blog post: <a href="http://blog.ezyang.com/2012/08/how-offlineimap-works/" rel="nofollow">http://blog.ezyang.com/2012/08/how-offlineimap-works/</a>
> To cover this layer of our codebase, we also run Trinity in a “native” mode, targeting the platform’s actual filesystem. However, running against the native filesystem incurs a huge performance penalty (roughly 10x), which in turn means Trinity Native can’t test as many different seeds.<p>What platforms do you test in “native” mode? What hardware backs it?
I'm sure Dropbox is first-class behind the scenes, but the desktop app has become simply awful with time, so that I almost feel sorry for them and embarrassed towards other people when I use Dropbox.
I find the capitalization of the title here on HN to be rather misleading.<p>I thought Dropbox was actually testing Sync (<a href="https://www.sync.com/" rel="nofollow">https://www.sync.com/</a>) in-house and doing a public comparison.