4 ms·
Coming from the man behind the FSD “beta”, this is par for the course; but I still find it questionable to turn this sort of feature on in prod (for paying cust
by cmckn 3y ago
Coming from the man behind the FSD “beta”, this is par for the course; but I still find it questionable to turn this sort of feature on in prod (for paying customers, no less) while simultaneously admitting it’s not trustworthy.
- robertlagrant 3y agoPerhaps it depends on what is meant by untrustworthy, but I don't see how it's a downgrade for users. Or are your concerns just PR-related?
- mjg59 3y agoIt's an improvement over the status-quo. But given what was communicated before the feature was launched, it's very easy to believe that users might believe that the expectations around privacy and security are stronger than they actually are. Ideally you don't need to put any meaningful trust in the service provider, but in this case you do.
- robertlagrant 3y agoWell, I think if comms have been over-zealous then a correction is appropriate. But either way, this just seems now commentary on their PR chops, rather than anything fundamental about their technical implementation, so I'll colour myself unworried again.
- diebeforei485 3y agoIt's better than the current product where it's readable in plaintext to Twitter employees, and to some outside contractors as well. For those who already use Twitter DM's (which is a lot of people), this is an improvement.