My primary use case for odrive is to backup my files to an encrypted location - sync is secondary. Encrypting includes encrypting the filenames, not just the data.
I’ve been using odrive1 with filename encryption with no problem (other than lots of sync activity that I don’t really want). I haven’t provided feedback because I don’t have any problems with it. It may be true that the majority of the feedback you are receiving makes it seem like data-only encryption is preferred, but I don’t think that is an accurate assumption. The majority of people don’t provide feedback unless they are not happy with the way something is working.
I would expect that only when you roll out odrive2 data-only encryption will you be getting feedback that “lots of folks” want filename encryption…
Why wouldn’t the first phase of odrive2 use the existing filename encryption from odrive1 if it already works? You could add data-only encryption as another option following that.
You had been promising backup in odrive1, now it looks like that is only part of odrive2 - but not with the same encryption capability as odrive1. As it now stands you provide all of the capability I want (backup and filename encryption) but you’ve split it across two different products and I can’t actually use it.