-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sorry about the delay, I've been busy preparing for and managing the XMPP Summit and our community's presence at FOSDEM 2012 last weekend.
However, this evening I did add a few domains to the list at xmpp.net and will aim to add one or two each day until I'm caught up. On 1/25/12 5:14 AM, Ivan Martinez wrote: > These are great news, thanks a lot :-) Ivan > > On Wed, 25 Jan 2012 12:00:01 +0000, [email protected] > wrote: >> Message: 1 Date: Tue, 24 Jan 2012 20:00:35 -0700 From: Peter >> Saint-Andre <[email protected]> Subject: [Operators] xmpp.net >> To: XMPP Operators Group <[email protected]> Message-ID: >> <[email protected]> Content-Type: text/plain; >> charset=UTF-8 >> >> Folks, this evening I coverted the information from the xmpp.org >> web page at http://xmpp.org/resources/public-services/ into a >> format that will enable us to use XEP-0309 when server software >> starts to support that protocol. I now store information about >> each server in a vCard4 file, which is converted into an >> old-style services.xml file (disco format) and into the >> index.html at xmpp.net using shell scripts and XSLT. Once we are >> running a suitable XMPP server at xmpp.net, the server software >> will gather vCards directly from other servers over the network >> (no need for admins to send the information on this email list, >> see XEP-0309 for details), those vCards will be stored in the >> right directory, and we'll have a cron job to automatically >> update the website. However, that's mostly in the future for >> now. >> >> You can see the results at http://xmpp.net/ -- if this looks >> fine, I'll create a redirect from >> http://xmpp.org/resources/public-services/ to http://xmpp.net/ >> sometime soon. >> >> Oh, and I did correct one piece of data while I was doing this >> work: I've removed jabber.fsinf.at from the server list (it still >> shows up at xmpp.org, but not at xmpp.net). >> >> Next steps: catch up on server registrations and work on >> implementation and deployment of XEP-0309. >> >> Peter >> >> -- Peter Saint-Andre https://stpeter.im/ >> >> >> >> >> ------------------------------ >> >> Message: 2 Date: Tue, 24 Jan 2012 20:04:02 -0700 From: Peter >> Saint-Andre <[email protected]> Subject: Re: [Operators] >> xmpp.net To: XMPP Operators Group <[email protected]> >> Message-ID: <[email protected]> Content-Type: >> text/plain; charset=UTF-8 >> >> BTW, I'll also check this stuff into source control (probably at >> github) so people can re-use it. >> >> On 1/24/12 8:00 PM, Peter Saint-Andre wrote: >>> Folks, this evening I coverted the information from the >>> xmpp.org web page at http://xmpp.org/resources/public-services/ >>> into a format that will enable us to use XEP-0309 when server >>> software starts to support that protocol. I now store >>> information about each server in a vCard4 file, which is >>> converted into an old-style services.xml file (disco format) >>> and into the index.html at xmpp.net using shell scripts and >>> XSLT. Once we are running a suitable XMPP server at xmpp.net, >>> the server software will gather vCards directly from other >>> servers over the network (no need for admins to send the >>> information on this email list, see XEP-0309 for details), >>> those vCards will be stored in the right directory, and we'll >>> have a cron job to automatically update the website. However, >>> that's mostly in the future for now. >>> >>> You can see the results at http://xmpp.net/ -- if this looks >>> fine, I'll create a redirect from >>> http://xmpp.org/resources/public-services/ to http://xmpp.net/ >>> sometime soon. >>> >>> Oh, and I did correct one piece of data while I was doing this >>> work: I've removed jabber.fsinf.at from the server list (it >>> still shows up at xmpp.org, but not at xmpp.net). >>> >>> Next steps: catch up on server registrations and work on >>> implementation and deployment of XEP-0309. >>> >>> Peter -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk80dxwACgkQNL8k5A2w/vwWoACfUFOjkbGjDnzBAtDQvPCDUD31 oOkAn04rC2kCZkcUohYLDj0FoyUAAT1m =N/RV -----END PGP SIGNATURE-----
