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.
Guus has generously provided a new Openfire plugin that implements XEP 0363 and shows off the flexibility of having the Jetty web server embedded in Openfire. If you want to perform file upload/download from the Candy Chat web application and other Strophe based web applications, then take a look at this Candy Chat plugin.
You can either drag and drop the files into the conversation window directly or click on the paperclip icon in the toolbar to select files. It then does the following:
The candy upload plugin is now available in Pàdé 0.1.14.
Screen sharing with Openfire Meetings is a bit tricky no thanks to Google's WebRTC security policy to use Chrome extensions for trust. This means you have to develop a personalised chrome extension to white-list your domain as trusted. I don't use Firefox and consequently have no idea of the user experience.
With Pàdé version 0.1.13, I have tried to improve the experience as follows:
If you use ofmeet from Pàdé exclusively, then you can screen/desk share from any domain. No extra work involved.
If you still use the ofmeet 0.3.x version, then you can use Pàdé to provide screen/desk-share from any domain as well. You should check "Desktop Share mode only" in the options screen
If you are using the ofmeet latest 0.9.x version, then you have to white-list your domain in order for Pàdé to support it. To do this, you can either raise a PR on the Pàdé repository at GitHub or raise an issue and I will add it manually. When the next Pàdé release is made, your domain should be supported.
Please note that your domain name will be exposed. This should not be a problem for a private network, but could expose your server if your domain is on the Internet. In that case, write your own chrome extension for Openfire Meetings or pay someone to do it or simply use Pàdé
The Ignite Realtime Community is thrilled to announce the availability of Openfire 4.2.1. But wait, you may wonder why Openfire 4.2.0 was not announced nor blogged about. The answer is that after a soft release of Openfire 4.2.0, we noticed a number of folks hitting a database schema issue that would cause logins to fail. We decided to turn around a fix for that issue and now fully announce the new release.
So what has changed with Openfire 4.2? A lot! Some highlights:
The changelog denotes the full listing of Jira issues addressed in this release and 4.2.0.
Here is a listing of
sha1sum values for the release binaries, which can be found on our download page.
a038d417784f6d623014ba88013407f3d36792ac openfire-4.2.1-1.i686.rpm 6c8886834b9b7d2ce6144d7ce23d3e47bbff91bd openfire-4.2.1-1.noarch.rpm 34bb23661c77b27a37572532fa23a0f8c6459015 openfire-4.2.1-1.x86_64.rpm 8a66b230323a9231dc2aca6ae7288186e56d5315 openfire_4.2.1_all.deb bcf543c65c1bf22da8c05413646230f30a60b378 openfire_4_2_1_bundledJRE.exe 947ef8ee8c08c527d1c3932bec7ea580b3c08956 openfire_4_2_1_bundledJRE_x64.exe a4ec386f9eb6cf4078b505ec57d007c799853034 openfire_4_2_1.dmg 922bb44ed7b72b75d781f1091978cb4759575112 openfire_4_2_1.exe 750524d79a18e8c6c38702f980dec961fa102f82 openfire_4_2_1.tar.gz 6d04e462bc7a5b39701d7dd1538c5508bdeff339 openfire_4_2_1_x64.exe 00b6a27057bac2b26ba6084b6606ca1ee449fc18 openfire_4_2_1.zip e918dfbfcd91d6f0562d20aa0600266db5f855e7 openfire_src_4_2_1.tar.gz 7e82909a7e9a55ed71483b054e61d0ec95b0cccf openfire_src_4_2_1.zip
Smack 4.2.2 was tagged and released recently to Maven Central.
We like to thank everyone who contributed to this release. This not only includes the various contributors shown below, but also everyone who reported an issue or suggested an improvement.
$ git shortlog -sn 4.2.1..4.2.2 >> ~/data/code/smack 39 Florian Schmaus 5 Ingo Bauersachs 2 Dmitry Deshevoy 2 damencho 2 vanitasvitae 1 iachimoe
To install, visit the Google Chrome Store
You will need at least the following four openfire plugins to use it.
Pàdé will fetch the logged in user's contact roster as well as all the bookmarks configured for the user. To see, the contacts, conference rooms and web page urls, right click on the Openfire icon.
A normal left click on the Openfire icon causes Pàdé to open into a Jitsi Meet video-conference with the currently selected contact or multi-chat room.
If the meeting is with a contact, then the meeting url is sent to the contact as a standard chat message. When Pàdé receives such a message, it displays a notification to the user.
Accepting the invitation opens the Jitsi Meet video-conference window.