On Wed Mar 2 13:22:56 2011, Gregg Vanderheiden wrote:
1 - If you want to call someone - you don't get to pick the
technology that they have. So it only works if it is pretty much
standard on mosts devices.
This is true of any technology, not just delay codes in RTT/XMPP.
2 - Many people only know how to use the default apps on a device.
This is true of any technology, not just delay codes in RTT/XMPP.
3 - For phones etc - it may not be possible to install different
software
This is true of - you're getting the picture, right?
4 - Often what you can use is determined by your company. You get
what they give you or offer and cannot use alternate devices or
software.
For these and similar reasons - it is important that such
capabilities be supported. Users can turn them on or not but they
need to be able to.
No, I'm afraid we cannot simply mandate featuresets because we think
they're important, we can only mandate protocol items required for
interoperability.
Otherwise I'd be very happy to mandate PEP, security labels, and
countless other things I happen to think are really useful.
Now, if there's a market need, people will use them, and if there's a
regulatory requirement, then regulators will similarly mandate.
But the XSF is neither a regulator nor the arbiter or a market, and
shouldn't attempt to be so.
Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
