Using #xmpp is simple, secure and easy. Just create an xmpp account, install an xmpp client, login and start chatting.
Join us tomorrow at XMPP Office Hours 📢 for a talk by Conversations developer Daniel Gultsch on verifying A/V calls with OMEMO at 17:00 UTC (19th of March '21)
Join here: https://socialcoop.meet.coop/sam-pku-dud-niv
You also would like to give a talk? More info at:
Our next virtual #Berlin #XMPP meetup will take place on Wednesday, 18:00 CET. We'll give a short introduction to #OpenPGP for XMPP (#OX), followed by a discussion with one of the XEP authors and various implementors:
The video conference URL will be announced in our public channel:
OK, time for me to make an apology.
I hadn't used XMPP for quite a while. While I liked it last time I used it there were issues keeping connections and the clients were less than stellar.
While the desktop clients for Linux are still a little shaky I can recommend Quicksy (thank you @moparisthebest for the recommendation).
I've been crabby when people recommend XMPP because I didn't realize that folks have taken XMPP from an early 21st century protocol to a joy to use.
Today, we released eturnal 1.2.0, which adds a module for logging STUN/TURN stats to InfluxDB (contributed by Marc Schink): https://eturnal.net
After testing Siskin and Monal for a few days, my impression is that XMPP is now way more usable on iOS than it was back in the days. Many thanks to @tigase for their great work on Siskin IM.
Today, we released version 1.0.0 of our new STUN/TURN server:
In case any Erlang people happen to be interested in straightforward support for systemd's notification/watchdog features:
XMPP@home - 9 June 2020
The XMPP Newsletter covering the month of May 2020.
Thanks for everyone's feedback!
During our next (virtual) XMPP meetup on Wednesday, 18:00 CEST, Daniel Gultsch and me will give an introduction to the technologies used for A/V calls with XMPP. Topics discussed will include Jingle, ICE/STUN/TURN, (S)RTP, and WebRTC. The meetup will take place on Jitsi Meet, see:
We'll also be streaming this meetup live to YouTube, so if you participate, you will be recorded. If you'd prefer to just listen, please use the YouTube stream:
Time required to fix an average bug in #erlang software: 10 minutes to code the fix, 20 minutes to write the commit message, 30 minutes to wait for the test suites to complete, 60 minutes to run Dialyzer for static type checking. (Yes, Erlang people, it's just a few seconds if you don't keep messing up your PLTs like I do.)
Metalhead.club is a Mastodon instance hosted in Germany and powered by 100% green energy.