145
edits
Difference between revisions of "Georg Lukas for Council 2018"
Jump to navigation
Jump to search
Georg Lukas for Council 2018 (view source)
Revision as of 13:08, 2 November 2018
, 13:08, 2 November 2018→Overview
(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/...") |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
This is my second 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 second 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 have experience with designing and implementing network protocols, and I've done some work on XEPs in the past. | * [https://upload.yax.im/upload/L9QpGat3GD9S3nMF/make-xmpp-great-again.jpg Official Campaign Banner] | ||
* My [https://op-co.de/tmp/MUC-CCDE.jpg MUC Corner Case Debugging Engineer] certificate | |||
I'm a client developer (https://yaxim.org) and a server operator of a mid-sized public server. I have experience with designing and implementing network protocols, and I've done some work on XEPs in the past (see below). | |||
I usually have strong opinions. A clearly written and unambiguous specification is paramount to consistent implementations on the client and server side. XMPP has many corner cases caused by loosely written, imprecise specifications. These make debugging of user problems harder than needed (and often cause those problems in the first place). When elected to Council, I will work hard to reduce the number of these corner cases and to specify well-defined behaviors for those that can not be removed. | I usually have strong opinions. A clearly written and unambiguous specification is paramount to consistent implementations on the client and server side. XMPP has many corner cases caused by loosely written, imprecise specifications. These make debugging of user problems harder than needed (and often cause those problems in the first place). When elected to Council, I will work hard to reduce the number of these corner cases and to specify well-defined behaviors for those that can not be removed. | ||
| Line 22: | Line 25: | ||
* Provide a unified [https://wiki.xmpp.org/web/Usability/Glossary glossary] to developers and users, hiding complexity where possible | * Provide a unified [https://wiki.xmpp.org/web/Usability/Glossary glossary] to developers and users, hiding complexity where possible | ||
* [[Easy XMPP]]: improve onboarding, UX, MUCs, etc | * [[Easy XMPP]]: improve onboarding, UX, MUCs, etc | ||
* [https://xmpp.org/extensions/xep-0379.html XEP-0379: Pre-Authenticated Roster Subscription] | ** Make onboarding of new users easier with the [https://github.com/ge0rg/easy-xmpp-invitation Easy XMPP Invitation] landing page | ||
* [https://xmpp.org/extensions/xep- | ** Share links for automatic roster approval with [https://xmpp.org/extensions/xep-0379.html XEP-0379: Pre-Authenticated Roster Subscription] | ||
* [https://xmpp.org/2017/08/easy-xmpp-the-challenges/ Easy XMPP: The Challenges] on our blog | ** Allow the creation of pre-configured accounts [https://xmpp.org/extensions/xep-0401.html XEP-0401: Easy User Onboarding] | ||
** [https://xmpp.org/2017/08/easy-xmpp-the-challenges/ Easy XMPP: The Challenges] on our blog | |||
* Solve the [https://mail.jabber.org/pipermail/members/2017-July/008586.html "Jabber" vs "XMPP" name clash] | * Solve the [https://mail.jabber.org/pipermail/members/2017-July/008586.html "Jabber" vs "XMPP" name clash] | ||
| Line 45: | Line 49: | ||
* Improve server admin contact Infos (use XEP-0157) | * Improve server admin contact Infos (use XEP-0157) | ||
* Improve detection and blocking of inbound spam messages / presence: Ask me about mod_firewall (prosody) | * Improve detection and blocking of inbound spam messages / presence: Ask me about mod_firewall (prosody) | ||
=== Last Year's Contributions === | |||
* [https://xmpp.org/extensions/xep-0401.html XEP-0401: Easy User Onboarding] (Some high-level / conceptual contributions) | |||
* [https://xmpp.org/extensions/xep-0410.html XEP-0410: MUC Self-Ping] | |||
* [https://op-co.de/tmp/whats-wrong-with-xmpp-2017.pdf What's Broken in XMPP, Summit 2018 edition] - the talk I gave at last year's Summit | |||
* [https://github.com/xsf/xeps/pull/600 Enforced stable message IDs in MUC] | |||