#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
#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.
Idk .. I mean, you have:
@dino
@gajim
@Goffi ( #Libervia )
@jcbrand ( #ConverseJS )
@kaidan
@Monal
@monocles
@movim (which is a social network in itself)
@profanity
@prose
Server wise you have:
@ejabberd
@prosodyim
@tigase
@snikket_im
.. the catch all: @news ( for #Openfire, #Spark, #Pàdé and #Smack )
and also
@micahilbery yes, I self host #OpenFire (@news) and use @monocles on android, and it works nicely. If you want a chat about it, lmk!
@HeavenlyPossum NIMBY liberal Boomerism will be the death of us all.
Take control of your digital sovereignty with Openfire! 🌐
Discover how this open-source, XMPP-based platform for instant messaging, group chat, voice and video calls, and file sharing can secure your data, enhance privacy, and offer unmatched customization. 💬🔐
#DigitalSovereignty #Openfire #DataPrivacy #SecureCommunication
https://www.igniterealtime.org/support/articles/whitepaper_digital_sovereignty.jsp
#Openfire 5.0.1 has been released (#XMPP / #XMPPServer / #Jabber / #Java / #IgniteRealtime / #Wildfire / #JiveMessenger) https://igniterealtime.org/
🚀 Openfire 5.0.1 is out! This update fixes several issues found in the 5.0.0 release that we did last week. Check out the blog post for more details: Openfire 5.0.1 Release #Openfire #XMPP https://discourse.igniterealtime.org/t/openfire-5-0-1-release-our-100th-maybe/95667
#XMPP is the gold standard for interoperability. Its ability to connect projects from different creators is unparalleled, making it the go-to choice for seamless communication.
Community member Luke wrote a guide on configuring #Openfire to work with #Slidge.
Slidge is a gateway designed to connect you to chat networks like WhatsApp, Telegram or Matrix. It acts as a bridge, allowing you to interact with your contacts directly from your single, preferred XMPP client.
#Openfire 5.0.0 has been released (#XMPP / #XMPPServer / #Jabber / #Java / #IgniteRealtime / #Wildfire / #JiveMessenger) https://igniterealtime.org/
@arawa
Une très bonne chose effectivement et si je peux me permettre, il y a une belle avancée côté #xmpp avec la version 5 de #openfire 👏🍾 https://igniterealtime.org/projects/openfire/
Exit jitsi, les pb avec #firefox... pour des #videoconf, #conf...bref si tu veux remettre totalement la main sur tes communications 👌👍 @Framasoft @aldil @plossra_a @apell @OSBA
@claude
#Openfire 5.0.0 Beta has been released (#XMPP / #XMPPServer / #Jabber / #Java / #IgniteRealtime / #Wildfire / #JiveMessenger) https://igniterealtime.org/
🚀 Exciting update! Openfire Pade plugin v1.8.4 now supports AV1 codec! 🎉 While upgrading Jitsi Meet code remains challenging, this release brings improved P2P call performance. 📈 Check it out and consider self-hosted Jitsi Meet for larger groups. 🔗 #Openfire #JitsiMeet #AV1Codec
https://discourse.igniterealtime.org/t/version-1-8-4-of-openfire-pade-plugin-released/95434
Conversations 2.18.2 is available on Google Play and has client side mitigations for a server side security issue that was recently discovered and fixed in #ejabberd¹ and #OpenFire²
Go update your server. But just in case that takes a minute Conversations has your back too!
This release also fixes an issue with restoring (importing) backups on recent Android versions.
¹: https://www.process-one.net/blog/ejabberd-25-04/
²: https://github.com/igniterealtime/Openfire/pull/2761
Hong Kong Directors Seek Global Partners for Action-Disaster Hybrid ‘Open Fire’
#Variety #Asia #Global #MarketsFestivals #News #Haf #HongKongFilmart #OpenFire
https://variety.com/2025/film/news/open-fire-hong-kong-haf-1236340164/
@drq @sam @daniel While XMPP is definitely behind for the team chat use case, as at least in my corner we have focused on private chat, you have some outdated info.
XEP-0313 enables fetching arbitrary messages by specific ID, ID-ranges and time ranges, so links to specific messages should be possible. Messages can be kept as long your database can handle it. Even full text search is implemented in #Openfire according to @guusdk https://logs.xmpp.org/xsf/2022-05-15#2022-05-15-cff31e4b7fc5c30b
@pixelschubsi I think you are misunderstanding what I am saying. *I* understand that #Skikket is a server and needs to be set up, but what I keep hammering on is that a typical user won't have the foggiest clue how to do that with any of the current #xmpp server programs. A typical user wants to install an app and get on with their life, and yes many of them will just blindly enter their phone number when requested, but not all will. And again, I agree that if someone else wants to set up a server and be your tech support it can be a breeze for you, although if they are not all that Linux savvy they may not care much for the current server choices.
The only time I ever had an xmpp server that was reasonably easy to install and use was #OpenFire, and that was only because it was installed using a script that actually set up several programs at the same time. But that was MANY years ago (probably more than 15, maybe 20 years) and was before certificates became a thing on xmpp servers. But as I recall it had a decent web interface (or maybe that was pa\rt of that package of programs), anyway I only ran that package for maybe two or three years and then that project died. But even that would be more than a typical user wants to deal with (and yes I had a nodding acquaintance with Linux even back then, but I don't know a whole lot more about it today than I did back then, it mostly frustrates the hell out of me whenever I encounter some problem).
Almost nobody running a xmpp server wants to invite anyone and everyone to use it, but even if those open servers exist, few people have heard of them and in a group of friends or family someone would surely object that they know nothing about that server, it could go down without warning at any time or the operators could be intercepting messages, etc. #Signal, at least, is big enough that it's probably not going to fall of the face of the earth without warning (and if it does the tech press will be telling you why and if it's likely to come back) and it does have a privacy policy. So running your own server is preferable and my point all along is that they need to make that MUCH easier for non-nerds. If the server uses text-based or yaml configuration files you are lost already. Users want web-based configuration (think something like Home Assistant, which I do not use but I have noticed it is getting very popular, which never would have happened if they did not have that superb web interface).
Snikket may in fact be most of the way there, but as far as I know it is not cross platform, and it could definitely stand to have a better introductory video than that one I was watching. BUT you could have the easiest server in the world to install and it's not going to motivate a user that wants to be up and running in two or three minutes, using a platform their friends and family have at least heard of. And yes I know, those are the kind that will happily give up their phone number, and it burns me to no end that people don't care about that, but they don't. And then if you have xmpp servers that also require that, you have really just taken away any reason someone should prefer xmpp over Signal.
In my mind before you go promoting xmpp as an alternative to Signal you need to have a server that preferably is cross-platform, but at the very least is drop-dead easy to set up (you should be able to show how to set it up and add users in a video of 3 minutes or less, 5 tops), and it should not require the user to know anything about certificates. It should not require a domain if you just want to use it locally, or tell you how to use it with a free service such as freedns.afraid.org or DuckDNS or something like that. It should not tell you that you need to use any paid service (Signal is free!). It should not assume you need any kind of group chat (maybe you just want one-to-one messaging) but it should let you send images and files to another user. It should not assume you want to federate with any other xmpp server (in case you are running a private friends/family server). In other words it needs to be as easy to work with as something like Home Assistant.
And for the people that absolutely will not set up their own server (and don't have a tech-savvy relative) then there needs to be a service they can use THAT DOES NOT REQUIRE A PHONE NUMBER (otherwise why not just use Signal?) and that has the ability to scale and that has a decent privacy policy (and it will still need to reach critical mass before people will use it). And of course that all costs money (again, Signal is free!). We actually used to have something more or less like that in the form of Google Talk but they shut that around 2016 if I recall correctly.
Anyway those are the hurdles the xmpp proponents need to think about and overcome if they really want to "sell" anyone outside their immediate friends/family circles on using xmpp. Speaking from experience, we used to have an xmpp server set up in our friends/family group (using Prosody after that OpenFire setup went away, only because we found some good instructions in some guy's blog that are now no longer online) but as with many things it became harder and harder to deal with and the when the xmpp clients started demanding valid certificates just to send photos and files that just killed it, and everyone went to just using email and then later to Signal. So that is not something I personally would ever want to get back into unless I was pretty certain the process of setting up and running a server had become MUCH easier.
In Yorkshire it is quite cold again
