On Fri, Jun 29, 2012 at 6:14 PM, Mark Rejhon <[email protected]> wrote: > On Fri, Jun 29, 2012 at 1:08 PM, Kevin Smith <[email protected]> wrote: >> >> > You missed the message where a vendor told me they would put it in a >> > Privacy >> > preference setting, and have it off by default. (while still enabling >> > an >> > audio/video button by default) So this is a real issue! This >> > accessibility concern needs to be clarified. >> >> Have /what/ off by default? I strongly support /sending/ RTT being >> disabled by default (although we're not in the business of telling >> people how to craft their UX). By default hiding that someone is >> sending you RTT is just strange. I don't understand why someone would >> do this. You're right that I missed the message where this happened - >> which thread was it in? Some context might help here. > > > Are you confusing the word "off"? > -- "off" meaning "stop sending <rtt/>, stop displaying incoming <rtt/>" > (CORRECT) > *VERSUS* > -- "off" meaning stop advertising the existence of XEP-0301 according to > Section 5 (WRONG) > > The vendor was implying "off" meant "completely off", in > Settings/Preferences/Privacy means stops advertising XEP-0301 in Section 5. > We need to clarify section 5 to say that it is not acceptable to stop > advertising XEP-0301 if you are advertising the existence of other > interactive conversational modes (i.e. audio/video) ....
I don't think this has a place in the XEP - if a vendor really does want to make it possible to completely disable RTT for some reason, or to make it accessible via a plugin, or whatever it's not the place of the XEP to stop them. > An "off" feature SHOULD mean "stop sending <rtt/>, stop displaying incoming > <rtt/>" .... INSTEAD of stopping advertising support of RTT in Section 5... Is that really better? My client tells you that it's accepting RTT, you're busy sending me a huge message because that's how you write when you're using RTT, but my client isn't going to tell me that it's RTT. This seems less helpful than my client just announcing to you that it's not dealing with RTT and setting expectations appropriately. /K
