The Ignite Realtime Community is pleased to announce the release of version 3.10.3 of Openfire.  This release continues our effort to produce a stable 3.10 release series of Openfire while we work toward the next major release of Openfire.  The release is available now for download from our website.

The Changelog for this release denotes 12 fixed Jira issues with thanks to contributions from speedy3k , tevans , csh, Guus, and dwd.

Here are SHA-1 hashes for the download artifacts

10093d7d5af8e68a69544d1a647978f2523f88c7  openfire_3_10_3.dmg

ecc63d97173f6795759fe8bfab5974477d98d608  openfire_3_10_3.exe

8e5609b1d44cd1f6ede939f5219c70acd7d06e38  openfire_3_10_3.tar.gz

a1fd0d677453bedde3d7e8f90505c8436f8279ec  openfire_3_10_3.zip

22cf5b6a62760d53bcd87d4b87f3c787cb5a57b7  openfire_src_3_10_3.tar.gz

5c6b303b46ce88a3c02f50f10f0e1ddd1e9a4085  openfire_src_3_10_3.zip

ebf86f137e4cf95552f7d22d2e65fb93e3aa6794  openfire-3.10.3-1.i386.rpm

211545b3c4e1f88a34ee7ba4a9fd5d5325de72b8  openfire_3.10.3_all.deb

Please note that we are no longer producing a Solaris build, due to perceived lack of interest and some strange build problems we encountered with our Bamboo build agent.  If you would like to help out with creating a Solaris build, please respond in the community forums.

As a reminder, Openfire is developed by a group of volunteers and are always looking for more developers and testers to pitch in.  Please stop by our XMPP chatroom open_chat@conference.igniterealtime.org at any time and say if you are interested in helping out!

Happy Chatting!

daryl

The Ignite Realtime community is proud to announce the availability of Smack 4.1.5. Like all patch level releases, this release includes some important fixes and users are strongly encouraged to update. Smack 4.1.5 is a API compatible drop-in replacement for every release of the Smack 4.1 series. Have a look at the changelog and the git changelog.

Thanks to everyone who contributed to this release by providing bug reports and patches.

Over the last few weeks, I have answered a few questions about Openfire Meetings and would like to post them here for others who might find them useful.

How do create a co-browsing between participants in a meeting

Co-browsing, in the context of web browsing, is the joint navigation through the World Wide Web by two or more people accessing the same web pages at the same time.

Co-browsing URLs are configured with the client control plugin. You can share URLs with all, specific users or user groups. The URL description appears in the pull-down list of the collaboration applications menu on the web client. It should also appear in Spark, but I have never tested it. The basic user experience is the syncing of DOM events via the chrome extension and the visual shared cursors of each participant labelled with their names. See this blog for more details.

How do I setup the SIP integration for Openfire Meetings? How can I achieve call-in and call-out to meetings?

SIP integration is a bit detailed. It only works with persistent chat rooms. It requires changing the default values in the openfire meetings settings admin web page.  You have to enable VOIP, audio mixer and configure either or both server and client roles. In server role, Openfire meetings will act as A SIP registrar and accept SIP registrations for any standard SIP phone or device or mobile softphone app.  In client mode, openfire meetings will register with Asterisk, FreeSwitch or any SIP proxy, IP PBX. To associate a SIP phone call with an openfire meeting, you decide on any dial-able telephone number from the SIP device or SIP Proxy/PBX and link it with a chat room. You can put the number in the description or create a room using the telephone number as the name.

For outgoing calls from the web client, you must also make sure that one of the room moderators is a participant in the meeting otherwise the telephone icon will not appear. You can optionally use the client control plugin to define SIP/TEL URIs that will appear in a pull down list when the telephone icon is clicked. I have added support for a multicast URI, but you need to look at the source code for more information. For incoming, you can only join an active meeting. When the SIP invite is received, the SIP URI telephone number is matched against all active meetings and SIP endpoint audio is added to conference audio mixer.

When the openfire meetings audio mixer is enabled, audio quality is reduced to G711 ulaw in order to manage the CPU load on the server while mixing the audio streams. This will affect the webrtc user experience in the browser. If you do not use an audio mixer, then your SIP endpoint (phone, softphone) will only work if it supports multiple audio streams and has a client side audio mixer like the Jitsi desktop app.

How do I record a meeting?

Enable meeting recording (audio/video/screen share) and specify location of media files/folders from openfire meetings settings. Video is recorded only in linux 64 servers. On everything else (windows, 32 bit servers), only audio is recorded.

The PDF viewer does not work or is very slow. How can I fix this?

The PDF rendering engine is implemented in JavaScript. Not sure it can go any faster. The key would be to use simpler PDFs. I save my powerpoint presentations as PDFs and get a good performance from them. Also, the use of JavaScript creates a cross-domain issue and therefore the PDF file is fetched by the server and not the web browser. You need to make sure the Openfire server has network access to the PDF web server. If the PDF is being fetched from the Internet, then your OF server needs access to the internet as well.

I can see Openfire Meetings has an API. can I use it from my web applications?

To do this, take a look at the demo video conference application (index.html) using the api in the “api” folder of the ofmeet plugin. You need to do the following things:

• Include “ofmeet.css” to get the correct styling and positioning of the video divs. The current  behaviour is to use the full screen and auto-repostion/resize as participants leave or go. Please note that the api does not include the toolbar and all its features. Your application must implement those via api calls. Only the UI for the main video window and film strip for participants are implemented in the api.
  
  
• Include “/ofmeet/config”, the generated script file which contains all the settings and server config data packaged as a global object called “config”
  
  
• Include “ofmeet-api.js” which contains all the javascript for openfire meetings  (including all dependencies like jquery) encapsulated in a global object called ofmeet. This ensures there is no name clashes with your own application if you add ofmeet-api.js directly to your application without using an iframe.
  
  
• Write your application using the config and ofmeet objects as follows:
  • Create event handlers for all ofmeet events. See index.html for the most common. All others can be found by looking at the ofmeet-api.js code for document.trigger calls.
  • Trace the application flow in index.html starting from jquery document.ready event. First thing to do is call ofmeet.ready(username, password). Handle ofmeet.ready event and call ofmeet.connect.
  • Handle ofmeet..connected and join the conference room with ofmeet.joinRoom(roomName, audioVideoFlag).
  • You can exit the conference with ofmeet.leaveRoom(). Make the whole UI visible/invisible with ofmeet.visible(flag).Toggle audio/video mute with ofmeet.toggleVideo() and ofmeet.toggleAudio()

Wouldn't it be great if your favourite XMPP Server was almost about to make a major release? Well, stop imagining, and start downloading, because Openfire 4.0.0 has reached Beta status!

This means that while we're quite sure there's bugs to be found, we believe the server is stable enough to use for formal testing and careful use in non-critical production environments (which means, basically, we're using it on igniterealtime.org itself and our own servers).

So if you're keen to help make this the best Openfire release we've ever made, then download, install, and keep us posted in the chatroom at open_chat@conference.igniterealtime.org

Download from here: Ignite Realtime: Beta Downloads

A Change Log is here: Openfire Changelog

And SHA1 checksums are below:

Enjoy!

The Ignite Realtime community has just released Spark 2.7.4 and it can be downloaded from Ignite Realtime: Downloads.

This update is a lot about updating translations (Russian, Chinese (Traditional), Lithuanian, etc.) and making some hardcoded parts of GUI available for translation. Also an old patch for proxy connection has been applied in this version, but it looks like Spark is ignoring proxy settings and connects directly instead. Needs more live testing (please report in the forums).

For a complete list of changes please check the official Spark Changelog

We are glad to receive patches from contributors on igniterealtime/Spark · GitHub. 6 of them included in this release. Thank you, guusdk (Guus der Kinderen) · GitHub, idma88 (Dmitrii Ivanov) · GitHub and gabriellelee. We hope more developers will find out about this and other Ignite Realtime projects and contribute patches.

Here are sha1 checksums for the downloads:

c8531c2a25b6f707df1ca95bae33f7c992c8376e  spark-2.7.4.rpm

7e250a2f41d9c218929a601d389382f8ce0288b7  spark-2.7.4.src.rpm

a9718810e11947df15df208314713a1c93bbac8f  spark_2_7_4.deb

7eae89de422a99588d1dc51bf9f07a34a5b6a1a6  spark_2_7_4.exe

364f716457d6070bbd5a4f531d531f97ffc80bed  spark_2_7_4.tar.gz

b97ad875edeae2c12e4b09b849f2f500293da81a  online/spark_2_7_4_online.exe

[Voice Chat] Voice chat is broken since the migration from proprietary JMF to free FMJ framework and there is no fix in the works. Spark project lacks good java developers.

[Mac OS X] There is no installer for Mac OS X (installer building system has issues with Mac OS X, also Spark has too many major issues on this platform).

[Linux] Linux version has issues with menu not showing up and chat window not opening normally on the latest Ubuntu version. Also flashing plugin is not working on Linux systems.

Almost 4 weeks ago, we released a beta of Openfire 4.0.0. Now, it's time for the real thing.

Openfire 4.0.0 is now available for immediate download. The Beta has been run in production by developers for some time, and we believe this is the best ever Openfire release, containing many new features and fixing dozens of bugs. It marks the culmination of a real resurgence in Openfire development.

We advise all users to plan on upgrading; the 3.10 branch will not be receiving anything other than critical fixes. The new 4.0 branch will be the focus for bug fixes, and the trunk is now 4.1.

Many of the plugins available from Ignite Realtime: Openfire Plugins will only work on 4.0.0, and will therefore require this upgrade.

You can download the new release from: Ignite Realtime: Downloads

A changelog is here: Openfire Changelog

SHA-1 Checksums are:

The Ignite Realtime community has just released Spark 2.7.5 and it can be downloaded from Ignite Realtime: Downloads.

This is a hotfix release to fix the issue with only first offline message showing upon login when using Openfire 4.0.0 as a server (or any other server which has dropped support for deprecated XEP-0091). Thanks a lot to csh  for providing a quick fix for this issue.

At the same time speedy3k  was tackling the long standing issue with an installer for Mac OS X. So we are adding that into this release. Please report issues with the installer at New Spark installer for Mac OS X needs testing. There is also a link in that thread to the list of issues in Spark when using on Mac OS X. You can test and report which issues are still present. The installer is not bundled with JRE yet, so you need to install Oracle's latest Java on your system.

Also thanks goes to another translator - swiftech · GitHub . This time for Chinese Simplified. And, of course, we thank akrherz  for his continuous support fixing the builds and providing installers for the release.

We also wanted to bring another major update for this release. Updating Smack library to 3.4.0 (from 3.3.1). But it brakes Fastpath plugin in Spark as Fastpath's part has been moved to smackx-workgroup.jar in that version. Waiting for a patch to fix that, so we can move on to even newer versions of Smack.

For a complete list of changes please check official Spark Changelog

Here are sha1 checksums for the downloads:

4189825dfea042828fc4f9d866454c106b79c01f  spark-2.7.5.rpm

75c69f904b12014d13ace57512ee69c51110ca91  spark-2.7.5.src.rpm

15468ac5a0422554510a0a0098e8457a3f03dd6a  spark_2_7_5.deb

74431214ea99949e047fa7d07bd95725f2f17a3b  spark_2_7_5.dmg

354155349298f0f81ce63de056753b80172a4a24  spark_2_7_5.exe

52e6f8e60ae5357a410e28654763f856e8e6cd8c  spark_2_7_5.tar.gz

8a19459c92957558358a5e5372216dc389f9dd5f  online/spark_2_7_5_online.exe

[Voice Chat] Voice chat is broken since the migration from proprietary JMF to free FMJ framework and there is no fix in the works. Spark project lacks good java developers.

[Mac OS X] There is now an installer available, but there are probably many other issues in Spark on this platform.

[Linux] Linux version has issues with menu not showing up and chat window not opening normally on the latest Ubuntu version. Also flashing plugin is not working on Linux systems.

We've had quite some feedback from our recent 4.0.0 release. As is to be expected in a release that has many changes, some issues sneaked in. To address most of them, we released Openfire 4.0.1 today.

This release contains various changes, but most importantly fixes problems introduced in 4.0.0 related to LDAP and certificate store management. The complete changelog is available here: Openfire Changelog

You can download the new release from the download section on the IgniteRealtime.org website: Ignite Realtime: Downloads

The SHA-1 checksums for the various downloads:

I've just released and uploaded Smack 4.1.6 and 4.2.0-alpha3 to Maven Central.

Smack 4.1.6 contains a few important bug fixes for Smack's stable branch: 4.1. The changelog can be found here: Smack Changelog

The third alpha version of Smack's upcoming development branch contains a ton of fixes and new features. Adventurous users are encouraged to explore the API improvements. But, as the version name suggests, don't use an alpha version for production deployments. A provisional and incomplete list of Smack 4.2's highlights can be found at Smack 4.2 Readme and Upgrade Guide · igniterealtime/Smack Wiki · GitHub

The Ignite Realtime community has just released Spark 2.7.6 and it can be downloaded from Ignite Realtime: Downloads.

In this release more patches went into fixing Mac OS X version (issues with Preferences, File transfer, etc.). Thanks to speedy for working on this. Also as part of fixing issues on Mac we have applied an experimental version of Libjitsi patch by cstux (Voice Chat module). We haven't been able to test, if it works better (or at all). So waiting for a feedback on this in Updated Voice Chat module testing. Thanks to Alexander198961 · GitHub for his patches fixing broadcast and other issues. Waiting for more from him.

For a complete list of changes please check Spark Changelog

Here are sha1 checksums for the downloads:

3ba0067ea2c106bbd78e97ac7b6cf8a01ebc648e  spark_2_7_6.dmg

8a666aaddbb492e1018746cb8c69722f15464a70  spark_2_7_6.exe

69e0323f326552b717e35dd48df1280e965db3d7  spark_2_7_6_online.exe

f61120bf954435a84d9bac23cac21a8f0467cff8  spark_2_7_6.tar.gz

2af77b0c70202636942d0648836a218c8aa8cba1  spark-2.7.6.rpm

eaf3486bb24876905ade7725d92f560dfd2d2a86  spark-2.7.6.src.rpm

[Voice Chat] Voice chat module has received an experimental patch and still needs testing and probably not working correctly.

[Mac OS X] Installer is now bundled with Java JRE, so it is easier to start using it and many issues has been fixed.

[Linux] Linux version has issues with menu not showing up and chat window not opening normally on the latest Ubuntu version. Also flashing plugin is not working on Linux systems.

The Ignite Realtime Community is pleased to announce the 4.0.2 release of Openfire.  This release signifies our ongoing effort to produce a stable 4.0 series release while continuing to work toward a 4.1 release.  A changelog of issues fixed indicates 9 issues resolved with hopefully the issue of stale/ghost client sessions being resolved.

As always, please report issues in the Community Forums and you can download this release from our website.  Here are the sha1sum's for the downloads available.

As a reminder, Openfire's source code and development can be found on Github and an active developer discussion occurs within our open_chat@conference.igniterealtime.org groupchat.  Please consider helping out with Openfire's development!

Thanks  to the sponsorship of Marc Laporte  and the effort of Guus der Kinderen, we have improved the documentation of Openfire Meetings.

There is still a lot more work to be done, but we are making good progress. You can find it here. Please have a read if you use this Openfire plugin.

The latest version of the plugin can be found here.

Two new releases of Smack have just been pushed to Maven Central.

Smack 4.1.7 fixes a few bugs. One noteworthy bug is that on certain platforms Smack's setEnabledSSL(Protocols|Ciphers) had no effect. More information about the fixed bugs can be found in the Release Notes.

The careful reader may noticed that this is the first beta release of Smack 4.2. Which means that Smack 4.2 just entered the beta phase. My rough timeplan is to release Smack 4.2 in 6 months: starting with 3 months long beta period now, followed by 3 months of release candidates. But as all schedules in the software industry, take it with a grain of salt.

The Ignite Realtime community has just released Spark 2.7.7 and it can be downloaded from Ignite Realtime: Downloads .

This is another minor release marking exactly one year since Spark project reboot (yeah, we also like to have Anniversary Update ). There are a few small fixes and updates in this release (as a regression with Idle presence, fix for OTR plugin, etc.). I want to use this chance to look back at the last year. Spark had 7 more releases since the 2.7.0 during that time. 100 tickets have been resolved. Some old patches have been applied (laying around in the forums and the tracker for years). We have also received new patches from around 10 new contributors. Which is great! We see that Spark project is often forked on GitHub, so we hope more developers will forward their patches and new features to the main project. There is also an official Wikipedia page for Spark now (and additional 6 languages linked to it) in hope to increase awareness of this project.

Here are the contributors to this release (besides myself):

Alexander198961 · GitHub

speedy

kilida (kilida) · GitHub

rarog · GitHub

For a complete list of changes please check Spark Changelog

Here are sha1 checksums for the downloads:

0d375c422bd86f9c8ded5484a173256871abaa26  spark_2_7_7.dmg

9f737012121432c20ca7db427051f29cbfca9734  spark_2_7_7.exe

39886c77a4b9821c2a12ea0b7623b9859e62d513  spark_2_7_7_online.exe

c62fe47aa89022b4d784245b833af7893b3e4897  spark_2_7_7.tar.gz

2e23a28d62cd37d6ab4c4a8befd19e765cea3a3b  spark-2.7.7.rpm

5fde7df644950d414bb997f32034a68efeb22cec  spark-2.7.7.src.rpm

[Voice Chat] Jingle (PC to PC) calls are not working at this point, but SIP should be improved.

[Linux] Flashing plugin is not working on Linux systems.

Marc Laporte Jun 1, 2016 9:50 AM

Dele, Guus and myself will be in London for a brainstorming and development sprint on Openfire Meetings.

This is in the context of Openfire Meetings within WikiSuite, and we will make improvements, useful to all the community (even if you don't use the Openfire Meetings plugin nor WikiSuite)

Here are some examples of things we could be working on: WikiSuite | Openfire Meeting and Jitsi Meet development

If interested in participating, please contact me.

Best regards,

M ;-)

Please be aware that over the next few days, the IgniteRealtime community will be moved to new server environment. As a result, new IP addresses will be used for the XMPP domain, this website and the Atlassian stack (JIRA, Bamboo et al). The community forum (everything under the "community" tab of the website) is not affected by the migration.

We plan to move gradually, a few services at a time. The migration will start in the coming few days, and will continue for some days to come. You can expect some downtime, but that should be limited. Watch this space for updates!

So, why are we moving in the first place? I've addressed this previously in a thread on the community, from which I'll cross-post the more interesting bits here.

Jive Software has expressed their intention to reduce the sponsoring of the hosting of this community. What will be discontinued specifically is all of the Contegix-based hosting, which includes the servers that run the igniterealtime.org website, our Atlassian stack (Bamboo, JIRA), our XMPP domain, and related tooling. The forum functionality that you're using to read this message is based on the Jive cloud, which is different from the Contegix-based hosting. Jive Software has expressed that we're welcome to continue to make use the Jive cloud-based solution for the foreseeable future.

After Jive established the community back in 2006, they continued to put in a lot of effort to maintain and support both the people and software. On top of that, they've been incredibly generous in regards to spending money on development and hosting - looking for suitable replacement for the hosting of this community has made us more aware of exactly how generous, too! But we accept that over time, Jive's business has moved away from XMPP and Instant Messaging. Most of our contacts within the company have also moved on by now, which resulted in where we are today - pretty much distinct entities. It's no wonder that Jive re-evaluated their support. We are extremely grateful for all of the time, effort, and money that we received from them in the past. Jive is also actively working to end our cooperation well, offering support and even donation of the existing hardware, as well as plenty of notice. Kudos.

After Jive expressed their intentions, we've been actively searching for a new home for our community. We have had some great offers, more than we would have imagined (thank you!). We eventually decided to accept the generous offer from John Atherton, of Surevine Ltd, who have offered to help us by hosting our entire environment in Amazon, as well as support us during and after the migration. I am inviting Surevine to write a posting here to further introduce themselves.

As for the migration: over the past few weeks, several of us (both in the community and within Surevine) have been putting in quite some time to prepare for everything. An important part of the move is rebuilding infrastructure that was put in place over a decade ago. This has been an interesting exercise in spelunking...  We've had to make some adjustments left and right, but we feel that we're good to go. Still, we'd like to ask you to be on the lookout for missing functionality. Although we're trying to cover all bases, a lot of nuts and bolts were added over the last few years. We will have missed one or two, or we might have believed some to be non-important while they were not. Feel free to pop into the community chat or leave a message here if you think we missed something!

Thanks for your patience while we move IgniteRealtime to its new home.

Starting with b91978dcc4ae partial support for the IoT XEPs was added to Smack. The XEPs consists, amongst other XEPs, of

• XEP-0323: Data
• XEP-0324: Provisioning
• XEP-0325: Control
• XEP-0347: Discovery

The XEPs are in experimental state, which means changes to them are possible.

Smack does currently only support a partial set of the mechanisms specified, especially when it comes to Data and Control. For example only boolean and integer values can be read and written But support for more data types can be easily added.

The IoT API for those XEPs is available in the latest snapshot builds of Smack, which are available via Maven Central's snapshot repository.  A quick start guide can be found here.

The development of the API was sponsored by Clayster.

Clayster creates technology to secure trust in the transactions between physical and digital entities, and strives to be that generic foundation for your physical assets digital life.

Clayster has an IoT discovery and provisioning platform supporting XEP-0347 and XEP-0324. The platform is available for those who are interested to explore XMPP and IoT further.  If you don't want to run your own infrastructure, Clayster is able to provide an XMPP Server and the discovery/provisioning platform for you. Feel free to reach out to rikard at clayster.com if you are interested to learn more about using XMPP for your next IoT project. www.clayster.com

I've just uploaded Smack 4.1.8 and 4.2.0-beta2 to Maven Central.

Smack 4.1.8 fixes a few minor issues and is expected to be the last release of the 4.1 branch. As always, Smack releases with the same major and minor version numbers are drop in replacements. Ideally you just need to change a single variable somewhere in your build system.

Smack 4.2.0-beta2 is the latest beta of Smack's current development branch. Notable additions include support for XEP-0313: Message Archive Management (MAM) and the IoT XEP series.

The Ignite Realtime Community is pleased to announce the 4.0.3 release of Openfire.  Openfire is a cross-platform real-time collaboration server based on the XMPP (Jabber) protocol.  This release signifies our ongoing effort to produce a stable 4.0 series release while continuing to work toward a 4.1 release. A changelog of fixes is available and indicates 14 issues resolved.

Note: There was an unfortunate and complicated problem with the distributed 4.0.2 .deb Openfire installer.  If you had troubles with it and reverted to 4.0.1, we hope that you try 4.0.3 now.  See OF-1116 for some more details.  Also, if you are an experienced Debian/Ubuntu packager, we would certainly love your feedback on how the .deb package for Openfire is generated and distributed.

Additionally, this update contains an updated truststore. This truststore is used by Openfire to secure remote connections.  If you are using an installer and have manually updated this file in the past, it is likely that the installer will not overwrite your changes with the new truststore.  Please review your resources/security directory after install and rectify differences you may find.

As always, please report issues in the Community Forums and you can download this release from our website.  Here are the sha1sum's for the downloads available.

Update 19 August 2016: A problem was found with the 32bit RPM containing a 64 bit JRE.  This artifact has been refreshed on the website for download. Also Binary (tar.gz) package has been replaced to include the usual binaries.

As a reminder, Openfire's source code and development can be found on Github and an active developer discussion occurs within our open_chat@conference.igniterealtime.org groupchat.  Please consider helping out with Openfire's development!  We can use help in about all areas of development, but especially:

• experienced packaging developers to improve the install/upgrade experience on various platforms
• developers interested in transitioning Openfire to Maven
• testing of bamboo generated builds

Thank you for your interest in Openfire!

The Ignite Realtime community has just released Spark 2.8.0 and it can be downloaded from Ignite Realtime: Downloads.

This is a major release marking the end of support for Java 7 (which has reached the end of life state more than a year ago). Full Spark installers have already been bundled with Java 8 for some time. Online installer won't work with Java 7 starting with 2.8.0 version. We recommend updating to Java 8. Underlying Smack library has been updated to the latest version in this release. Roar plugin has received new popup control options as well.

There is a huge list of changes in this version. So this most probably has introduced new issues (though we have tried to catch and fix most of them before the release). Please report in the forums, if you find them. Again, please do not post bug reports in the comments of this blog post.

For a complete list of changes please check Spark Changelog

As usually we encourage new developers to join Spark project and provide patches. Those familiar with Smack can join the development easier, as we are now on the current version of it (4.1.8 at the moment of this release). Patches can be attached in the forums or submitted as PRs on GitHub.

Here are the contributors to this release (besides myself):

Wolf  updated Roar plugin to have separate settings for group chat and keyword matching popups, added system style popups

Alexander198961 · GitHub  added option to save room's password, added URL support to admin's broadcast dialog

Леонід  added Ukrainian translation

nicoben (Nico Ben) · GitHub  updated Italian translation

speedy  fixed failed login process with self-signed certificates, updated Substance skin library, fixed an issue with idle on Windows 10 lock screen

Daryl Herzmann  fixed Debian build

We owe Guus der Kinderen  a separate mention. Guus has done a huge job of updating Spark to the current Smack version, which contains a lot of bug fixes, security patches and new features. He has also fixed many other issues along the way. Such as group chat window size issues, room occupants presence management, annoying word wrapping issue with long text lines, SSO/GSSAPI problems, etc.

Important information for SSO (Single Sign On) users, if they are using SRV records:SSO (Single Sign On) configuration changes with Spark 2.8.0

UPDATE: Important information for those having login issues with 2.8.0:Login issues with Spark 2.8.0

[SIP phone] SIP plugin is not working since the Smack 4 update. We hope to have it fixed for 2.8.1.

[Voice Chat] Jingle (PC to PC) calls are not working at this point.

[Linux] Flashing plugin is not working on Linux systems.

Here are sha1 checksums for the downloads:

6fa1265e7def8800e0a4356bd1b7d8cf58bb85f8  spark_2_8_0.dmg

741c20d9141c88ecde08d60fbc11145887d32573  spark_2_8_0.exe

b76e36da81469561fdad4a227fa4ad68d792ca7b  spark_2_8_0_online.exe

e2fcdddb4e84f6f1abe9d62a39aa0c7c9e06d814  spark_2_8_0.tar.gz

a772028ba10db2084ea7e2b7b1fb408803c77a5b  spark-2.8.0.rpm

38ca0d9ab5ccd7d61be03b702a0abd5c8939ada5  spark-2.8.0.src.rpm

fba8705d54f49bceb62f19a30348482f9bbeacfb  spark_2_8_0.deb