Topic 1: #XMPP Shortage Audit
We talk about ways in which xmpp comes short compared to other solutions like Slack, WhatsApp etc.
On the list are things such as contact discovery, snippets, microblogging ("stories"), stickers, bots and other integrations.
Some of those are already specified but lack implementation, others are not yet tackled at all.
Topic 2: Easy Password-less Onboarding and Account Management
User onboarding could be vastly simplified by having the registering device generate a random password/key. Problems arising from this are usage with multi devices (QR code scanning with existing devices), password reset (reset link via email, pin via other device).
Other things to consider are client certificates (XEP-0257) and other SASL authentication methods.
Topic 4: Rich Account Presence in PEP
Classic presence in #xmpp is device centered and breaks down in multi device usage.
Eg. if the user sets his desktop client to "away" and starts using his phone, is he now away or on the phone? Both?
Publishing the status of a user (eg. "I'm at the Summit \o/") to a PEP node would solve this issue as that node would be per account instead of per device. The latest status would override the previous one.
Topic 5: Message Layer Security
A workgroup within the #IETF is currently developing a new end-to-end encryption protocol called MLS which is basically the IETFs answer to the Signal protocol.
MLS focuses on group chat encryption in larger groups, but is also suitable for normal chats. Dave gave an overview of the protocol and suggests that we start looking into how to deploy it with XMPP now.
Topic 7: Why Push Notifications are not enough?
Push on iOS sucks and appears to be unreliably. Additionally the Push XEP-0357 lacks support for different types of priorities. Therefore spam messages from strangers will always alert the user as there are no silent notifications.
Tigase proposes some very interesting solutions to current push issues, like using encryption to hide message contexts inside push notifications from the push service itself.
Link to proposed push solution by Tigase: https://tigase.github.io/tigase-xeps/docs/push-notifications
Topic 8: MIX, when?
MIX is the spiritual successor of MUC group chat. There exist some implementations that suggest that implementing it is feasible. For wider adoption however, MUC downwards compatibility would be necessary.
Part of the feedback to the specification has not yet been addressed, eg. where to store records of all the MIX channels a user joined (roster?).
@vanitasvitae @tigase Hmm, that's not entirely true. The user shouldn't be notified when a push notification comes in. The app should be woken up and the app should check what's new and then decide whether the new content is worth waking up the user, right?
That content doesn't have to be part of the push necessarily for that.
@vanitasvitae What's the difference between identity key sharing and a master key? If the ID key is shared, isn't it a master key?
(I know I could go try read the minutes, but it might be helpful to have here on the record as well.)
@stevenroose a master key would be eg. an OpenPGP key which signs all OMEMO keys. The benefit of this is that the master key can be used to sign the identity keys of different encryption mechanisms.
@stevenroose It doesn't have to be an OpenPGP key though. If it is some sort of certificate, it could also be used to log into the account in the first place.
@vanitasvitae fix me if I wrong, but statuses are describes statuses of recourses, not device. Currently, if desktop client is "away" and phone status is "online", you will see both statuses simultaneously. I do not see any issues here
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.