Version 1.1.1 of XEP-0153 (vCard-Based Avatars) has been released.
Abstract:
This document provides historical documentation of a vCard-based
protocol for exchanging user avatars.
Changelog:
XEP-0054 says “Email addresses MUST be contained in a <USERID>
element”. (egp)
URL: https://xmpp.org/extensions/xep-0153.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
I have setup the membership application Wiki page for the application
period Q3 2024
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community. To apply, create a page about
yourself on the Wiki:
https://wiki.xmpp.org/web/Membership_Applications_Q3_2024
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
https://wiki.xmpp.org/web/Sysops
Apply now!!!
Thanks,
Alex
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: WebXDC
Abstract:
This document defines an XMPP protocol extension to communicate WebXDC
widgets and their state updates.
URL: https://xmpp.org/extensions/inbox/webxdc.html
The Council will decide in the next two weeks whether to accept this
proposal as an official XEP.
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Chat notification settings
Abstract:
This document defines an XMPP protocol extension to synchronise per-
chat notification settings across different clients.
URL: https://xmpp.org/extensions/inbox/notification-filter.html
The Council will decide in the next two weeks whether to accept this
proposal as an official XEP.
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Jingle Remote Control
Abstract:
This specification defines a way to remotely control a device using
local peripheral inputs.
URL: https://xmpp.org/extensions/inbox/remote-control.html
The Council will decide in the next two weeks whether to accept this
proposal as an official XEP.
I am an end-user using two XMPP clients: for desktop and mobile. Since there is no XEP standard for muting conversations, the two clients implement this in their own way, and they are out of sync: the contacts I have muted on phone are not automatically muted on desktop and vice-verse.
While looking to see if XMPP have such XEP, I found these extensions from Tigase that might be helpful in writing an official XEP:
https://xeps.tigase.net/docs/push-notifications/filters
Version 0.2.0 of XEP-0421 (Anonymous unique occupant identifiers for
MUCs) has been released.
Abstract:
This specification defines a method that allows clients to identify a
MUC participant across reconnects and renames. It thus prevents
impersonification of anonymous users.
Changelog:
* Make explicit that one can't just hash the real JID.
* Expand security considerations.
* Add schema.
* Fix some examples captions and casing (mw)
URL: https://xmpp.org/extensions/xep-0421.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
"XEP-0469: Bookmark Pinning" specifies the implementation for bookmark pinning but only for group chats?
Not sure if there is already an existing XEP for that, but one for pinning user chats would be useful.
I am an end-user, and having used Telegram for some time, it offers a more fine-grained control over members of a group.
One of those controls is to prevent group members (usually bots) from reading group messages, and only allow them to send messages, following the principle of least privilege.
A more complex set up would be partially allow them to read messages directed to them and exclude the rest of messages. E.g: by specifying a command like /bot, the bot can read the content of that message to process it then reply back.
