Difference between revisions of "Georg Lukas for Council 2017"
(Created page with "= Contact Info = * '''Georg Lukas''' * '''Ge0rG''' in the usual MUCs * XMPP identifier: '''[xmpp:georg@yax.im georg@yax.im]''' * Employer: [https://rt-solutions.de/en/home-2/...") |
|||
Line 9: | Line 9: | ||
This is my first application for Council. I have a progressive agenda to make XMPP suitable for the Instant Messaging of this decade (even if it's a bit late). | This is my first application for Council. I have a progressive agenda to make XMPP suitable for the Instant Messaging of this decade (even if it's a bit late). | ||
I'm a client developer (https://yaxim.org) and a server operator of a mid-sized public server. I've done some work on XEPs in the past and usually have strong opinions. | |||
= Goals = | = Goals = |
Revision as of 11:08, 5 November 2017
Contact Info
- Georg Lukas
- Ge0rG in the usual MUCs
- XMPP identifier: georg@yax.im
- Employer: rt-solutions.de GmbH (Germany)
Overview
This is my first application for Council. I have a progressive agenda to make XMPP suitable for the Instant Messaging of this decade (even if it's a bit late).
I'm a client developer (https://yaxim.org) and a server operator of a mid-sized public server. I've done some work on XEPs in the past and usually have strong opinions.
Goals
Improve Usability
Jabber (the IM ecosystem) needs many usability improvements. My ongoing activities in that regard are:
- Provide a unified glossary to developers and users, hiding complexity where possible
- Easy XMPP: improve onboarding, UX, MUCs, etc
- XEP-0379: Pre-Authenticated Roster Subscription
- Easy XMPP: The Challenges on our blog
- Solve the "Jabber" vs "XMPP" name clash
Fix the Multi-Client Story
There are many edge cases in setups where a user runs a mobile client plus a desktop client on the same account. Messages are still lost, different things get delivered to online clients and stored into MAM/offline storage, encryption fails, etc.
We need to evaluate our current situation with regards to the base protocol, how it is used, XEPs related to multi-client operations, etc. Then we need to make a clear mission statement for how we want the system to work in the future. Finally, we need to change our protocols in a way that doesn't break backward compatibility, while providing more robust support for modern use cases.
Topics to address:
- "Message Routing 2.0"
- Multi-Session Nicks
- Device identity, per-device passwords, etc
Get Rid of Spam
XMPP spam is getting more and more prevalent. We have some obvious and some more complex tasks:
- Improve default server setups to prevent IBR / mass-flooding
- Improve server admin contact infos
- Improve detection and blocking of inbound spam messages / presence