We are too big to not to engage with XMPP
You can just endorse XMPP, which might probably be even more important than actively participating.
Preface
Not only that XMPP is the largest federated network in history, but it is also the network with the most developers and projects.
This article includes references to XMPP portals, projects, developers and events from the past and present.
History
Historical progress and events.
1999: Beginning
Since 1999, after XMPP was released, many have developed software for XMPP, including transports (i.e. gateways) to other networks, and other helpful utilities.
From transports, to weather components, to news services, to real-time HTML sotfware and so on and so forth.
Known transports are Biboumi, jabberd2 transports, Spectrum, PyTransport of xmpp.py, and Slidge.
2003: Formation
In the year of 2003, the XMPP network has included a vast amount of chat clients, extensions, servers, and utilities, mostly in the Java, Perl, Python, and even XUL.
It was impressive, even though many software were still in testing stages.
2004: Group chat
In the years of 2003 to 2004, XMPP clients add support for Multi-User Chat (MUC).
2005: Publishing
In the years of 2005 to 2008, many people, including the developer of JWChat, have advocated and encouraged to publish content over XMPP, using the Atom Syndication Format (RFC 4287).
Publishing was not initially planned for XMPP, and yet it is feasible and actively done by projects Blasta, JappixMe, Libervia, Movim, and Rivista.
The sabotage to approve Atompub/Atomsub (Atom Over XMPP) at the IETF, has prompted the creation of specification XEP-0277: Microjournaling over XMPP by Joe Hildebrand and Peter Saint-Andre.
2008: Jabber Feed
During the year of 2008, Jehan, who is the lead developer of the software The GIMP, has released a WordPress plugin which publishes articles to XMPP.
2010: Group chat
During the years, there were many ideas to improve the MUC specification, until the realization of a new specification MIX.
Some have also suggested to create lobby group chats, yet not many have dedicated the proper attention, and this idea was established as XEP-0503: Server-side spaces, 15 years later.
2012: Psi
A couple of years after the establishment of Psi+, Justin from USA has announced of an updated version of Psi, while welcoming new developers from the Balkan and Russia.
2015: WebExtensions
In the year of 2015, HTML browser vendors have engaged their plot against all protocols that are not HTTP (e.g. eD2k, FTP, Gopher, IRC, and XMPP), and so by introducing the so called WebExtensions system which lacks of TCP and UDP Socket API, XMPP software such as OneTeam, Open Aether, SamePlace, XULmark, and even ChatZilla for IRC were not compatible due to the lack of the XUL and XPCOM systems.
That insidious act of browser vendors, was, of course, obvious to many people, especially due to the senseless statements of people from browser vendor organizations, including the removal of syndication support.
Such bad events should encourage you, not otherwise; because, it means that:
- Greedy big organizations are at panic; and
- You are engaging with technology which can change the future for the better.
2020:
Ideas
There are many ideas that can be implemented today.
Presence and whiteboard
Developers of Inkscape, Krita, and The GIMP, can encourage the development of utilities and plugins which would allow to their graphics software to be integrated with XMPP.
There are many opportunities for integrating real-time features like user availability ("presence") and instant messaging into other GSoC projects. Many of these may be more appropriate for other mentoring organizations. Here are some ideas:
* AbiSource or OpenOffice.org -- Add presence icons to documents so that you can see the availability of document authors and click to chat
* Inkscape -- Building on a 2006 GSoC project, harmonize Inkboard more closely with other Jabber-based whiteboarding systems and protocols.