In there now. I found mention of [email protected] earlier,
but that seems pretty dead. Last comment in there is from August 2014 and
it's just someone asking if anyone is there.

On 11 March 2015 at 18:13, Yonnji <[email protected]> wrote:

> I had checked xmpp.org and found a chat room [email protected]
>
> On 11/03/15 02:15, Mike Barnes wrote:
> > Well it'd be ideal to have a conference server on xmpp.net
> > <http://xmpp.net> or xmpp.org <http://xmpp.org>, but that really depends
> > on the domain owners. Doesn't even need to support client users, just
> > the conference would be nice.
> >
> > On 11 March 2015 at 09:54, Yonnji <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> >     MUC is great idea. But on which server? Everyone has their own xD
> >
> >     On 11/03/15 01:02, Mike Barnes wrote:
> >     > Yeah it looks that way, despite the last time this was brought up
> on
> >     > this list there were reassurances from the maintainer that he was
> just
> >     > "busy" or something.
> >     >
> >     > This is a massive issue across so many sites. The public directory
> on
> >     > xmpp.net <http://xmpp.net> <http://xmpp.net> needs to be REMOVED
> >     if it's not maintained,
> >     > or its maintenance handed over to someone else. It CANNOT be that
> damn
> >     > hard. The observatory is excellent and useful, but leads people to
> links
> >     > to this stupid server list that nobody can get anything added to.
> >     >
> >     > But hey, that's the way we live right? Jabber.org "temporarily"
> >     > suspended registrations two years ago. Jabber.org.au <
> http://Jabber.org.au>
> >     > <http://Jabber.org.au> is still missing any kind of web site ...
> and
> >     > we're here as operators of instant messaging and conference
> servers and
> >     > we're using a mailing list. How about an "official" MUC on
> something and
> >     > link to that instead? Oh, probably impossible, as someone would
> have to
> >     > take 10 minutes out of their day and update a web page.
> >     >
> >     > Honestly if anyone's surprised that people keep using proprietary
> >     > messaging solutions, just take a look at the half-finished and
> neglected
> >     > projects that wave an XMPP banner around, and think about who's
> actually
> >     > paying attention to users.
> >     >
> >     > On 10 March 2015 at 23:02, remi bruggeman <[email protected]
> <mailto:[email protected]>
> >     > <mailto:[email protected] <mailto:[email protected]>>> wrote:
> >     >
> >     >     The list is not managed anymore. No new entries are being
> added.
> >     >
> >     >     Rémi Bruggeman
> >     >
> >     >     On 10 Mar 2015 11:55, Mike Barnes <[email protected]
> <mailto:[email protected]>
> >     >     <mailto:[email protected] <mailto:[email protected]>>>
> wrote:
> >     >
> >     >         Hey, I thought I'd submitted this a long time ago, but
> >     >         apparently that only happened in my imagination. Are they
> >     >         getting added at the moment? :D
> >     >
> >     >
> >     >         Please add my public XMPP service to the list at xmpp.net
> <http://xmpp.net>
> >     >         <http://xmpp.net>. The information is as follows:
> >     >
> >     >         domain: jabberzac.org <http://jabberzac.org>
> >     <http://jabberzac.org>
> >     >         website: http://jabberzac.org
> >     >         year launched: 2010
> >     >         country: Australia
> >     >         latitude: -31.9
> >     >         longitude: 115.9
> >     >         CA: StartSSL
> >     >         server software: Prosody
> >     >         admin name: Mike Barnes
> >     >         admin JID: [email protected]
> >     <mailto:[email protected]> <mailto:[email protected]
> >     <mailto:[email protected]>>
> >     >         description: A primarily AU/NZ based community, focused on
> MUC
> >     >         services (on conference.jabberzac.org <
> http://conference.jabberzac.org>
> >     >         <http://conference.jabberzac.org>), also open to public
> >     use and
> >     >         registration.
> >     >
> >     >
> >
> >
>

Reply via email to