On Feb 3, 2015 8:49 AM, "Siva Narendra" <siva@tyfone.com> wrote:
>
> Is payments also an overkill?
>
Failing to consider privacy as a valid concern or declaring users privacy
irrelevant (as it seems Rigo is doing) will always cause your use case to
be called overkill.
Put differently, there is no use case that is valuable enough that should
cause us to be willing to suspend the priority of constituencies and ignore
the very real privacy and security risks users face. And before anyone
slips into some trite argument that "Not implementing X is not putting
users first" - no, privacy and security is the one universal that trumps
all.
So it is disingenuous and counterproductive to frame the discussion as "X
not being a valid use case" or "Y being overkill". The argument remains
unchanged for the past three years - any solution that does not preserve
users privacy and security is unacceptable, full stop.
If you provide and explore a solution that preserves these two aspects -
and this thread has many such concrete examples of ways in which the
proposals to date have failed miserably at doing so - then it may be worth
discussing. But *no* use case is worth trumping these concerns, and it is
not the *use case* being rejected, but the "solutions" being put forth.