Tag Archives: Jabber

feeds

Peter Saint-Andre (Jabber): Org Docs

2011/09/24 – 00:43

Today I also scanned in and posted a bunch of official documents related to the Jabber Software Foundation (articles of incorporation and the like) -- check them out here.

Tags , , , , | Permalink | Comments Off
about

Welcome to Jaim.at!

2011/08/13 – 00:43

Our Jabber server has moved to a new location and got updated to a  ejabberd version.
Various transports installation will follow soon.

thank you for your mental support,
FRZ

Incoming search terms:

Tags , , , , | Permalink | Comments (7)
feeds

Connectivity Issues Solved

2011/08/04 – 17:26

Just a quick note that the jabber.org admin team (thanks, Kev!) worked with the Google Talk admin team (thanks Jonas and Pascal!) to diagnose the problem. It turns out that Google had some broken DNS records, which have been fixed. Data is flowing smoothly again, but as always let us know if you experience any further problems.

Tags , , , , , , , | Permalink | Comments Off
feeds

Python transports conference room moved

2011/08/04 – 12:42

As of now, the official location of the pytransports conference room is:
pytransports@conference.jabber.modevia.com

Many thanks to Modevia for providing a good stable location for the conference room!

Tags , , , , | Permalink | Comments Off
feeds

Thiago Rocha Camargo: XMPP Server SRV Record Tutorial

2011/05/21 – 23:26
With the new Openfire Version (3.7.0) released in March. I noticed a change in the S2S (federation) integration and would like to share the tips to help the setup to be done by other XMPP System Admins.

To prevent connection issue among the Servers it is required the registration of the SRV records according to the example:

In the case of the domain minhaempresa.com.br and the jabber domain to be  xmpp.minhaempresa.com.br the following records are required:_jabber._tcp.xmpp.minhaempresa.com.br_jabber._tcp.minhaempresa.com.br_xmpp-server._tcp.xmpp.minhaempresa.com.br_xmpp-server._tcp.minhaempresa.com.brAll the registration must point to your jabber domain, as noticed below:
marcelo@hellboy:~$ dig srv _xmpp-server._tcp.minhaempresa.com.br

; < <>> DiG 9.7.3 < <>> srv _xmpp-server._tcp.minhaempresa.com.br
;; global options: +cmd
;; Got answer:
;; ->>HEADER< <- opcode: QUERY, status: NOERROR, id: 11368
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;_xmpp-server._tcp.minhaempresa.com.br. IN SRV

;; ANSWER SECTION:
_xmpp-server._tcp.minhaempresa.com.br. 86297 IN SRV 0 1 5269 xmpp.minhaempresa.com.br.

;; Query time: 16 msec
;; SERVER: 200.175.5.139#53(200.175.5.139)
;; WHEN: Sun May 15 00:24:00 2011
;; MSG SIZE rcvd: 89I've have faced this situation when migrating a customer server that was upgraded a from a previous version of Openfire. If you don't register the domain fixing SRV record, S2S functionallity will not work.

* This is an authorized translation from the Blog Mundo OpenSource written by Marcelo Terres.  Especial thanks for the great and simple guide for setting up DNS SRV records required for an XMPP server.
Tags , , , , , , | Permalink | Comments Off
about

Remote Roster Management

2011/05/12 – 13:52

Jaim.at update to support Remote Roster Management for transports to legacy networks like AIM, ICQ, MSN, YAHOO and XMPP.

Remote roster is a “proto XEP” which allows your server to synchronize legacy network contact list with your users’ rosters. Currently it works only for local users (users registered on the same server which supports this protoXEP). It’s available for Ejabberd 2.1.x and Prosody.

 

  • When they register their account and login for first time, they won’t receive lots of subscribe presences or Roster Item Exchanged stanza. All their legacy network buddies just appear in their roster with proper groups and nicknames.
  • When they will unregistering their account, buddies are just removed from their rosters without need of unsubscribing them.
  • When they rename some buddy in their Jabber roster, it’s renamed also in legacy network.
  • When they move some buddy into different groups, it’s moved also in legacy network.
  • All changes made in legacy network when transport is disconnected are synchronized with Jabber account once they become online in Jabber.

 

Incoming search terms:

Tags , , , , , , , , | Permalink | Comments Off
feeds

Twitter Updates for 2011-05-12

2011/05/12 – 10:34
Tags , | Permalink | Comments Off
about

JaIM.at website relaunch

2011/05/09 – 15:34

Following an period of consultation, JaIM.at relaunched its website at 1. Mai this month. The new site incorporates a number of significant improvements developed on the basis of extensive usability testing.

Improvements include much-improved search capabilities and a much clearer design. The new site also includes improved support for RSS feeds, which are now available for jabber related publications, as well as Jappix an open-source XMPP web-client for the worldwide Jabber Service.

If you have any comments or queries related to the new website please send your suggestions.

Comments or questions are welcome.

*(denotes required field)

Powered by Fast Secure Contact Form

Tags , , , , , , , | Permalink | Comments Off
about

Welcome to jaim.at!

2011/05/04 – 14:39

Welcome to JaIM.at’s public Jabber Instant Messaging (IM) service, you can interact with millions of other Jabber users worldwide!

Please register your Jabber ID with a jabber client of your choice to join the Jabber network, if you want a web client there’s jappix.jaim.at a full featured, web based jabber client available.

Jabber is an excellent and secure instant messaging protocol. You can choose your own server to use, similar to mail. A list of available clients for various platforms is available at xmpp.org.

The owners of JaIM.at are not responsible for the content of our users’ pages and input. JaIM.at provides no warranty that the service will be uninterrupted or error-free. We assume no liability, expressed or implied, for any downtime for any reason.

Enjoy! FRZ

 

Incoming search terms:

Tags , , , , , , , | Permalink | Comments Off
feeds

jitsi: Emil talks about "XMPP Conf Calls: One Way or Another" in the FOSDEM Jabber & XMPP devroom. http://ur1.ca/34azi

2011/02/05 – 19:40
Emil talks about "XMPP Conf Calls: One Way or Another" in the FOSDEM Jabber & XMPP devroom. http://ur1.ca/34azi
Tags , , , , , | Permalink | Comments Off
feeds

More Certificate Fun

2011/01/07 – 23:31

If you tried to register a new account in the last ~48 hours, you probably noticed that the certificate we use expired. We’ve updated the certificate at register.jabber.org so that it uses the same certificate we use for the XMPP service. You can now register accounts securely again. :)

Tags , , , | Permalink | Comments Off
feeds

Certificate Renewal

2010/12/16 – 15:23

The digital certificate for the jabber.org service expired this morning. We’re working to renew it as fast as possible, but it might take an hour or two because it requires manual approval by our certification authority. Sorry about the confusion.

UPDATE: The new cert is in place, and improved processes are on the way. :)

Tags , , , , , , | Permalink | Comments Off
feeds

Service Update, 2010-03-18

2010/03/18 – 20:07

This morning the jabber.org admin team installed a new build of M-Link provided by Isode. This build addresses the major issues we’ve had over the last month or so.

First, communication between Google Talk and jabber.org appears to be fixed. We can’t promise that you’ll never experience any difficulties chatting with your Google Talk friends, but the previous problem (lagged and in some cases lost messages) has been solved.

Second, the old legacy SSL port 5223 is working again, enabling you to connect using most older clients (e.g., iChat on Tiger) as well as various “crippled” clients that still don’t support STARTTLS on port 5222 (e.g., mobile clients like QIP and SIM). We will continue to encourage developers of those clients to add STARTTLS support and we reserve the right to turn off port 5223 at some point in the future, but we probably won’t do so until platforms like OS X Tiger and KDE 3 have been end-of-lifed.

Several smaller issues have yet to be fixed (e.g., chatroom logs and persistent storage of changes to personal vCards and chatroom configurations), but we will be working with the Isode team on those fixes in the coming weeks. We are also aware that we still need to get web registration working again. If you really need a new jabber.org account instead of an account at one of the many other open XMPP services, please use the contact information provided on the Get Help page for assistance and we’ll try to take care of your request as soon as possible.

Tags , , , , , , | Permalink | Comments Off
feeds

Service Update, 2010-03-14

2010/03/15 – 06:45

This is just a quick note to let jabber.org users know that the folks at Isode have been working on fixes to a number of the open issues we mentioned in our last update, including our communication problems with Google Talk. Testing is underway and we hope to be installing updated software this week.

Tags , , , , , | Permalink | Comments Off
feeds

Service Update, 2010-02-16

2010/02/16 – 23:06

Our apologies for the lack of reports over the last 10 days or so — most of the jabber.org admin team was at FOSDEM 2010 / XMPP Summit #8 the weekend of February 5-8, and it takes a little while to recover from so much Jabber fun. :)

As you might have noticed, last Friday we installed an updated build of M-Link, which incorporates a number of fixes and has been quite a bit more stable.

There are still some unresolved issues that are being worked on by the jabber.org admin team, the Isode M-Link team, or both:

Communication between Google Talk and jabber.org has unacceptable lag most of the time. We’re still working to debug this problem. Some old or incomplete clients simply cannot connect to the server securely since we turned off the legacy SSL-only port 5223, including Miranda (see update!), Palringo, QIP PDA, Sameplace, and old releases of clients like Kopete on KDE 3.x and iChat on OS X Tiger. Although most clients are working just fine on port 5222 with encryption upgrade using STARTTLS, we will turn port 5223 on again in the near future (this requires a new build from Isode because they never expected that people still needed port 5223, given that it was deprecated in 2004!). Room logs are not enabled yet for posting to logs.jabber.org. We should have those working again in the next week. New user registration is not working yet at register.jabber.org. We’ll try to have it working again this week or next (there are some backend changes required). Until then, feel free to create an account at one of the many other XMPP-based IM services.

We think those are the main issues at this time, but as always feel free to join the jabber@conference.jabber.org chatroom via XMPP or HTTP if you have questions or comments.

– Peter Saint-Andre

Tags , , , , , , | Permalink | Comments Off
feeds

Service Update, 2010-02-03

2010/02/04 – 07:36

As you might have noticed, the jabber.org IM service has been much more stable in the last few days, thanks to a number of bug fixes from our friends at Isode. There are still several known issues that have been fixed in M-Link, but both Isode personnel and jabber.org admins are travelling this week for the XMPP Summit in Brussels this weekend, so we won’t deploy any updated software builds until sometime next week. This will also give Isode’s QA department an opportunity to complete some more thorough testing than was possible while we were all in “crisis mode” over the last two weeks. Finally, we are also still working to pinpoint some remaining issues (such as delayed and even dropped messages from gmail.com to jabber.org), which the admin team will discuss with the Isode team this weekend. If pertinent information becomes available, we will post again in the next few days. Thanks again for your patience during the recent migration.

Peter Saint-Andre

Tags , , , , , | Permalink | Comments Off
feeds

Service Update, 2010-01-29

2010/01/30 – 07:42

This is the jabber.org service notice for Friday, January 28, 2010.

For the most part, today was a good day at the jabber.org IM service. We installed a new build from Isode earlier today that seems to have solved the login delays our users experienced, as well as most of the memory usage issues. This build isn’t perfect, because we had a hard crash this evening, followed by some false restarts, so we’ll be monitoring it closely over the weekend. In addition to these fixes, the jabber.org admin team corrected a problem with our digital certificate and continues to debug connection issues with a number of different IM clients.

We will post updates over the weekend, so stay tuned.

Tags , , , , , , | Permalink | Comments Off

Next Page »

Next Page »