I set the 'Time till idle (min)' to '3' minutes and various other settings to no avail. I don't really have access to the server, other than being able to log into it as a client, so not sure I'll be able to trouble-shoot it, but I figured I'd ask. Maybe there's some client-side debugging I can do?

 

 

And is there a XMPP api into so I can understand how the timeout/idle mechanism work, at least at a high level?

 

 

Thanks!

 

 

 

I understand that the /   "forward slash" is an escape character for ADSI, but not for LDAP.

 

 

Does Openfire use the ADSI, if not, why does it fail to import users with a forward slash?

 

 

 

Well, my solution was unique I imagine but I will post it here just in case it helps someone out.  What we had is a bunch of ldap users whos uid was slightly different due to a previous migration from one DS to Fedora DS.  So, all I had to do was correct the ldap entries which was on my list to do anyway and magically it started working.  Basically what happened for me was I ended up with an invisible partition between two groups of users and it manifested itself in weird ways like presence problems and messages never getting there even though the user appears online and lots of good stuff like that.  Once I corrected the ldap discrepencies, we haven't see the problem since.

 

 

 

 

-_Carl

 

 

 

 

(bump)

 

Sorry, but I just need to know why this is! Anyone here familiar with the archiving plugin?

 

Thanks for your help!

I was looking for a way to do this as well, and came to the conclusion that no one had written something to do it, so I did so myself.  =)  I'm attaching it to this response.

 

It will convert a jabber spool directory into an XML file compatible with the "User Import Export" plugin for OpenFire.  Just run:

 

  ./convert-jabber-spool.pl /var/lib/jabber > /tmp/openfire.xml

 

You'll need the XML::Twig and Tie::IxHash perl modules through CPAN or your distribution.

 

The spool format is missing email address and name, (I just set name to the username), and I stubbed out most of the presence stuff in the roster bits, but I was able to get users/passwords/etc. imported into a jabberd -> openfire migration with this, and all seems to work.

 

Hi,

 

 

Are these the docs you're talking about in setting up your development environment?

 

 

http://www.igniterealtime.org/community/docs/DOC-1521

 

 

http://www.igniterealtime.org/community/docs/DOC-1020

 

 

They're very good. Instead of using the trunk branch of the repository, use something in the tag branch. These are guaranteed to compile and work so if you get say svn.igniterealtime.org/svn/repos/spark/tags/spark_2_5_8 and try compiling and it works, then that is a good baseline to start looking at the trunk branch. This is what I did to make sure my environment was set up correctly.

 

 

For some more help: in NetBeans, make sure that Spark can Clean and Compile successfully first (set it up as per the NetBeans doc above). Once that is done, you can go down to the, for example, src/plugins/fastpath/build folder and then right click on the build.xml and click Run on the jar option (it should already be bolded by default). This should build the plugin's jar file (usually located in the src/plugins/fastpath folder).

 

 

 

If someone can point me to what i am doing wrong, id appreciate it.

 

 

First databases and such are not my fortay, frankly i have little idea what i am doing, but i am a quick learner, and the documentation is just not helping me.

 

 

I have created a database, i have run the script to drop the tables and set up.  I am running the set up and it never connects.

 

 

Here is what i am putting in, i just do not know if its right, i have tried a few different ways.

 

 

jdbc:jtds:sqlserver://[server]/[SQLEXPRESS]/[Databases]/[Openfire];appName=jive

 

 

  i have changed nothing else other then to put in the user and its password, i am just using the SA account and have modified its password, and made Openfire its default database.

 

 

 

What am i doing wrong?

 

 

It took us five months and about 30 thousand lines of code to complete Jabbim 0.4 „VELES“.

But the effort was worth it. Jabbim 0.4 can now honestly be called one of the best XMPP/Jabber clients out there. Sure, it certainly isn't perfect (yet) and it doesn't have the userbase of older clients, but we believe Jabbim has the power to become the client for everyone, especially when used with the astonishing service of Jabbim.com server.

Please take a look at our short features highlight or download newest release of Jabbim to see for yourself. Registration wizard If you are new to Jabbim, it's amazingly easy to create a new account. Jabbim 0.4 comes with comfortable registration wizard with several default avatars and Jabber ID availability check. Signing up is now easier than turning on the computer. User Mood, User Activity and User Chatting support You may have heard about PEP. It's an XMPP extension allowing publication of user-specific data to subscribed friends. Simply speaking, you can have your mood, your current song, the chatrooms you are in and similar information published to people in your contacts who support retrieving it.

As you have probably guessed, Jabbim supports all three mentioned ones, thus allowing you to enjoy the latest „rich presence“ fun and improve your productivity.

Jabbim supports retrieving songs from the following players: Winamp, Foobar 2000, MPD, Amarok, Exaile, Banshee, Rhythmbox, Audacious. Multi-User Chat The support for multi-user chat was finished and improved since 0.3. You can browse, join, create and configure rooms. You can also transform conversations into multi-user chat simply by dragging and dropping someone from your contacts into the conversation window. Jabbim Disk Manager Jabbim 0.4 comes with plugin support. Jabbim Disk Manager, or, as we call it, JDM, is probably the most handy among them. With JDM you can manage files on your Jabbim Disk with neat and user-friendly graphical interface. Downloading, uploading and preview of Jabbim Disk files is now easier than ever. Other plugins The list of plugins bundled with Jabbim Veles goes further.

If you'd like to share files with others, you'll probably like EasyShare plugin. People you share the file with can download it via ad-hoc commands without your participation. Easy and elegant.

The autoupdate plugin keeps track of new versions of Jabbim and its plugins, so you don't have to check yourself. Less things to care about, more time for your family, friends and work.

Since it's important to relax from time to time, we introduce Jabbim games. Although the current state is admittedly not quite ready, it certainly is a promising technology which shall be improved in forthcoming versions. Getting more smileys and plugins Getting more smileys and plugins is now as simple as a few clicks. Jabbim 0.4 provides you with buttons allowing download of additional smileys and plugins directly from the Options dialog. Get involved Please download Jabbim here. If you find any bugs, please report them in our bugreporting system. We will be very happy if you decide to help Jabbim. If you can provide code, smileys, graphics, plugins and especially test Jabbim, please join us in MUC room jabbim@conf.ne­tlab.cz and check out our wiki page. Help us with creating the XMPP/Jabber client for everyone.

If you like Jabbim, please vote for it at the Jabber.org's cli­ent list.

 

Hey all,

 

 

Marking myself as a complete noob here today but I want to check whether something is possible with xiff.  I am building a desktop app in which I'd like to embed a xiff swf.  Does a xiff swf have to live on the same server as the jabberd instance that it is connecting to or can it be distributed to the desktop? I've been reading contradictory stuff online which seems as though it may be outdated but I also have concerns in regards to the last damned update to the flash player which seems to have knocked the networked flash community for a tizzy......

 

 

Also, is there a good comparison anywhere online between as3xmpp and xiff. From what I have been able to tell so far xiff is far more robust and this may be a bit biased a place to be asking this question but what are the plusses and minuses between the two?

 

 

 

 

Thanks in advance,

 

 

Phil

 

 

 

Hello all,

 

 

I'm very new - this afternoon - to xiff and haven't been able to find much info on it online. I was able to find the svn repo as well as the beta zip.  What I noticed in the svn trunk is that there are some weird anomolies.... JID.as is a completely empty file, that kind of thing. I guess my main question is - what is the most recent stable version to work with?

 

 

Thank you,

 

 

Phil

 

 

I never said it would stop the storing of messages in memory, i just thought of a way that is less distracting to the user.

Hello all,

 

Today's chat transcript is attached. Hope to see you next week.

 

Daniel

Version 1.0 of XEP-0136: Message Archiving has been released.

This document defines mechanisms and preferences for the archiving and retrieval of XMPP messages.

The changelog is:

Per a vote of the XMPP Council, advanced status to Draft; concurrently, the XMPP Registrar issued the urn:xmpp:archive namespace. (psa)

Version 0.3 of XEP-0243: XMPP Server Compliance 2009 has been released.

This document defines XMPP server compliance levels for 2009.

The changelog is:

Added PEP as required for Advanced level per Council discussion. (psa)

Version 1.2 of XEP-0054: vcard-temp has been released.

This specification provides canonical documentation of the vCard-XML format currently in use within the Jabber community.

The changelog is:

More fully specified error cases; added section on determining support. (psa)

Version 1.24 of XEP-0045: Multi-User Chat has been released.

This specification defines an XMPP protocol extension for multi-user text chat, whereby multiple XMPP users can exchange messages in the context of a room or channel, similar to Internet Relay Chat (IRC). In addition to standard chatroom features such as

The changelog is:

Added more examples of the reason element; removed mention of nick inclusion with regard to ban lists; added denial of service considerations. (psa)

Version 1.3 of XEP-0012: Last Activity has been released.

This specification defines an XMPP protocol extension for communicating information about the last activity associated with an XMPP entity. It is typically used by an IM client to retrieve the most recent presence information from an offline contact by se

The changelog is:

Corrected server processing rules to block queries to a full JID when the requesting entity is not authorized to view the presence of the user. (psa)

Standalone Sameplace 0.9.2

I build a standalone version (ie: a completely independent) of the sameplace extension.

Download the Windows version
Download the Linux version

At the moment, only linux and windows version are available.

To do:

• Localize the application
• Built a macOS version
• Improve developperisation
• A patch to have a better ergonomics and a more pratical use
• Fix the bug that creates conflict between the extension and the standalone version
• By default a more larger window

Developpers can install this extension, it adds the official DOM inspector and javascript debugger.

http://sonnypiers.net/blog/?page_id=12

There are a lot of Jabber/XMPP email discussion lists (even more than we usually talk about on the site here, and that doesn't count specific lists for various open-source projects!). Now all the jabber.org lists are easily searchable at jabber.markmail.org, a service of the good folks at markmail.org. Just another tool to make your life a little better. :)

Version 0.3 of XEP-0223: Best Practices for Persistent Storage of Private Data via Publish-Subscribe has been released.

This specification defines best practices for using the XMPP publish-subscribe extension to persistently store private information such as bookmarks and client configuration options.

The changelog is:

Added text about composition model, and modified examples accordingly. (psa)