home.social

#openfire — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #openfire, aggregated by home.social.

fetched live
  1. Openfire 5.1.1 is out! 🎉

    A maintenance release for our open-source #XMPP server, with a focus on PubSub correctness and connection handling. Highlights: fixed excessive memory use from a bloated pubsub subscription table, resolved an IQBind thread-starvation bug, and corrected IP encoding in certificate SANs. 24 issues resolved in total.

    Thanks to everyone who reported issues!

    discourse.igniterealtime.org/t
    #Openfire #IgniteRealtime

  2. Openfire 5.1.1 is out! 🎉

    A maintenance release for our open-source #XMPP server, with a focus on PubSub correctness and connection handling. Highlights: fixed excessive memory use from a bloated pubsub subscription table, resolved an IQBind thread-starvation bug, and corrected IP encoding in certificate SANs. 24 issues resolved in total.

    Thanks to everyone who reported issues!

    discourse.igniterealtime.org/t
    #Openfire #IgniteRealtime

  3. Openfire 5.1.1 is out! 🎉

    A maintenance release for our open-source #XMPP server, with a focus on PubSub correctness and connection handling. Highlights: fixed excessive memory use from a bloated pubsub subscription table, resolved an IQBind thread-starvation bug, and corrected IP encoding in certificate SANs. 24 issues resolved in total.

    Thanks to everyone who reported issues!

    discourse.igniterealtime.org/t
    #Openfire #IgniteRealtime

  4. Openfire 5.1.1 is out! 🎉

    A maintenance release for our open-source #XMPP server, with a focus on PubSub correctness and connection handling. Highlights: fixed excessive memory use from a bloated pubsub subscription table, resolved an IQBind thread-starvation bug, and corrected IP encoding in certificate SANs. 24 issues resolved in total.

    Thanks to everyone who reported issues!

    discourse.igniterealtime.org/t
    #Openfire #IgniteRealtime

  5. Openfire 5.1.1 is out! 🎉

    A maintenance release for our open-source #XMPP server, with a focus on PubSub correctness and connection handling. Highlights: fixed excessive memory use from a bloated pubsub subscription table, resolved an IQBind thread-starvation bug, and corrected IP encoding in certificate SANs. 24 issues resolved in total.

    Thanks to everyone who reported issues!

    discourse.igniterealtime.org/t
    #Openfire #IgniteRealtime

  6. @debacle

    Thats is it, there is no good #foss #xmpp client for #Windows. I run #Openfire as my server with the #ConverseJS package installed but I like #Gajim more for everyday use.

    For me Gajim is the best option at this moment.

    @[email protected] @[email protected]

  7. @debacle

    Thats is it, there is no good #foss #xmpp client for #Windows. I run #Openfire as my server with the #ConverseJS package installed but I like #Gajim more for everyday use.

    For me Gajim is the best option at this moment.

    @[email protected] @[email protected]

  8. @debacle

    Thats is it, there is no good #foss #xmpp client for #Windows. I run #Openfire as my server with the #ConverseJS package installed but I like #Gajim more for everyday use.

    For me Gajim is the best option at this moment.

    @[email protected] @[email protected]

  9. @debacle

    Thats is it, there is no good #foss #xmpp client for #Windows. I run #Openfire as my server with the #ConverseJS package installed but I like #Gajim more for everyday use.

    For me Gajim is the best option at this moment.

    @[email protected] @[email protected]

  10. @debacle

    Thats is it, there is no good #foss #xmpp client for #Windows. I run #Openfire as my server with the #ConverseJS package installed but I like #Gajim more for everyday use.

    For me Gajim is the best option at this moment.

    @[email protected] @[email protected]

  11. 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.

    #XMPP #Openfire

  12. 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.

    #XMPP #Openfire

  13. 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.

    #XMPP #Openfire

  14. 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.

    #XMPP #Openfire

  15. 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.

    #XMPP #Openfire

  16. 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?

    discourse.igniterealtime.org/t

    #Openfire #XMPP #Java #SelfHosting #SysAdmin #OpenSource

  17. 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?

    discourse.igniterealtime.org/t

    #Openfire #XMPP #Java #SelfHosting #SysAdmin #OpenSource

  18. 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?

    discourse.igniterealtime.org/t

    #Openfire #XMPP #Java #SelfHosting #SysAdmin #OpenSource

  19. 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?

    discourse.igniterealtime.org/t

    #Openfire #XMPP #Java #SelfHosting #SysAdmin #OpenSource

  20. 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?

    discourse.igniterealtime.org/t

    #Openfire #XMPP #Java #SelfHosting #SysAdmin #OpenSource

  21. 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! discourse.igniterealtime.org/t

    #xmpp #openfire #release

  22. 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! discourse.igniterealtime.org/t

    #xmpp #openfire #release

  23. 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! discourse.igniterealtime.org/t

    #xmpp #openfire #release

  24. 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! discourse.igniterealtime.org/t

    #xmpp #openfire #release

  25. 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! discourse.igniterealtime.org/t

    #xmpp #openfire #release

  26. 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?

    #Openfire #XMPP #databases

    discourse.igniterealtime.org/t

  27. 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?

    #Openfire #XMPP #databases

    discourse.igniterealtime.org/t

  28. 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?

    #Openfire #XMPP #databases

    discourse.igniterealtime.org/t

  29. 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?

    #Openfire #XMPP #databases

    discourse.igniterealtime.org/t

  30. 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?

    #Openfire #XMPP #databases

    discourse.igniterealtime.org/t

  31. #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

  32. #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

  33. #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

  34. #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

  35. #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

  36. #HealthWarning #CO #poisoning for people having any #openfire in the house!
    A CO-monitor saves lives!
    Early signs of CO poisoning are headache, dizziness, fast heartbeat and glowing cherry-red cheeks. Immediate medical assistance is mandatory, or severe organ/brain damage can happen! CO binds 250x stronger to hemoglobin - the carrier protein in red blood cells - than O2. Hyperbaric O2 (in chamber) or 100% O2 through a mask is necessary to get the CO off the hemoglobin and replace it with O2.

  37. #HealthWarning #CO #poisoning for people having any #openfire in the house!
    A CO-monitor saves lives!
    Early signs of CO poisoning are headache, dizziness, fast heartbeat and glowing cherry-red cheeks. Immediate medical assistance is mandatory, or severe organ/brain damage can happen! CO binds 250x stronger to hemoglobin - the carrier protein in red blood cells - than O2. Hyperbaric O2 (in chamber) or 100% O2 through a mask is necessary to get the CO off the hemoglobin and replace it with O2.

  38. #HealthWarning #CO #poisoning for people having any #openfire in the house!
    A CO-monitor saves lives!
    Early signs of CO poisoning are headache, dizziness, fast heartbeat and glowing cherry-red cheeks. Immediate medical assistance is mandatory, or severe organ/brain damage can happen! CO binds 250x stronger to hemoglobin - the carrier protein in red blood cells - than O2. Hyperbaric O2 (in chamber) or 100% O2 through a mask is necessary to get the CO off the hemoglobin and replace it with O2.

  39. #HealthWarning #CO #poisoning for people having any #openfire in the house!
    A CO-monitor saves lives!
    Early signs of CO poisoning are headache, dizziness, fast heartbeat and glowing cherry-red cheeks. Immediate medical assistance is mandatory, or severe organ/brain damage can happen! CO binds 250x stronger to hemoglobin - the carrier protein in red blood cells - than O2. Hyperbaric O2 (in chamber) or 100% O2 through a mask is necessary to get the CO off the hemoglobin and replace it with O2.

  40. #HealthWarning #CO #poisoning for people having any #openfire in the house!
    A CO-monitor saves lives!
    Early signs of CO poisoning are headache, dizziness, fast heartbeat and glowing cherry-red cheeks. Immediate medical assistance is mandatory, or severe organ/brain damage can happen! CO binds 250x stronger to hemoglobin - the carrier protein in red blood cells - than O2. Hyperbaric O2 (in chamber) or 100% O2 through a mask is necessary to get the CO off the hemoglobin and replace it with O2.

  41. @biline #XMPP never left, see what #ejabberd #prosody #snikket #openfire servers are up to. #Conversations_IM #Cheogram #monoclesChat will serve you as modern clients on #FDroid and #Monal for your fruit devices fans.