Tijl Houtbeckers wrote:
This simply is one thing where "we", the Jabber community, have not
done much yet (the lack of need for it, being one of the reasons
perhaps). Just days ago we were still talking about how it's not clear
right now how TLS/SASL/Dailback should work together. Google apperently
thinks TLS is very important, they'll definatly want *some* form
certificate (so SASL is a must) to prevent an army of zombie machines
to start flooding them with SPIM, and if they want to keep it as open
as you seem to want, they'll definatly need dailback.
Since this was all "top secret" till a few hours ago, they could hardly
come on here and have a nice chat with us about it. However, the minute
their service went official, they already invited the community to
think about this problem with them.
i totally agree with Tijl.
There are still s2s problems on the current servers. We should figure
out this problems and work on the s2s protocols for one secure standard.
When you read this list then you will see lots of developers having
problems with lots of different s2s implementations we have.
And we should start building a SPIM working group. When XMPP gets more
popular (and it will now with google), then XMPP will be also attractive
for Spammers. We must work on a solution now, and not when we get the
SPIM and it's too late.
We also should invite the google developers to our discussions. It would
be very interesting for all of us to get feedback and details about
their server implementation and clustering technologies .
Alex
_______________________________________________
jdev mailing list
[email protected]
http://mail.jabber.org/mailman/listinfo/jdev
