[webteam] XML files for public transports

[Robert Martinez]

Sander Devrieze wrote:
> To solve this issue of stupid people not understanding why XMPP is the
> most interoperable system out there, we need *extremely* good and
> userfriendly basic interoperability to closed chat systems using
> transports. With basic I don't mean "lots of features", instead I mean
> "reliable support for key instant messaging features like messages and
> presence".
>
>   
Do you believe in reliability here? letting people use random transport 
servers?
My experience tells me that the user experience is quite dissapointing 
(maybe this is not the case for everyone).
It completely depends on the server admins how stable the service is.
And more fatal: if a server is "known" to work well it will soon be  
overcrowded and instable :P

>>  Since the setup of a transport means giving away credentials about your
>> account, you might not want to give those away to a random server so
>> quickly. You would need to explain users where this data is going to be
>> stored, this will be confusing.
>>     
>
> I don't think most people care. Especially, as the transports in this
> list are verified by the jabber.org  procedures!! Anyway, it is up to
> the XMPP client how this should be implemented: instead of randomly
> selecting a public transport themselves, they also can tease the user
> with the choice to choose a server from a list.
>   
I care. Switching to jabber should not imply to spill around your 
credentials everywhere. We're supposed to make things better :).

Transports as a feature are nice to have, and clearly you _have_ to give 
way your credentials away.
But doing it quickly without letting the user know of the implications 
isn't a perfect solution.
If you want to circumvent that you need to explain this _clearly_ (most 
people don't understand the way transports work immediately).

>>  In the end I thing the benefit will not outweigh the downside of the
>> effort.
>>     
>
> I think all this can be automated, right?
>
>   
I don't consider the transports as a true, reliable solution (not with 
those instable small servers out there).
So I also don't see the benefit of scripting stuff that won't be a 
solution in the end.

Honestly, I think this is really a pitty. I like the idea of solving the 
hassle of setting up transports. And the XML file seems like a nice way 
to include the community.

But, say, do you rally have a good conscience sending people with lots 
of "proprietary buddies" in their list to such a scripted client 
solution? (maybe I'm just a exeption to experience bad quality of service?)