+1 but the XEP have been deferred (last update 2007): http://xmpp.org/extensions/xep-0209.html
/Steffen On Dec 28, 2012, at 5:19 AM, Sergey Dobrov <[email protected]> wrote: > Why not metacontacts here? > > Stefan de Konink <[email protected]> wrote: > >> Currently a lot of transports are available which provide a subdomain >> and a new XMPP "compatible" jid which is build out of >> old_protocol_uri@transport_subdomain. >> >> In clients such as Pidgin it is possible to group contacts which have >> the same physical identy. Similar to the resource system in XMPP, Pidgin >> offers to fallback on a different technology if the user becomes >> unavailable on either of the grouped accounts. >> >> Given that this fallback is what we actually want to see happening I >> wonder if any thought has been given on "automatic accountgrouping" or >> registering a different account as a specific resource of a user. The >> latter is currently - to my knowledge - not able to be achieved using >> current XEPs other than having a specific transport 'call in' as Jabber >> client opposed to being component. Other solutions like proprietary >> extensions fake client connectivity. >> >> >> I would like to hear some thoughts on the goal of registering >> transparent accounts, independent of technology. For example: >> user@domain/pidgin, user@domain/msn, user@domain/sip. >> >> >> Stefan >> _______________________________________________ >> JDev mailing list >> Info: http://mail.jabber.org/mailman/listinfo/jdev >> Unsubscribe: [email protected] >> _______________________________________________ > _______________________________________________ > JDev mailing list > Info: http://mail.jabber.org/mailman/listinfo/jdev > Unsubscribe: [email protected] > _______________________________________________ _______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
