The past weekend some members of the XMPP community gathered in Düsseldorf to work on the next iteration of the OMEMO End to End Encryption Specification. All of us agree that the result - version 0.4 of XEP-0384 - is a huge step forward and better than ever! https://blog.jabberhead.tk/2020/03/10/omemo-specification-sprint/
If you are a college student and want to get payed to become a part of a great open source project that deals with open standards, check out the ideas page: https://wiki.xmpp.org/web/GSoC/2020/Project_Ideas
You can also propose your own awesome project idea!
Dino 0.1 is released! 🎉
Dino is a secure and open-source application for decentralized messaging. It uses the XMPP (“Jabber”) protocol and is interoperable with other XMPP clients and servers. We aim to provide an intuitive, clean and modern user interface.
Release blog post: https://dino.im/blog/2020/01/dino-0.1-release/
Following last years tradition we'll have a #fdroid meetup at #36C3 on the day 1 at 1400.
Last year we had a room with 12 seats and 60 minutes, this year we'll have a lot more space at #cbase and 90 minutes 🙂.
There will be lots of stickers. See you all there.
My talk got accepted for #fosdem! 🎉
Multi-user chats are often divided into two use cases: Groups and Channels. In Groups you talk with specific people about varying topics, while in Channels you talk with a changing set of people about a specific topic.
Dino displays a list of member names as the default Group name and uses member avatars to generate a default Group avatar. Both features wouldn't make sense in a Channel with a continuously changing set of members. #Dino #XMPP
Converse.js 5.0.3 has been released which patches another vulnerability. Please update ASAP (Thanks and sorry for the quick succession of releases!)
Support for #Jingle file transfer over #SOCKS5 was merged into #Dino. SOCKS5 enables data transfer without an intermediary but also supports transfer via a server if a #firewall prohibits direct transfer. Data transfer over the #XMPP stream ("In-Band-Bytestream") has an overhead due to encoding, but serves as a fallback if http file upload and SOCKS5 fail.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!