Ignite Realtime Foundation

@IgniteRealtime

Igniterealtime is an Open Source community of those that are interested in applying innovative, open-standards-based Real Time Collaboration to their businesses

Joined November 2017

Tweets

You blocked @IgniteRealtime

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @IgniteRealtime

  1. May 10

    A new release of the inVerse plugin for Openfire is now available! This plugin bundles the third-party Converse web client to make it available as an embedded component of Openfire. Find out more in our blogpost!

    Undo
  2. Apr 27

    XMPP has not been acquired.

    Undo
  3. Apr 7

    Are you developing a project or product based on any of our projects? Get in touch! We can only benefit from learning from each-other!

    Undo
  4. Apr 6

    We have released version 9.1.0-1 of the inVerse plugin for Openfire. This plugin updates the bundled Converse.js web client to its latest release! Details at

    Undo
  5. Apr 6

    Another Openfire plugin update! We've updated the JSXC plugin for Openfire to include the latest release of that client, 4.4.0! Read more on

    Undo
  6. Apr 6

    Earlier today, version 1.2.3 of the Openfire Message of the Day plugin was released. This version adds a German translation to the admin console. Read more about this release on our blog, at

    Undo
  7. Apr 6

    Version 1.8.0. of the REST API plugin for Openfire has been released. This release brings new endpoints that help monitor Openfire-based server installations.

    Undo
  8. Apr 1

    Openfire Pàdé 1.6.3 has been released! Read more at

    Undo
  9. Mar 24

    A maintenance release of the GoJara plugin for Openfire is now available! GoJara provides support for Remote Roster Management (XEP-0321). More information to be found at

    Undo
  10. Mar 3

    We are happy to announce the release of Smack 4.4.5. Thanks to numerous contributors this patch level release includes many fixes and improvements. Read more in our blog post!

    Undo
  11. Mar 1

    We are happy to be able to announce the release of Openfire Pàdé versions 1.6.2 and 1.5.6! These versions have a few issues fixed which include restoring the much-requested in-progress meeting feature of Openfire Meetings (ofmeet). Read more about it on

    Undo
  12. Feb 17

    Ignite Realtime community is happy to be able to announce the release of Openfire Pàdé versions 1.6.1 and 1.5.5. Read all about it in our release post at

    Undo
  13. Feb 16

    We have just released Openfire 4.7.1! Read more about it on

    Undo
  14. Feb 14

    We've released version 1.7.1 of the Openfire REST API plugin. This version fixes changes to the API that inadvertently sneaked into the 1.7.0 release. The API in 1.7.0 should closely resemble that of releases prior to 1.7.0! See

    Undo
  15. Feb 8

    Are you a student and interested in working on XMPP? The XMPP Standards Foundation is planning to participate as a hosting organisation in Google Summer of Code 2022. From past experience, we know this to be a very fun and rewarding experience. More info:

    Undo
  16. Jan 19

    We're excited to be able to announce the immediate availability of Openfire 4.7.0! Lots of work went into this one! Read more about it in our blog post.

    Undo
  17. Jan 5

    We have just create a release for the older 4.5 branch, that addresses an issue with its latest release that was log4j-related. Read all about it on our blog!

    Undo
  18. Jan 5

    We have released version 4.6.7 of Openfire! Read more about it on

    Undo
  19. To add better protection for the recent Log4j vulnerabilities, we have made available two new versions of Openfire: 4.6.6 and 4.5.5. These only include changes related to Log4j. Read all about it in this blog post!

    Undo
  20. With the recent discovery of a nasty Log4j vulnerability, we've pushed for an immediate release of Openfire 4.6.5 to address this issue. Please consider updating! As per usual, the full details for the release are available on our blog.

    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·