Fair enough .
In that case, however, it would be important to debate which files to encrypt (an when – is it optional?). I use simple, anonymous (no user ids or anything like that) analytics for my plugins and have already gotten concerned reactions by users, but could always calm users by stating how anonymous my analytics are and that they can, of course, check my code to confirm that.
If files are encrypted, no one would know if and – more importantly – how plugins handle your data. With the target group – designers – often working under NDAs and therefore rightfully concerned about data getting submitted to an external party and in a time when – thankfully – there are users concerned with privacy, obscuring plugin code seems like a bad approach that could lower trust into plugins severely to me.
The only way to enable both sides of this would be to make this encryption optional and show a kind of “warning” about plugins using encryption. As a user, I could understand the reasoning for using this in a paid plugin from a known source (where it wouldn’t affect my trust), but I could “stay away” from free plugins (or other plugins where it wouldn’t be necessary or where I don’t trust the developer) using encryption, leaving me to guess what this plugin does to my data.
The thing is that it is – of course – sometimes necessary to use such systems, but I don’t think that this should be encouraged. For cases where it’s necessary, there of course isn’t another option (and for those cases, I’ve voted for this request). I do not think, however, that this should get encouraged in other cases (as I do – very much – believe transparency often outweighs security in these questions)…
PS: Please don’t see this as me saying I don’t think something like this should exist (I’ve voted for it, after all). I do, however, believe that it’s a question where it’s important to discuss the issue to find the best, or in this case, least bad solution for a problem where there’s no right or wrong.