Ignite Realtime is the community site for the users and developers of Jive Software's open source Real Time Communications projects. Your involvement is helping to change the open RTC landscape.
Greetings all. Baring any significant community protest, the subversion server for Igniterealtime will be shutdown on 1 January 2015. All of the active and still relevant repositories have been migrated (with commit histories hopefully in-tact) to our Github presence.
The following Ignite subversion repositories were not migrated due to them likely no longer being relevant
Some of the migrated repositories to Github have not seen development in a number of years. We are certainly interested to hear of any community members that may wish to revitalize any of these projects:
When the subversion service is shutdown, a copy of the repos will be maintained offline in case anything comes up in the future necessitating its revival. Github has been an awesome platform to collaborate on for our active projects that migrated a number of months ago. Hopefully this change helps breathe some life into the older Igniterealtime projects!
Ignite Realtime is pleased to announce "Openfire Meeting", a new plugin for Openfire that continues the development of the ofmeet web application which was part of the deprecated Jitsi-videobridge plugin.
PLEASE NOTE - You will need latest Openfire 3.10.0 to use this plugin. Use a nightly build or wait for the imminent official release.
Openfire Meetings is a complete standalone plugin powered by Jitsi Videobridge. It does not depend on any other plugins
The front-end we application is a combination of Candy and Jitsi Meet and enables the following features
How to use
Jitsi Meet - https://your-server.com:7443/ofmeet
Discussion place is in the community plugins, here
So, what happens to the old jitsivideobridge plugin?
The old jitsivideobridge plugin has been deprecated and removed from igniterealtime. The embedded ofmeet and candy webrtc conferencing applications will re-appear in some future plugin later on. Watch this space.....
After months of hard work it's at the time to release the first alpha version of Smack 4.1, the open source Java XMPP client library, for testing purposes.
Smack 4.1 marks a milestone in the development history of Smack, as it's the first version that runs native on Android. This means that aSmack is no longer required and will be phased out in the future. Future aSmack releases will be solely form the stable 4.0 branch.
Together with support for Android, Smack 4.1 also adds support for XEP-198 "Stream Management" in smack-tcp. XMPP connections with enabled Stream Management provide acknowledgments of sent stanzas (and acknowledges received stanzas to the server) and allow transparent stream resumption in case of a network outage (for example because of a WiFi ↔ GSM switch on Android).
Smack 4.1.0-alpha1 is now available from Maven Central and we would welcome interested and adventurous users to try this early alpha release and provide feedback. For more information about using Smack 4.1 and how to include it in your Android project, consult the "Smack 4.1 Readme and Upgrade Guide".
5 months after the relase of Smack 3.4.1 the Ignite Realtime developer community is proud to annouce the first release of Smack 4, which marks a milestone in the development history of Smack. Smack has undergone a major overhaul and refactoring, including moving from Ant to Gradle and from SVN to git.
Smack 4 also includes security related fixes. Users are encouraged to update as soon as possible.
Many people have helped to develop this release. We especially would like to thank
- Ryan Sleevi of the Google Chrome Security Team for reporting a security flaw in ServerTrustManager (
- Thijs Alkemad for reporting a security flaw regarding IQ spoofing (
- Lars Noschinski for fixing the IQ spoofing flaws and adding support for roster versioning (
- Jens Offenbach for helping making Smack an OSGi bundle (