Upgraded my Openfire server to the latest version this morning (5.1.0), and then found that none of my users could connect to the server. Everyone was constantly reconnecting and disconnecting, getting stream errors. The server logs reported no errors, everything running smoothly.
Downgraded back to 5.0.5, restored the database and openfire folder from backup, and now we're up and running again.
I think that there was a bug in Ignite Realtime Discourse, publication has been removed ^^ Users and devs request informations about SCRAM in more SCRAM-SHA-1, the missing SCRAM-SHA-1-PLUS point from RFC6120 (March 2011) and SCRAM-SHA-256(-PLUS): SCRAM-SHA-1-PLUS (RFC5802 + RFC6120) SCRAM-SHA-256(-PLUS) (RFC7677 + draft-ietf-mile-xmpp-grid) Why not SCRAM-SHA-512(-PLUS). Source: Salted Challenge Response Authentication Mechanism (SCRAM): SASL and GSS-API Mechanisms: https://tools.ietf.org/...
Openfire deployments have been running in the wild for a *long* time.
Some started when Java 5 was current, Docker didn't exist yet, and IPv6 was still "future tech".
As we prepare the Openfire 5.1.0 release, We'd love to hear your stories: What's the oldest Openfire deployment that you still run?
https://discourse.igniterealtime.org/t/what-s-your-oldest-openfire-deployment/96473
As we’re preparing the upcoming Openfire 5.1.0 release, I’ve been spending a lot of time looking at parts of the codebase that have been around for a long time. Some of them date back to assumptions that were perfectly reasonable when Java 5 was current, IPv6 was still considered “future tech”, Docker didn’t exist yet, and “cloud-native” wasn’t a phrase anyone but meteorologists used. Yet somehow, Openfire deployments that started in those days are still running today. That got me wondering: ...
We have released Openfire 5.0.5, our open source real-time communications server! This is a maintenance release, bringing some interesting bug fixes and library upgrades. Read more about this release in our blog! https://discourse.igniterealtime.org/t/openfire-5-0-5-release/96468
The Ignite Realtime community is pleased to announce a new release of Openfire, version 5.0.5. The full changelog has more details with the highlights being bug fixes and bundled library updates whilst we continue to work on an upcoming 5.1.0 feature release. You can obtain the new version of Openfire for your platform from its download page. The sha256sum values for the release artifacts are: 4ba9b6476efefc54378c0fd4a2a402177fd94bc11512354db887eb446f37f211 openfire-5.0.5-1.noarch.rpm 3a870e...
This is nice. Hotel room with an open fire!
We are exploring support for #MariaDB, #Firebird and #CockroachDB in Openfire. This includes early pull requests and discussion of trade-offs, maintenance cost and real-world demand.
We would love community input before proceeding further.
Is this valuable, or more trouble than it is worth?
I have recently started experimenting with adding support for three additional databases in Openfire: MariaDB, Firebird and CockroachDB. This work is still exploratory. Before committing to this direction, I would like to get a better understanding of whether this is actually valuable to the Openfire community. I have prepared initial pull requests for each database: MariaDB: https://github.com/igniterealtime/Openfire/pull/3240 (OF-3239 in our issue tracker) Firebird: https://github.com/igni...
#FOSDEM was absolutely WILD! 😻
🤯🤯🤯 Got a hand-made #XMPP developers post card with a personal mention!
🤯🤯 Got a "Thanks Ge0rG, keep up the good work!" while walking the food mile!
🤯 Met an IRC contact from 25 years ago, @olbohlen ("Apparently I'm the only operator of #OpenFire on #Solaris") and connected him to @guusdk who brought stickers and hugs!
🤯 Accidentally met an IRC contact from 20 years ago
🤯 Accidentally met an #FDroid member iRL
🤯 Met @sven (#fail0verflow) after 20 years
Gυιdσ Kσѕтσиѕ
Neustradamus :xmpp: :linux:
DeadTOm 
Ignite Realtime News
Greem (Graeme. Not Graham!)
Ge0rG
Ivi Choc