The way the 2.0 update was pushed out was more of an issue than the folder limit itself; if you're going to push an update out like that which is going to change functionality, need things to be reconfigured etc, then you need to give the user big, clear warnings about what they're going to do. When I inadvertently updated my phone, I had no clue that it was anything more than a regular point update. When it seems like you're trying to stealthily foist changes on people that them might not agree to if given the choice, that's a trust-breaker. And why act that way, unless we're now on the slippery slope of gradually degrading the free version and trying to push people on to the paid version*? * a paid version which is not at all an attractive proposition for me, I'm afraid; I could see a one-off purchase, but $40 per year basically for the odd bug-fix? I'm supplying my own power, storage and bandwidth. Nah, man. You want to charge cloud storage prices, give me a cloud-based Sync node with some cloudy features, so I can do the things that Sync currently can't do, like sending files to people without requiring them to install any software, or streaming media from the cloud without requiring any of my machines to be on. Right now $24/year for 100GB of Google Dive storage seems like a much better deal.