-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
you are right, "never" was a bit too hard. I just was talking about what I heard from some official sides before. Just wanted to say that would be a pretty nice "improvement". Seems to work fine for Google, but this list is not the right place for policital discussions, I guess. On 08.01.13 08:39, Pedro Melo wrote: > Hi, > > On Tue, Jan 8, 2013 at 7:32 AM, Dennis Schubert > <[email protected]> wrote: >> IIRC, Facebook will never allow s2s. > > "Never" is one of those words… > > There is no technical reason that prevents Facebook providing S2S. > Even with their usage of your own email address as login. > > When you add a new buddy to your Facebook chat app, say > [email protected], they could offer the option of using my > Facebook IM account ([email protected], who they know is > associated with that email address) or a remote Jabber/Gtalk/XMPP > account. > > The person identifier you use to add a buddy needs not be the actual > XMPP JID you'll use to communicate. It's just a mapping process at > the moment you add the buddy account. > > Only political/strategy reasons, and possibly a little concern with > another attack vector, prevent Facebook from adding S2S. > > Bye, - -- Dennis Schubert http://schub.io xmpp:[email protected] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJQ69BpAAoJEOlJwL026k+ux2MIAKH6sxk+OYTYp250Zb/sP3rI J4LtZpXf3ixlRzvMVc3JOZQgbe2MnTIbkLQ5Yvr1A328eB1XGrJrTg38eq0ri+xB PEsawi6IIBlmsm0NroseMoxWeriPi1IQsL0S58lLtWyv+UKNKTGlRs+NM1iRA5mG D0liJPZZm48MKlS6RXrStBkeWb68ccVfVvr1AVidrNo3YjCu1wqpwHa6rqIwZ9k3 LYnfKVUIZus+/nVdXOzkaqBwWgdxr/OpdjUMdw8SHSxQAsVhLIo1bHi8tYiQMNXU UqmZ17+lDdidTpwpQpBXAQZcpTgz+4gzrmO2lvIEyfzG1tpSX/aa68j9S4b65v0= =41Tm -----END PGP SIGNATURE----- _______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
