Thanks Daniel, that sounds like a sensible approach to me. One thing I am still not entirely clear on is what we mean by an XMPP recipe. Do we mean something that explicitly promotes XMPP itself, or something that promotes specific products built on XMPP.
My original suggestion was to focus on promoting products rather than the protocol. The website currently lists Signal, Threema, Matrix, and Element, and it is not obvious to me why it could not also include Conversations, Quicksy, and Snikket, to name just a few examples. I am also not convinced that we should limit ourselves to a single product. Even if the DI.DAY team ultimately decides not to add all or any of our suggestions to their website, each project in our ecosystem would still benefit from going through the process of preparing a clear and reusable proposition. That material could be used on individual project pages, within our community, and by the communications team when reaching a broader audience. It would of course be a shame if none of this made it onto the DI.DAY website, but I think we would still get a lot of value out of the work regardless. Kind regards, Guus On Thu, Jan 15, 2026 at 1:28 PM Daniel Gultsch <[email protected]> wrote: > On Thu, Jan 15, 2026 at 10:47 AM Guus der Kinderen > <[email protected]> wrote: > > > As a few days have passed and no objections have come up, it seems safe > to say there is general support for engaging with the DI.DAY initiative. \o/ > > > > I want to clarify one point about the idea that we are already "beyond > this" because some XMPP community members have reached out to DI.DAY. I do > not see that as a reason to slow down or stop further effort. If anything, > it makes it more useful to make sure our own members and projects are aware > of what is going on. > > > > One helpful role for the Communications Team could be to spread > awareness of the DI.DAY initiative within our own community. Not everyone > follows the same channels, and not all projects will know about DI.DAY or > about the opportunities it creates. Sharing this information simply gives > people the chance to decide for themselves if and how they want to get > involved. > > > > It is also worth saying that the fact that some people have already > reached out does not mean others cannot or should not do the same. I do not > know what approach was used in the first outreach. Seeing interest from > multiple projects and people can actually be a good signal for the DI.DAY > organizers. > > > > When it comes to showing solutions, I think it can sometimes be better > to lead with individual projects rather than the word XMPP itself. XMPP as > a term is not very appealing to most end users, and DI.DAY mainly targets > end users. Showing real projects and what they offer may be more > attractive, and less off putting for the organizers. Those projects can > still mention XMPP if they want, but the focus would be on their value, not > just on the protocol they use. > > > > I also think there is more we can do than just aiming for a listing on > the DI.DAY website. Even if some projects decide not to be listed there, > they could still benefit from the visibility around the initiative by > aligning blog posts, announcements, or other outreach with it. > > > > Finally, I understand there is already a group chat where people > involved are coordinating this work. Pointing interested members to that > chat and inviting them to join the ongoing effort seems like a very > practical next step. > > > > To be clear, I am not against a simple public endorsement. I just feel > there is a lot more we could do here, and that a slightly more active > approach could massively benefit our projects and the wider ecosystem. > > > A bit of an update. Please try to keep this information more or less > to this list for now. > > People have reached out to DI.DAY and the website now mentions XMPP in > a footnote of a footnote. People are trying to get them to clean up > the wording around that mention a bit but I’m afraid that is the > maximum we will get out of them. I don’t think they will publish an > official XMPP recipe. > > However the aforementioned channel has been working on a nice XMPP > recipe that we plan to push hard on social media on February 1st. This > is something the comm team can help with. (Social media and maybe a > blog post) > > I think our official communication should mention Digital Independence > day as a concept and push our "recipe" but not link to or acknowledge > the official website. The official website recommends a competitor > (Signal) and I don’t think any of our communication should include > "Hey check out Signal". > > > cheers > Daniel >
