4 ms·

> "why didn't we do this earlier?" Because it's invasive. The user consents to sending you information when they hit Send(explicit). They can remove any incor

> "why didn't we do this earlier?" Because it's invasive. The user consents to sending you information when they hit Send(explicit). They can remove any incorrect or unrelated information from the text box before they do so. Especially if they paste in to the text box and inadvertently paste the wrong thing(be that sensitive info or similar).

chrischen 8y ago
I use a chat service that has this feature on by default (for real-time chat customer support, not for general messaging), and never in the history of its usage has a person complained about it. For every 10,000 people that may not have an issue with it, 1 may have an issue about it, and with these numbers it's really up to that 1 person to guard their privacy better (disable JS, never step outside their house, etc) than to inconvenience 9,999 other people from the benefits. The experience is all in the context, and since this is only general behavior for customer service chats (where you're expected to send everything you type and the other end is simply trying to help resolve an issue), it's not really a realistic issue in terms of privacy. I agree that if facebook messenger started doing this and showed the other person what you are typing, this would be unexpected and potentially unwanted behavior, but the likelihood of unwanted behavior in a customer support context is extremely rare.
- sp0rk 8y ago
  > I use a chat service that has this feature on by default (for real-time chat customer support, not for general messaging), and never in the history of its usage has a person complained about it. How would most people know to complain about something they don't know is happening?
- craftyguy 8y ago
  > For every 10,000 people that may not have an issue with it, 1 may have an issue about it, How many of those 10k people even know this is happening? I suspect, given the other comments here and the fact that this article exists, that it's a very small number. Try informing all 10k people first, then count how many 'may not have an issue' with it.

chrischen 8y ago

I use a chat service that has this feature on by default (for real-time chat customer support, not for general messaging), and never in the history of its usage has a person complained about it. For every 10,000 people that may not have an issue with it, 1 may have an issue about it, and with these numbers it's really up to that 1 person to guard their privacy better (disable JS, never step outside their house, etc) than to inconvenience 9,999 other people from the benefits. The experience is all in the context, and since this is only general behavior for customer service chats (where you're expected to send everything you type and the other end is simply trying to help resolve an issue), it's not really a realistic issue in terms of privacy. I agree that if facebook messenger started doing this and showed the other person what you are typing, this would be unexpected and potentially unwanted behavior, but the likelihood of unwanted behavior in a customer support context is extremely rare.

sp0rk 8y ago
> I use a chat service that has this feature on by default (for real-time chat customer support, not for general messaging), and never in the history of its usage has a person complained about it. How would most people know to complain about something they don't know is happening?
craftyguy 8y ago
> For every 10,000 people that may not have an issue with it, 1 may have an issue about it, How many of those 10k people even know this is happening? I suspect, given the other comments here and the fact that this article exists, that it's a very small number. Try informing all 10k people first, then count how many 'may not have an issue' with it.