On Thu, Jun 28, 2012 at 12:45 PM, Mark Rejhon <[email protected]> wrote: > On Thu, Jun 28, 2012 at 12:22 AM, Kurt Zeilenga <[email protected]> > wrote: >> >> Suddenly, we now have the potential discrimination issue of software >> permitting audio initations by default, but not being able to do RTT >> initations by default. This is the discriminatory situation we want to >> avoid. :-) >> >> >> I guess bandwidth-challedged XMPP networks should be fair and, if they >> want to block one real-tine conversation method, block them all. > > > This came up as a potential issue. > One software vendor I contacted, suggested that XEP-0301 is a privacy issue, > and implied if added, it would need to be enabled via a user privacy > preference. (Note: That vendor has audio/video enabled by default in their > XMPP). > It's a real issue that I am concerned about -- vendors implementing RTT but > then not advertising RTT in clients that already has audio/video.
Sending RTT without user intervention would be fairly horrible. That's no reason not to advertise support for it, then other clients can send you RTT and your client can prompt "Hey, they're sending RTT, would you like to reply with RTT [Always, Never, for now, not now]?" /K
