From stpeter at stpeter.im Wed Jun 3 12:53:56 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Wed, 03 Jun 2009 11:53:56 -0600 Subject: [Operators] public XMPP service: [jabbim.cz] In-Reply-To: <4A05AF57.7010803@humboldtec.cz> References: <4A05AF57.7010803@humboldtec.cz> Message-ID: <4A26B8B4.2060605@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Added. My apologies for the delay. On 5/9/09 10:29 AM, Jan Pinkas wrote: > Please add my public XMPP service to the list at > . The service information is as follows: > > * domain: [jabbim.cz] > * website: [http://www.jabbim.cz] > * year launched: [2005] > * country: [CZ] > * latitude: [50.07] > * longitude: [14.51] > * CA: [CAcert] > * server software: [ejabberd] > * admin name: [Jan Pinkas] > * admin JID: [pinky at njs.netlab.cz] > * description: [Jabbim.cz] > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkomuLQACgkQNL8k5A2w/vyPvQCgpcQYgOph0h/u2tqiAnYvJbAa TCsAnjFWY4Y8XBbpaesR4p2haSDdks1M =ry8q -----END PGP SIGNATURE----- From stpeter at stpeter.im Wed Jun 3 12:54:22 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Wed, 03 Jun 2009 11:54:22 -0600 Subject: [Operators] public XMPP service: [jabber.cz] In-Reply-To: <4A05AF23.8080602@humboldtec.cz> References: <4A05AF23.8080602@humboldtec.cz> Message-ID: <4A26B8CE.2090500@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Added. On 5/9/09 10:28 AM, Jan Pinkas wrote: > Please add my public XMPP service to the list at > . The service information is as follows: > > * domain: [jabber.cz] > * website: [http://www.jabbim.cz] > * year launched: [2001] > * country: [CZ] > * latitude: [50.07] > * longitude: [14.51] > * CA: [CAcert] > * server software: [ejabberd] > * admin name: [Jan Pinkas] > * admin JID: [pinky at njs.netlab.cz] > * description: [Jabber.cz] > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkomuM4ACgkQNL8k5A2w/vw/pACfdkZghdm42oFpFnNKA3KRij8g C1wAn1Cx+Y0O68/ZPEr5TurqyUhr6MdO =IQsf -----END PGP SIGNATURE----- From stpeter at stpeter.im Wed Jun 3 12:54:35 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Wed, 03 Jun 2009 11:54:35 -0600 Subject: [Operators] public XMPP service: [njs.netlab.cz] In-Reply-To: <4A05AF80.90604@humboldtec.cz> References: <4A05AF80.90604@humboldtec.cz> Message-ID: <4A26B8DB.3000009@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Added. On 5/9/09 10:29 AM, Jan Pinkas wrote: > Please add my public XMPP service to the list at > . The service information is as follows: > > * domain: [njs.netlab.cz] > * website: [http://www.jabbim.cz] > * year launched: [2001] > * country: [CZ] > * latitude: [50.07] > * longitude: [14.51] > * CA: [CAcert] > * server software: [ejabberd] > * admin name: [Jan Pinkas] > * admin JID: [pinky at njs.netlab.cz] > * description: [Netlab Jabber Server] > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkomuNsACgkQNL8k5A2w/vzCLQCeNkHWHDmWnpw/ZA14LA13V6Kh 8QAAoJpynrJQ5UQnhJhJ1FxLCG2ot1ph =onoR -----END PGP SIGNATURE----- From stpeter at stpeter.im Wed Jun 3 12:54:50 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Wed, 03 Jun 2009 11:54:50 -0600 Subject: [Operators] public XMPP service: [jabbim.com] In-Reply-To: <4A05AFC0.30406@humboldtec.cz> References: <4A05AFC0.30406@humboldtec.cz> Message-ID: <4A26B8EA.6080809@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Added. On 5/9/09 10:30 AM, Jan Pinkas wrote: > Please add my public XMPP service to the list at > . The service information is as follows: > > * domain: [jabbim.com] > * website: [http://www.jabbim.com] > * year launched: [2005] > * country: [CZ] > * latitude: [50.07] > * longitude: [14.51] > * CA: [CAcert] > * server software: [ejabberd] > * admin name: [Jan Pinkas] > * admin JID: [pinky at njs.netlab.cz] > * description: [Jabbim for EN users] > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkomuOkACgkQNL8k5A2w/vw9gQCgprEX7CoiNaLz5OYYyeBNMri+ FJUAoJDBP7IgwpsMJbSGS4tcjBEA6dFX =X2Gb -----END PGP SIGNATURE----- From stpeter at stpeter.im Wed Jun 3 12:55:03 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Wed, 03 Jun 2009 11:55:03 -0600 Subject: [Operators] public XMPP service: [jabbim.sk] In-Reply-To: <4A05AFE1.6000801@humboldtec.cz> References: <4A05AFE1.6000801@humboldtec.cz> Message-ID: <4A26B8F7.4030907@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Added. On 5/9/09 10:31 AM, Jan Pinkas wrote: > Please add my public XMPP service to the list at > . The service information is as follows: > > * domain: [jabbim.sk] > * website: [http://www.jabbim.sk] > * year launched: [2005] > * country: [CZ] > * latitude: [50.07] > * longitude: [14.51] > * CA: [CAcert] > * server software: [ejabberd] > * admin name: [Jan Pinkas] > * admin JID: [pinky at njs.netlab.cz] > * description: [Jabbim for SK users] > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkomuPcACgkQNL8k5A2w/vzE7gCeM1VljpHXeDSDLkcjcpfk49xG 4ScAn1NNct0mGueaE1H+AZ+Fon1aVs6e =NPnH -----END PGP SIGNATURE----- From stpeter at stpeter.im Wed Jun 3 12:55:14 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Wed, 03 Jun 2009 11:55:14 -0600 Subject: [Operators] public XMPP service: [jabbim.pl] In-Reply-To: <4A05B004.1090907@humboldtec.cz> References: <4A05B004.1090907@humboldtec.cz> Message-ID: <4A26B902.8070706@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Added. On 5/9/09 10:32 AM, Jan Pinkas wrote: > Please add my public XMPP service to the list at > . The service information is as follows: > > * domain: [jabbim.pl] > * website: [http://www.jabbim.pl] > * year launched: [2005] > * country: [CZ] > * latitude: [50.07] > * longitude: [14.51] > * CA: [CAcert] > * server software: [ejabberd] > * admin name: [Jan Pinkas] > * admin JID: [pinky at njs.netlab.cz] > * description: [Jabbim for PL users] > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkomuQIACgkQNL8k5A2w/vw6cgCg2tvCKwsj2NaoBmfqtu3f49R5 r3cAn0eIBcoCj0UWxCsPasoVfDsoYMTT =o3uu -----END PGP SIGNATURE----- From stpeter at stpeter.im Wed Jun 3 12:58:38 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Wed, 03 Jun 2009 11:58:38 -0600 Subject: [Operators] updated pages Message-ID: <4A26B9CE.9010300@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 FYI, I have updated the pages here: http://xmpp.org/services/ The data is now in an XML file: http://svn.xmpp.org:18080/browse/XMPP/trunk/services/source.xml The http://xmpp.org/services/ page is now generated from that source file via XSLT, as are the following machine-readable files: http://xmpp.org/services/services.xml http://xmpp.org/services/services-full.xml The data now also includes the latitude and longitude of the machine that hosts each service, for use in making maps and such (a request from the Pidgin developers). More soon. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkomuc4ACgkQNL8k5A2w/vwr/QCfYb+RekS4T//gHifXOL9DNkfT 1Z4AoIhhi0JEV9MBop+vZZEpvxORfOvL =ihvg -----END PGP SIGNATURE----- From stpeter at stpeter.im Wed Jun 3 13:02:10 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Wed, 03 Jun 2009 12:02:10 -0600 Subject: [Operators] request for volunteers Message-ID: <4A26BAA2.5000602@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If you would like to assist with verifying service registrations, please let me know. I even wrote a small howto about the verification process: http://xmpp.org/services/verify.shtml The tasks are simple, but I don't always have the time to complete them quickly. Thanks! Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkomuqEACgkQNL8k5A2w/vx++gCeLQRqJx3XS+hITL1kN2LNJznn j3MAn3c2x5JzGJ+xiyygo4O3ep3Et9Su =L1xp -----END PGP SIGNATURE----- From stpeter at stpeter.im Wed Jun 3 13:20:34 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Wed, 03 Jun 2009 12:20:34 -0600 Subject: [Operators] public XMPP service: JabberIM.de In-Reply-To: <4A09BC31.2050109@sebastian-riebel.de> References: <4A09BC31.2050109@sebastian-riebel.de> Message-ID: <4A26BEF2.4050407@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Added. On 5/12/09 12:13 PM, Sebastian Riebel wrote: > Hello, > > please add my public XMPP service to the list at . The service information is as follows: > > * domain: JabberIM.de > * website: http://www.JabberIM.de/ > * year launched: 2008 > * country: DE > * latitude: 50 > * longitude: 8 > * CA: XMPP ICA > * server software: OpenFire > * admin name: Sebastian Riebel > * admin JID: sebastian at JabberIM.de > * description: All users are welcome. This server provides Transports to ICQ, MSN, YAHOO, AOL and more. All passwords > (Account and Transports) are > encrypted. > > Best Regards > Sebastian Riebel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkomvvIACgkQNL8k5A2w/vxccQCgnIDT1NxbSx6wtfFEl0O+PbWb rt0AoKKktz5yOXL/QyJ+xQ4mb1XpUuLs =eH6N -----END PGP SIGNATURE----- From stpeter at stpeter.im Wed Jun 3 13:20:57 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Wed, 03 Jun 2009 12:20:57 -0600 Subject: [Operators] public XMPP service: thiessen.org In-Reply-To: <4A184E7D.1000303@thiessen.org> References: <4A184E7D.1000303@thiessen.org> Message-ID: <4A26BF09.6060805@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Added. On 5/23/09 1:29 PM, Florian Thie?en wrote: > Please add my public XMPP service to the list at > . The service information is as follows: > > * domain: thiessen.org > * website: http://xmpp.thiessen.org > * year launched: 2009 > * country: DE > * latitude: 50.1 > * longitude: 8.63 > * CA: XMPP ICA > * server software: Prosody > * admin name: Florian Thie?en > * admin JID: florian at thiessen.it > * description: Public service running Prosody development branch, also > reachable via port 80 and 443. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkomvwkACgkQNL8k5A2w/vxBPgCaAxvQ15e18uYDu7lpipo/UmCh 7IAAn2rk99/Pe0mV2Se4k0U7likdoSQO =Y8cP -----END PGP SIGNATURE----- From stpeter at stpeter.im Wed Jun 3 13:22:04 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Wed, 03 Jun 2009 12:22:04 -0600 Subject: [Operators] netops meeting / radar redux In-Reply-To: <4A217611.2010102@thiessen.it> References: <4A2051FE.5020401@stpeter.im> <4A217611.2010102@thiessen.it> Message-ID: <4A26BF4C.80905@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 5/30/09 12:08 PM, Florian Thie?en wrote: > A short summary of what we talked about: > > Community: Operators should be able to register their service, add > information, post status updates etc. > Users may be able to vote/comment. > > Monitoring: Services that choose to register are monitored for their > uptime, features etc. Tobias Markmann is working on a distributed > system, that feeds the site with all kind of neat information. > > Services: Things like DNS lookups (and so on) come to mind, but also the > option to give 'external' projects a place. Think about Matthew Wild's > bot 'HAL', which could get a subdomain (hal.xmpp-services.org or > hal.xmpp.net ...) where users 'request' the bot to join their channel. That all sounds good! I also want a nice map of the public services. ;-) We'll discuss next Tuesday... Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkomv0wACgkQNL8k5A2w/vxeswCgkH6WrrOaACKhWlvs1olQXKah hSUAnRQk2y++6kvNgbX1n4wfq0kt3qE5 =4pAl -----END PGP SIGNATURE----- From stpeter at stpeter.im Wed Jun 3 13:30:54 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Wed, 03 Jun 2009 12:30:54 -0600 Subject: [Operators] public XMPP service: zsim.de In-Reply-To: <36e09164adc72229366b6e11e2f6cace@localhost> References: <36e09164adc72229366b6e11e2f6cace@localhost> Message-ID: <4A26C15E.7050809@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Added. On 5/26/09 3:34 AM, kase at zockerstube.net wrote: > Hello, > > this is our application for the public XMPP Services list. > > * *domain*: zsim.de > * *website*: zsim.de > * *year launched*: 2009 > * *country*: Germany > * *latitude*: 49.0 > * *longitude*: 10.7 > * *CA*: CAcert > * *server software*: Openfire > * *admin name*: Kaspar Janssen > * *admin JID*: kase at zsim.de > * *description*: Our Jabber Server originaly startet for a couple of > friends but is also open for everyone else. We are respecting the > privacy of everyone and trying to serve on high availability. No > conversations will be logged. > > > regards, > > Kaspar Jan?en > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkomwV0ACgkQNL8k5A2w/vwILgCg6ZPpVLNPUEkoZgdzAP/AIJtx xdsAoKNQjxN6vGthjcA+7jJ4l2F5+4TO =Y1bE -----END PGP SIGNATURE----- From tim at we-are-teh-b.org Wed Jun 3 15:56:35 2009 From: tim at we-are-teh-b.org (Tim Schumacher) Date: Wed, 3 Jun 2009 22:56:35 +0200 Subject: [Operators] public XMPP service: boese-ban.de Message-ID: <200906032256.44967.tim@we-are-teh-b.org> Hi folks, here is my jabberd info: * domain: boese-ban.de * website: http://kaoskinder.de/jabber_server * year launched: 2008 * country: DE * latitude: * longitude: * CA: XMPP ICA * server software: ejabberd * admin name: Tim Schumacher * admin JID: tim at boese-ban.de * description: the jabberd of the ccc people of jena greetings Tim -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 315 bytes Desc: This is a digitally signed message part. URL: From paul at mcrides.co.nz Wed Jun 3 21:23:25 2009 From: paul at mcrides.co.nz (Paul) Date: Thu, 04 Jun 2009 14:23:25 +1200 Subject: [Operators] public XMPP service: jabber.co.nz Message-ID: <4A27301D.1090205@mcrides.co.nz> Hi Peter and friends Please add my public XMPP service to the list at . The service information is as follows: * domain: [jabber.co.nz] * website: [http://www.jabber.co.nz] * year launched: [2009] * country: [NZ] * latitude: [-37.46] * longitude: [175.18] * CA: [XMPP ICA] * server software: [ejabberd] * admin name: [Paul Willard] * admin JID: [paul at jabber.yeahnah.co.nz] * description: [ Representing Jabber in New Zealand ] ta, Paul. From stpeter at stpeter.im Fri Jun 5 17:52:02 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Fri, 05 Jun 2009 16:52:02 -0600 Subject: [Operators] [Fwd: [Standards] UPDATED: XEP-0268 (Incident Reporting)] Message-ID: <4A29A192.3000203@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 FYI. - -------- Original Message -------- Subject: [Standards] UPDATED: XEP-0268 (Incident Reporting) Date: Fri, 05 Jun 2009 17:42:10 -0500 From: XMPP Extensions Editor Reply-To: XMPP Standards To: standards at xmpp.org Version 0.2 of XEP-0268 (Incident Reporting) has been released. Abstract: This specification defines methods for incident reporting among XMPP server deployments. Changelog: Added more detailed information about the solution element; removed the suggestion element since the solution element can be used by both reporting entities and receiving entities; added notes about processing of incident reports by receiving entities. (mw/psa) Diff: http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0268.xml?%40diffMode=u&%40diffWrap=s&r1=3109&r2=3228&u=3&ignore=&k= URL: http://xmpp.org/extensions/xep-0268.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkopoZIACgkQNL8k5A2w/vxQxwCfciCPrgnsnFvC6QT0XlFt/k7c j5kAnjLClYTNLaQdTETrJU2JBgk0/rae =4pcU -----END PGP SIGNATURE----- From stpeter at stpeter.im Mon Jun 8 18:06:09 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Mon, 08 Jun 2009 17:06:09 -0600 Subject: [Operators] Monthly XMPP Meeting tomorrow Message-ID: <4A2D9961.5080607@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just a reminder that we will hold our Monthly XMPP Meeting tomorrow (Tuesday) at 19:00 UTC. The topics will focus on operational issues, communication among XMPP server deployments, building a site like mailradar.com for the XMPP network, etc. Details here: http://mail.jabber.org/pipermail/operators/2009-May/000583.html Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkotmWEACgkQNL8k5A2w/vzhaQCgteoDwYGFMyfVdy0yCkDCgjh3 uMIAninxzAhfvZxCvRtda4k7PBNDbYFo =qyGf -----END PGP SIGNATURE----- From melo at simplicidade.org Tue Jun 9 13:23:21 2009 From: melo at simplicidade.org (Pedro Melo) Date: Tue, 9 Jun 2009 19:23:21 +0100 Subject: [Operators] netops meeting / radar redux In-Reply-To: <4A2051FE.5020401@stpeter.im> References: <4A2051FE.5020401@stpeter.im> Message-ID: <5C239A29-2239-4262-9FBE-B3A524598507@simplicidade.org> Hi, On May 29, 2009, at 10:22 PM, Peter Saint-Andre wrote: > A while back we talked about the possibility of building a site like > http://www.mailradar.com/ but for XMPP. Florian Thiessen and I just > had > a chat about that, so I figured I'd try to restart the conversation. > Perhaps we can have a groupchat about it soon? I propose to make this > (and other matters related to network operations) the topic of our > next > "Monthly XMPP Meeting": > > Date: Tuesday, June 9, 2009 > Time: 19:00 UTC (check your local time!) eh, 40 minutes to spare :) At the time I really liked this idea and I started to write a small system to track this. I've been working on it on and off, and it mostly works right now. I need to write a small web interface and put it online. I'm pasting my "braindump document" with all the ideas, problems, questions, doubts that occured to me while thinking about this. I don't claim it to be complete, but it should cover a lot of ground. See you in 37 mins. ----8<----- Notes for a XMPP Radar ====================== What to collect --------------- The XMPP radar keeps a list of domains with related bits of information. For each domain, we should keep: * XMPP-relevant DNS records: does it have C2S, S2S or TXT records (as defined in XEP-0156: Discovering Alternative XMPP Connection Methods); * Certificates presented on C2S and S2S connections: in particular, the CA, issue and expire date and id-on-xmppAddr entries; * Advertised features: for both C2S and S2S connections. Some features are only advertised after some negotiation (for example plain text authentication only after TLS). The system should try at least STARTTLS to see if other features are offered; * disco#info information: collected over S2S. We could collect this over C2S also if the server offers account creation, but I find that a bit intrusive; * disco#items information: collected over S2S. Each new domain would be added to the database and treated as a new standalone domain; * server vCard if available; We should keep track of the date when we discovered each piece of information, as well as the date that the information is updated. Keep a history of the changes would be even better. This list is based on current XEP's. There is some talk about a new format for server contact information. If those efforts pan-out, we should also support it. Access methods -------------- The information collected would be stored in a database, and queries to the database could be made via: * an HTTP interface; * Ad-Hoc command; * Jabber search protocol. Also interesting would be a light REST-based API, providing JSON, JSONP, and XML results. Collection Methods ------------------ How can we grow the database? These are my initial ideas: * use the search interface: if someone queries the domain X, and we don't have that in our database, add it - is this kosher, privacy-wise? * create small scripts to parse common XMPP server logs: we could ask big server operators to run some scripts daily and send us the domains found - again, privacy issues, but each server has his own privacy rules. Also, we wouldn't be disclosing bare jid's, only domains; * roster analysis: script provided for most common XMPP servers to scan the rosters - same issues as previous method; * disco#items on some servers list S2S connections; * list of public servers kept by the XSF. A more aggressive approach would be to ask top level DNS maintainers for dumps of their databases, and crawl common names: * domain; * xmpp.domain; * im.domain; * jabber.domain. So far I wasn't able to find out if the list (for example) of the .{com,org,net} domains is public or not. A request from a non-profit foundation, like the XSF, has better chances of getting this lists. A final approach that is being pursued: crawl the IP address space. I got a BGP dump (about 300k networks), expanded all to /24 or smaller, and generated a list of IP addresses per network. The next step is to shuffle this set of networks. Then, we would pick an address per network, and try ports 5222, 5223 and 5269. If a TCP connection is successful, we can try and "fingerprint" the server on the other side, tricking him to give us one of the domains that he hosts. Preliminary tests indicate that some common servers are suceptible to this fingerprint process and would give us a decent number of domains. My preliminary calculations give me less than a probe per minute per network. So DoS protections shouldn't be a problem. I expect to be able to scan 10k IPs in parallel, with a 10 second timeout. No idea on how long it would take to scan the entire internet. Prior art on scanning IP networks for mail and DNS servers: http://cr.yp.to/surveys.html Database Onwership ------------------ Who owns the database? Who has raw access to it? I don't have answers here. I would prefer that the ownership of the database would stay with the XSF, but I don't know if the XSF is or isn't the proper place for this. Privacy issues -------------- Some domain operators might not want there domain listed, or searchable. There is no XMPP-based protocol to specify privacy policy for a domain. For now my best solution (not great, but should work right now until something better) is this: publish a TXT record as _xmpp-policy.domain with a HTTP URL for a XML document (schema TBD) with the privacy policy. As a fallback plan, try the well known URL http://domain/xmpp-policy.xml ------8<----- Best regards, From paul at mcrides.co.nz Tue Jun 9 15:30:05 2009 From: paul at mcrides.co.nz (Paul) Date: Wed, 10 Jun 2009 08:30:05 +1200 Subject: [Operators] [Fwd: public XMPP service: jabber.co.nz] Message-ID: <4A2EC64D.5010502@mcrides.co.nz> Have you fellas forgotten my request .. or busy talking about jabberradar ?? :) -------------- next part -------------- An embedded message was scrubbed... From: Paul Subject: [Operators] public XMPP service: jabber.co.nz Date: Thu, 04 Jun 2009 14:23:25 +1200 Size: 4200 URL: From stpeter at stpeter.im Tue Jun 9 15:34:34 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Tue, 09 Jun 2009 14:34:34 -0600 Subject: [Operators] [Fwd: public XMPP service: jabber.co.nz] In-Reply-To: <4A2EC64D.5010502@mcrides.co.nz> References: <4A2EC64D.5010502@mcrides.co.nz> Message-ID: <4A2EC75A.5080009@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just now? Talking about jabberradar. :) Pedro Melo and I will send out a summary soon... On 6/9/09 2:30 PM, Paul wrote: > Have you fellas forgotten my request .. or busy talking about > jabberradar ?? :) > > > ------------------------------------------------------------------------ > > Subject: > [Operators] public XMPP service: jabber.co.nz > From: > Paul > Date: > Thu, 04 Jun 2009 14:23:25 +1200 > To: > XMPP Operators Group > > To: > XMPP Operators Group > > > Hi Peter and friends > > > Please add my public XMPP service to the list at > . The service information is as follows: > > * domain: [jabber.co.nz] > * website: [http://www.jabber.co.nz] > * year launched: [2009] > * country: [NZ] > * latitude: [-37.46] > * longitude: [175.18] > * CA: [XMPP ICA] > * server software: [ejabberd] > * admin name: [Paul Willard] > * admin JID: [paul at jabber.yeahnah.co.nz] > * description: [ Representing Jabber in New Zealand ] > > > ta, > Paul. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoux1oACgkQNL8k5A2w/vxS3wCeNSepAOXrCc1siUPmN/BYTPWj BKgAoJkPrlVkmvMAlVicoc2hc08dv8xP =IRr4 -----END PGP SIGNATURE----- From melo at simplicidade.org Wed Jun 10 01:33:52 2009 From: melo at simplicidade.org (Pedro Melo) Date: Wed, 10 Jun 2009 07:33:52 +0100 Subject: [Operators] Notes from the 2009/06/09 Monthly meeting Message-ID: Hi, Some pre-meeting ideas where sent to the mailing list: * http://mail.jabber.org/pipermail/operators/2009-May/000584.html * http://mail.jabber.org/pipermail/operators/2009-June/000601.html 1. Radar The idea of having a site that lists domains that have a XMPP service, and associated stats (Ed: during the discussion the notion of radar and monitoring service seemed to merge, not sure if it should merge) Domains could be added by anybody or by any means to the radar DB, the information collected is publicly available on a web site. Mickael is worried about spam, if the database is available publicly or if the service allows listing of domains. The issue of database ownership was raised but not discussed. Current consensus is: * collect information from all domains found: how to find new domains was not discussed though; * publish information on the radar site, but allow for opt-out: methods for opt-out where not discussed. => Possible next steps: * gather suggestions about how to collect new domains; * methods to opt-out. The radar should have some way to include information (description, URLs, logo) in the domain/service page. There where some discussion on how to do this, the consensus seems to be that a pubsub node @domain with a well known node would work. A IQ based fallback was also mentioned. => Possible next steps: * specify types of payload: Articles (atom entries?) and "vcard" for the domain (meta data like contact address, URL, description) were mentioned as possible payloads. A second method for radar metadata maintenance was discussed: domain/ service ops should be able to use a HTML form at the radar site to update the information. The admins could authorize themselves to the radar web interface with a simple token sent with a to the domain/service. After that, the ops can use the radar web interface to publish announcements, updates and other tweaks. Useful for downtimes. A protocol using of the xmpp at domain jid to update the status of the domain/service was mentioned as a simple alternative to keep server status flowing. There where some discussion about what is federation and if we can connect to the s2s port uninvited just because you have S2S DNS records. No clear consensus. Current Radar examples: * http://imtrends.com/ * http://74.125.155.132/search?q=cache:VuFw301LIFUJ:www.jabberes.org/servers/%3Fsort%3Dhas_pep%26order%3Ddesc+jabberes+list&cd=2&hl=en&ct=clnk&gl=us * http://coccinella.im/servers/servers.html * http://coccinella.im/servers/servers_by_pubsub_pep.html 2. Domain for the radar Several proposals: * radar.xmpp.net; * xmpp-services.org; * monitor.im; * up.im; * imradar.com / imradar.org (Ed: it seems that monitor and radar are the same project? I don't think they are.); * uptime.im. 3. Monitoring A service to monitor servers uptime was also discussed. Tobias is working on something like that. His current interface is at http://monitor.ayena.de . The consensus seems to be that the monitoring should be done distributed, and reports would be send to a collector agent that would correlate the information. Some (stpeter, melo) would like to see the Server Roster XEP used for monitoring, for example, having each server monitor all the servers in his roster. Some domains where suggested to host this service: * yourstatus.org; * viewstatus.org; * whatsup.im; * bigbrother.im; => Possible next actions: * ??; 4. Robots robots.txt for xmpp: a version of the HTTP ad-hoc protocol for crawler control was discussed. Several options for implementation - a new in disco#info. The robots.txt file would be available with a iq-based protocol or on a well known pubsub node on the server. the server vcard was also mentioned as a possible place for this no further talk about what this robots.txt would contain. It was suggested to use the same format as HTTP but no discussion about if that is appropriate or workable.... => Possible next actions: * define a "robots.txt" format for XMPP use; 5. Domain admins The topic of which JIDs should be accepted as domain admins was present through out the conversation. The xmpp at domain and owner at domain hard-coded addresses where noted, as was XEP-0157. A disco#items method for discovering admin JIDs (using a well-known node value like 'urn:xmpp:valid-admins' for example) was also floated. Using a well known pubsub node @domain was also presented as an alternative. There was no clear consensus but several people (Mickael, bear, melo) prefered a pubsub-based approach. 6. Other topics A brave attempt by JMcA to bring the subject of a standard server configuration file format to ease the pain of switching servers. Best regards, From florian at thiessen.it Thu Jun 11 12:15:33 2009 From: florian at thiessen.it (=?ISO-8859-1?Q?Florian_Thie=DFen?=) Date: Thu, 11 Jun 2009 19:15:33 +0200 Subject: [Operators] Notes from the 2009/06/09 Monthly meeting In-Reply-To: References: Message-ID: <4A313BB5.1040109@thiessen.it> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey, thanks for your summary. I'm wondering if we want to separate radar and monitoring url-wise. I agree those shouldn't be thought of as the same, but I think we should provide them on the same website. Florian T. Pedro Melo schrieb: > Hi, > > Some pre-meeting ideas where sent to the mailing list: > > * http://mail.jabber.org/pipermail/operators/2009-May/000584.html > * http://mail.jabber.org/pipermail/operators/2009-June/000601.html > > > 1. Radar > > The idea of having a site that lists domains that have a XMPP service, > and associated stats > > (Ed: during the discussion the notion of radar and monitoring service > seemed to merge, not sure if it should merge) > > Domains could be added by anybody or by any means to the radar DB, the > information collected is publicly available on a web site. > > Mickael is worried about spam, if the database is available publicly or > if the service allows listing of domains. The issue of database > ownership was raised but not discussed. > > Current consensus is: > > * collect information from all domains found: how to find new domains > was not discussed though; > * publish information on the radar site, but allow for opt-out: methods > for opt-out where not discussed. > > => Possible next steps: > > * gather suggestions about how to collect new domains; > * methods to opt-out. > > The radar should have some way to include information (description, > URLs, logo) in the domain/service page. There where some discussion on > how to do this, the consensus seems to be that a pubsub node @domain > with a well known node would work. A IQ based fallback was also mentioned. > > => Possible next steps: > > * specify types of payload: Articles (atom entries?) and "vcard" for the > domain (meta data like contact address, URL, description) were mentioned > as possible payloads. > > A second method for radar metadata maintenance was discussed: > domain/service ops should be able to use a HTML form at the radar site > to update the information. > > The admins could authorize themselves to the radar web interface with a > simple token sent with a to the domain/service. After that, > the ops can use the radar web interface to publish announcements, > updates and other tweaks. Useful for downtimes. > > A protocol using of the xmpp at domain jid to update the status > of the domain/service was mentioned as a simple alternative to keep > server status flowing. > > There where some discussion about what is federation and if we can > connect to the s2s port uninvited just because you have S2S DNS records. > No clear consensus. > > Current Radar examples: > > * http://imtrends.com/ > * > http://74.125.155.132/search?q=cache:VuFw301LIFUJ:www.jabberes.org/servers/%3Fsort%3Dhas_pep%26order%3Ddesc+jabberes+list&cd=2&hl=en&ct=clnk&gl=us > > * http://coccinella.im/servers/servers.html > * http://coccinella.im/servers/servers_by_pubsub_pep.html > > > 2. Domain for the radar > > Several proposals: > > * radar.xmpp.net; > * xmpp-services.org; > * monitor.im; > * up.im; > * imradar.com / imradar.org (Ed: it seems that monitor and radar are the > same project? I don't think they are.); > * uptime.im. > > > 3. Monitoring > > A service to monitor servers uptime was also discussed. Tobias is > working on something like that. His current interface is at > http://monitor.ayena.de. > > The consensus seems to be that the monitoring should be done > distributed, and reports would be send to a collector agent that would > correlate the information. > > Some (stpeter, melo) would like to see the Server Roster XEP used for > monitoring, for example, having each server monitor all the servers in > his roster. > > Some domains where suggested to host this service: > > * yourstatus.org; > * viewstatus.org; > * whatsup.im; > * bigbrother.im; > > => Possible next actions: > > * ??; > > > 4. Robots > > robots.txt for xmpp: a version of the HTTP ad-hoc protocol for crawler > control was discussed. > > Several options for implementation - a new in disco#info. The > robots.txt file would be available with a iq-based protocol or on a well > known pubsub node on the server. the server vcard was also mentioned as > a possible place for this > > no further talk about what this robots.txt would contain. It was > suggested to use the same format as HTTP but no discussion about if that > is appropriate or workable.... > > => Possible next actions: > > * define a "robots.txt" format for XMPP use; > > > > 5. Domain admins > > The topic of which JIDs should be accepted as domain admins was present > through out the conversation. The xmpp at domain and owner at domain > hard-coded addresses where noted, as was XEP-0157. > > A disco#items method for discovering admin JIDs (using a well-known node > value like 'urn:xmpp:valid-admins' for example) was also floated. Using > a well known pubsub node @domain was also presented as an alternative. > > There was no clear consensus but several people (Mickael, bear, melo) > prefered a pubsub-based approach. > > > 6. Other topics > > A brave attempt by JMcA to bring the subject of a standard server > configuration file format to ease the pain of switching servers. > > > Best regards, -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoxO7MACgkQaeqoWtiIdZIPbgCeK+5ca0wqcCxktnNceHrUes4+ My0An3H0Y9MWJKJUm/W8dVYqkEMF/Upt =c35E -----END PGP SIGNATURE----- From melo at simplicidade.org Fri Jun 12 04:55:02 2009 From: melo at simplicidade.org (Pedro Melo) Date: Fri, 12 Jun 2009 10:55:02 +0100 Subject: [Operators] Notes from the 2009/06/09 Monthly meeting In-Reply-To: <4A313BB5.1040109@thiessen.it> References: <4A313BB5.1040109@thiessen.it> Message-ID: On Jun 11, 2009, at 6:15 PM, Florian Thie?en wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hey, > > thanks for your summary. > I'm wondering if we want to separate radar and monitoring url-wise. > I agree those shouldn't be thought of as the same, but I think we > should > provide them on the same website. URLs/Sites are "free", just link from one to the other. Best regards, > > > Florian T. > > Pedro Melo schrieb: >> Hi, >> >> Some pre-meeting ideas where sent to the mailing list: >> >> * http://mail.jabber.org/pipermail/operators/2009-May/000584.html >> * http://mail.jabber.org/pipermail/operators/2009-June/000601.html >> >> >> 1. Radar >> >> The idea of having a site that lists domains that have a XMPP >> service, >> and associated stats >> >> (Ed: during the discussion the notion of radar and monitoring service >> seemed to merge, not sure if it should merge) >> >> Domains could be added by anybody or by any means to the radar DB, >> the >> information collected is publicly available on a web site. >> >> Mickael is worried about spam, if the database is available >> publicly or >> if the service allows listing of domains. The issue of database >> ownership was raised but not discussed. >> >> Current consensus is: >> >> * collect information from all domains found: how to find new domains >> was not discussed though; >> * publish information on the radar site, but allow for opt-out: >> methods >> for opt-out where not discussed. >> >> => Possible next steps: >> >> * gather suggestions about how to collect new domains; >> * methods to opt-out. >> >> The radar should have some way to include information (description, >> URLs, logo) in the domain/service page. There where some discussion >> on >> how to do this, the consensus seems to be that a pubsub node @domain >> with a well known node would work. A IQ based fallback was also >> mentioned. >> >> => Possible next steps: >> >> * specify types of payload: Articles (atom entries?) and "vcard" >> for the >> domain (meta data like contact address, URL, description) were >> mentioned >> as possible payloads. >> >> A second method for radar metadata maintenance was discussed: >> domain/service ops should be able to use a HTML form at the radar >> site >> to update the information. >> >> The admins could authorize themselves to the radar web interface >> with a >> simple token sent with a to the domain/service. After that, >> the ops can use the radar web interface to publish announcements, >> updates and other tweaks. Useful for downtimes. >> >> A protocol using of the xmpp at domain jid to update the >> status >> of the domain/service was mentioned as a simple alternative to keep >> server status flowing. >> >> There where some discussion about what is federation and if we can >> connect to the s2s port uninvited just because you have S2S DNS >> records. >> No clear consensus. >> >> Current Radar examples: >> >> * http://imtrends.com/ >> * >> http://74.125.155.132/search?q=cache:VuFw301LIFUJ:www.jabberes.org/servers/%3Fsort%3Dhas_pep%26order%3Ddesc+jabberes+list&cd=2&hl=en&ct=clnk&gl=us >> >> * http://coccinella.im/servers/servers.html >> * http://coccinella.im/servers/servers_by_pubsub_pep.html >> >> >> 2. Domain for the radar >> >> Several proposals: >> >> * radar.xmpp.net; >> * xmpp-services.org; >> * monitor.im; >> * up.im; >> * imradar.com / imradar.org (Ed: it seems that monitor and radar >> are the >> same project? I don't think they are.); >> * uptime.im. >> >> >> 3. Monitoring >> >> A service to monitor servers uptime was also discussed. Tobias is >> working on something like that. His current interface is at >> http://monitor.ayena.de. >> >> The consensus seems to be that the monitoring should be done >> distributed, and reports would be send to a collector agent that >> would >> correlate the information. >> >> Some (stpeter, melo) would like to see the Server Roster XEP used for >> monitoring, for example, having each server monitor all the servers >> in >> his roster. >> >> Some domains where suggested to host this service: >> >> * yourstatus.org; >> * viewstatus.org; >> * whatsup.im; >> * bigbrother.im; >> >> => Possible next actions: >> >> * ??; >> >> >> 4. Robots >> >> robots.txt for xmpp: a version of the HTTP ad-hoc protocol for >> crawler >> control was discussed. >> >> Several options for implementation - a new in disco#info. >> The >> robots.txt file would be available with a iq-based protocol or on a >> well >> known pubsub node on the server. the server vcard was also >> mentioned as >> a possible place for this >> >> no further talk about what this robots.txt would contain. It was >> suggested to use the same format as HTTP but no discussion about if >> that >> is appropriate or workable.... >> >> => Possible next actions: >> >> * define a "robots.txt" format for XMPP use; >> >> >> >> 5. Domain admins >> >> The topic of which JIDs should be accepted as domain admins was >> present >> through out the conversation. The xmpp at domain and owner at domain >> hard-coded addresses where noted, as was XEP-0157. >> >> A disco#items method for discovering admin JIDs (using a well-known >> node >> value like 'urn:xmpp:valid-admins' for example) was also floated. >> Using >> a well known pubsub node @domain was also presented as an >> alternative. >> >> There was no clear consensus but several people (Mickael, bear, melo) >> prefered a pubsub-based approach. >> >> >> 6. Other topics >> >> A brave attempt by JMcA to bring the subject of a standard server >> configuration file format to ease the pain of switching servers. >> >> >> Best regards, > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkoxO7MACgkQaeqoWtiIdZIPbgCeK+5ca0wqcCxktnNceHrUes4+ > My0An3H0Y9MWJKJUm/W8dVYqkEMF/Upt > =c35E > -----END PGP SIGNATURE----- -- Pedro Melo Blog: http://www.simplicidade.org/notes/ XMPP ID: melo at simplicidade.org Use XMPP! From rain at richim.org Thu Jun 25 14:36:29 2009 From: rain at richim.org (Alexandr Shapoval) Date: Thu, 25 Jun 2009 22:36:29 +0300 Subject: [Operators] public XMPP service: [richim.org] Message-ID: <4A43D1BD.3080109@richim.org> Please add my public XMPP service to the list at . The service information is as follows: * *domain*: [richim.org] * *website*: [http://richim.org] * *year launched*: [2009] * *country*: [UA] * *latitude*: [56.5] * *longitude*: [-2.9667] * *CA*: [StartCom Ltd.] * *server software*: [ejabberd] * *admin name*: [Alexandr Shapoval] * *admin JID*: [rain at richim.org] * *description*: [Free public Jabber service with many capabilities and the best support for Ukrainian users. Located in UK.] From daniel at freies-im.de Mon Jun 29 10:38:10 2009 From: daniel at freies-im.de (Daniel Vigano) Date: Mon, 29 Jun 2009 17:38:10 +0200 Subject: [Operators] public XMPP service: freies-im.de Message-ID: <1246289890.3935.13.camel@elefant> Hello! Please add my public XMPP service to the list at http://xmpp.org/services/. The service information is as follows: * domain: freies-im.de * website: http://www.freies-im.de * year launched: 2009 * country: DE * latitude: 39.8048415 * longitude: -76.8663195 * CA: CAcert * server software: ejabberd * admin name: Daniel Vigano * admin JID: daniel at freies-im.de * description: A free (not in the spirit of freebier) Jabber service From cascardo at jabber-br.org Mon Jun 29 11:11:10 2009 From: cascardo at jabber-br.org (Thadeu Lima de Souza Cascardo) Date: Mon, 29 Jun 2009 13:11:10 -0300 Subject: [Operators] [cascardo@jabber-br.org: public XMPP service: jabber-br.org] Message-ID: <20090629161109.GD4327@vespa.holoscopio.com> We have upgraded about 10 days ago and we think TLS support is fine now: the whole key chain is sent as fixed in ejabberd. ----- Forwarded message from Thadeu Lima de Souza Cascardo ----- Date: Tue, 7 Apr 2009 00:27:32 -0300 From: Thadeu Lima de Souza Cascardo To: operators at xmpp.org Subject: [Operators] public XMPP service: jabber-br.org User-Agent: Mutt/1.5.19 (2009-01-05) domain: jabber-br.org website: http://jabber-br.org/ (not a proper website still) year launched: 2005 country: run by Brazillian people, but hosted in USA CA: XMPP ICA server software: ejabberd in Debian lenny admin name: Thadeu Lima de Souza Cascardo admin JID: cascardo at jabber-br.org description: a Jabber service run by Brazillian people ----- End forwarded message ----- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From stpeter at stpeter.im Mon Jun 29 11:28:38 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Mon, 29 Jun 2009 10:28:38 -0600 Subject: [Operators] [cascardo@jabber-br.org: public XMPP service: jabber-br.org] In-Reply-To: <20090629161109.GD4327@vespa.holoscopio.com> References: <20090629161109.GD4327@vespa.holoscopio.com> Message-ID: <4A48EBB6.9070504@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Great, I will check it soon. :) On 6/29/09 10:11 AM, Thadeu Lima de Souza Cascardo wrote: > We have upgraded about 10 days ago and we think TLS support is fine now: > the whole key chain is sent as fixed in ejabberd. > > ----- Forwarded message from Thadeu Lima de Souza Cascardo ----- > > Date: Tue, 7 Apr 2009 00:27:32 -0300 > From: Thadeu Lima de Souza Cascardo > To: operators at xmpp.org > Subject: [Operators] public XMPP service: jabber-br.org > User-Agent: Mutt/1.5.19 (2009-01-05) > > domain: jabber-br.org > website: http://jabber-br.org/ (not a proper website still) > year launched: 2005 > country: run by Brazillian people, but hosted in USA > CA: XMPP ICA > server software: ejabberd in Debian lenny > admin name: Thadeu Lima de Souza Cascardo > admin JID: cascardo at jabber-br.org > description: a Jabber service run by Brazillian people > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpI67UACgkQNL8k5A2w/vyZ1ACePPNXy3ICzY5aNErDwKDy+xUp O9oAn3IG6j/QDJq8MMjD9mHi5dsNnNyh =/wUL -----END PGP SIGNATURE----- From stpeter at stpeter.im Mon Jun 29 17:35:14 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Mon, 29 Jun 2009 16:35:14 -0600 Subject: [Operators] Notes from the 2009/06/09 Monthly meeting In-Reply-To: References: Message-ID: <4A4941A2.9030308@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Any progress on this front? How can I help? :) On 6/10/09 12:33 AM, Pedro Melo wrote: > Hi, > > Some pre-meeting ideas where sent to the mailing list: > > * http://mail.jabber.org/pipermail/operators/2009-May/000584.html > * http://mail.jabber.org/pipermail/operators/2009-June/000601.html > > > 1. Radar > > The idea of having a site that lists domains that have a XMPP service, > and associated stats > > (Ed: during the discussion the notion of radar and monitoring service > seemed to merge, not sure if it should merge) > > Domains could be added by anybody or by any means to the radar DB, the > information collected is publicly available on a web site. > > Mickael is worried about spam, if the database is available publicly or > if the service allows listing of domains. The issue of database > ownership was raised but not discussed. > > Current consensus is: > > * collect information from all domains found: how to find new domains > was not discussed though; > * publish information on the radar site, but allow for opt-out: methods > for opt-out where not discussed. > > => Possible next steps: > > * gather suggestions about how to collect new domains; > * methods to opt-out. > > The radar should have some way to include information (description, > URLs, logo) in the domain/service page. There where some discussion on > how to do this, the consensus seems to be that a pubsub node @domain > with a well known node would work. A IQ based fallback was also mentioned. > > => Possible next steps: > > * specify types of payload: Articles (atom entries?) and "vcard" for the > domain (meta data like contact address, URL, description) were mentioned > as possible payloads. > > A second method for radar metadata maintenance was discussed: > domain/service ops should be able to use a HTML form at the radar site > to update the information. > > The admins could authorize themselves to the radar web interface with a > simple token sent with a to the domain/service. After that, > the ops can use the radar web interface to publish announcements, > updates and other tweaks. Useful for downtimes. > > A protocol using of the xmpp at domain jid to update the status > of the domain/service was mentioned as a simple alternative to keep > server status flowing. > > There where some discussion about what is federation and if we can > connect to the s2s port uninvited just because you have S2S DNS records. > No clear consensus. > > Current Radar examples: > > * http://imtrends.com/ > * > http://74.125.155.132/search?q=cache:VuFw301LIFUJ:www.jabberes.org/servers/%3Fsort%3Dhas_pep%26order%3Ddesc+jabberes+list&cd=2&hl=en&ct=clnk&gl=us > > * http://coccinella.im/servers/servers.html > * http://coccinella.im/servers/servers_by_pubsub_pep.html > > > 2. Domain for the radar > > Several proposals: > > * radar.xmpp.net; > * xmpp-services.org; > * monitor.im; > * up.im; > * imradar.com / imradar.org (Ed: it seems that monitor and radar are the > same project? I don't think they are.); > * uptime.im. > > > 3. Monitoring > > A service to monitor servers uptime was also discussed. Tobias is > working on something like that. His current interface is at > http://monitor.ayena.de. > > The consensus seems to be that the monitoring should be done > distributed, and reports would be send to a collector agent that would > correlate the information. > > Some (stpeter, melo) would like to see the Server Roster XEP used for > monitoring, for example, having each server monitor all the servers in > his roster. > > Some domains where suggested to host this service: > > * yourstatus.org; > * viewstatus.org; > * whatsup.im; > * bigbrother.im; > > => Possible next actions: > > * ??; > > > 4. Robots > > robots.txt for xmpp: a version of the HTTP ad-hoc protocol for crawler > control was discussed. > > Several options for implementation - a new in disco#info. The > robots.txt file would be available with a iq-based protocol or on a well > known pubsub node on the server. the server vcard was also mentioned as > a possible place for this > > no further talk about what this robots.txt would contain. It was > suggested to use the same format as HTTP but no discussion about if that > is appropriate or workable.... > > => Possible next actions: > > * define a "robots.txt" format for XMPP use; > > > > 5. Domain admins > > The topic of which JIDs should be accepted as domain admins was present > through out the conversation. The xmpp at domain and owner at domain > hard-coded addresses where noted, as was XEP-0157. > > A disco#items method for discovering admin JIDs (using a well-known node > value like 'urn:xmpp:valid-admins' for example) was also floated. Using > a well known pubsub node @domain was also presented as an alternative. > > There was no clear consensus but several people (Mickael, bear, melo) > prefered a pubsub-based approach. > > > 6. Other topics > > A brave attempt by JMcA to bring the subject of a standard server > configuration file format to ease the pain of switching servers. > > > Best regards, > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpJQaIACgkQNL8k5A2w/vxWNACeK8TMvevtL3auUBAr+2Q52cqg r0sAoIZEio0BMgTJvDtHPDGs56MQW8ke =KxNX -----END PGP SIGNATURE----- From stpeter at stpeter.im Mon Jun 29 22:27:22 2009 From: stpeter at stpeter.im (Peter Saint-Andre) Date: Mon, 29 Jun 2009 21:27:22 -0600 Subject: [Operators] public XMPP service: jabber.co.nz In-Reply-To: <4A27301D.1090205@mcrides.co.nz> References: <4A27301D.1090205@mcrides.co.nz> Message-ID: <4A49861A.1050300@stpeter.im> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Added. Thanks for registering! On 6/3/09 8:23 PM, Paul wrote: > Hi Peter and friends > > > Please add my public XMPP service to the list at > . The service information is as follows: > > * domain: [jabber.co.nz] > * website: [http://www.jabber.co.nz] > * year launched: [2009] > * country: [NZ] > * latitude: [-37.46] > * longitude: [175.18] > * CA: [XMPP ICA] > * server software: [ejabberd] > * admin name: [Paul Willard] > * admin JID: [paul at jabber.yeahnah.co.nz] > * description: [ Representing Jabber in New Zealand ] > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpJhhoACgkQNL8k5A2w/vyw7gCgsVA+LzWpH22YVMJLc64LGyH+ /PcAn1AbyThVcGE00nBybp09FA4lgua5 =gnMf -----END PGP SIGNATURE-----