Version 1.2.2 of XEP-0107 (User Mood) has been released.
Abstract:
This specification defines a payload format for communicating
information about user moods, such as whether a person is currently
happy, sad, angry, or annoyed. The payload format is typically
transported using the personal
Version 0.1.0 of XEP-0491 (WebXDC) has been released.
Abstract:
This document defines an XMPP protocol extension to communicate WebXDC
widgets and their state updates.
Changelog:
* Promoted to Experimental (XEP Editor: dg)
URL: https://xmpp.org/extensions/xep-0491.html
Note: The information in
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
element”. (egp)
URL:
Good morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, June 18
2024 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
* Proposed XMPP Extension: Chat notification settings
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
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
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
Good morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, May 21 2024
at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
* Proposed XMPP Extension: Jingle Remote Control
4) Items for voting
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
on the phone.
I agree that the current phrasing of the XEP with regards to
server-end-point is not the best.
cheers
Daniel
___
Standards mailing list -- standards@xmpp.org
To unsubscribe send an email to standards-le...@xmpp.org
This message constitutes notice of a Last Call for comments on
XEP-0421.
Title: Anonymous unique occupant identifiers for MUCs
Abstract:
This specification defines a method that allows clients to identify a
MUC participant across reconnects and renames. It thus prevents
impersonification of
Version 1.34.6 of XEP-0045 (Multi-User Chat) has been released.
Abstract:
This specification defines an XMPP protocol extension for multi-user
text chat, whereby multiple XMPP users can exchange messages in the
context of a room or channel, similar to Internet Relay Chat (IRC). In
addition to
Version 2.5.0 of XEP-0030 (Service Discovery) has been released.
Abstract:
This specification defines an XMPP protocol extension for discovering
information about other XMPP entities. Two kinds of information can be
discovered: (1) the identity and capabilities of an entity, including
the
Good morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, May 7 2024
at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
4) Items for voting
a) PR: XEP-0030: Note known wart
This message constitutes notice of a Last Call for comments on
XEP-0440.
Title: SASL Channel-Binding Type Capability
Abstract:
This specification allows servers to annouce their supported SASL
channel-binding types to clients.
URL: https://xmpp.org/extensions/xep-0440.html
This Last Call begins
Version 1.0.0 of XEP-0398 (User Avatar to vCard-Based Avatars
Conversion) has been released.
Abstract:
This specification describes a method for using PEP based avatars and
vCard based avatars in parallel by having the user’s server do a
conversion between the two.
Changelog:
Accept as Stable as
Version 1.0.1 of XEP-0388 (Extensible SASL Profile) has been released.
Abstract:
This document describes a replacement for the SASL profile documented
in RFC 6120 which allows for greater extensibility.
Changelog:
Fixed typos (md)
URL: https://xmpp.org/extensions/xep-0388.html
Note: The
Good morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, April 23
2024 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
* STABLE: XEP-0334 (Message Processing Hints)
* STABLE: XEP-0333
Version 1.0.0 of XEP-0334 (Message Processing Hints) has been
released.
Abstract:
This document defines a way to include hints to entities routing or
receiving a message.
Changelog:
Accept as Stable as per Council Vote from 2024-04-17 (XEP Editor (dg))
URL:
Version 1.0.0 of XEP-0333 (Displayed Markers) has been released.
Abstract:
This specification introduces a method to let the sender, or multiple
participants in a group chat, know that a client has displayed
messages up to a certain point.
Changelog:
Accept as Stable as per Council Vote from
Good morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, April 16
2024 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
Minor updates to XEP-0444 (Message Reactions) and XEP-0440 (Channel
Version 0.2.1 of XEP-0444 (Message Reactions) has been released.
Abstract:
This specification defines a way for adding reactions to a message.
Changelog:
fix grammar and spelling (wb)
URL: https://xmpp.org/extensions/xep-0444.html
Note: The information in the XEP list at
Version 0.4.1 of XEP-0440 (SASL Channel-Binding Type Capability) has
been released.
Abstract:
This specification allows servers to annouce their supported SASL
channel-binding types to clients.
Changelog:
Recommend the usage of tls-exporter over tls-server-end-point
(fs)
URL:
Good morning Council Members,
the next XMPP Council Meeting will take place today on, Tuesday, April
9 2024 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
* STABLE: XEP-0386 (Bind 2)
* STABLE: XEP-0388 (Extensible
Version 0.7.0 of XEP-0333 (Displayed Markers) has been released.
Abstract:
This specification introduces a method to let the sender, or multiple
participants in a group chat, know that a client has displayed
messages up to a certain point.
Changelog:
* Change title to "Displayed Markers"
* Bring
Version 1.0.0 of XEP-0388 (Extensible SASL Profile) has been released.
Abstract:
This document describes a replacement for the SASL profile documented
in RFC 6120 which allows for greater extensibility.
Changelog:
Accept as Stable as per Council Vote from 2024-04-02. (XEP Editor
(dg))
URL:
Version 1.0.0 of XEP-0386 (Bind 2) has been released.
Abstract:
This specification provides a single-request replacement for several
activities an XMPP client needs to do at startup.
Changelog:
Accept as Stable as per Council Vote from 2024-04-02. (XEP Editor
(dg))
URL:
Good morning Council Members,
the next XMPP Council Meeting will take place today on, Tuesday, April
2 2024 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
* LAST CALL: XEP-0398: User Avatar to vCard-Based Avatars
This message constitutes notice of a Last Call for comments on
XEP-0398.
Title: User Avatar to vCard-Based Avatars Conversion
Abstract:
This specification describes a method for using PEP based avatars and
vCard based avatars in parallel by having the user’s server do a
conversion between the
Version 0.4.1 of XEP-0424 (Message Retraction) has been released.
Abstract:
This specification defines a method for indicating that a message
should be retracted.
Changelog:
* Fix schema.
* Add missing for attribute in fallback element (Example 4). (nc)
URL:
Version 1.0.0 of XEP-0392 (Consistent Color Generation) has been
released.
Abstract:
This specification provides a set of algorithms to consistently
generate colors given a string. The string can be a nickname, a JID or
any other piece of information. All entities adhering to this
specification
Version 0.2 of XEP-0360 (Nonzas (are not Stanzas)) has been released.
Abstract:
This specification defines the term "Nonza", describing every top
level stream element that is not a Stanza.
Changelog:
Defer due to lack of activity. (XEP Editor (jwi))
URL:
that other HSL could be used
- state that implementations SHOULD use constant S and L for specific
usecases/themes for uniformity
Council believes that this can happen after the move to stable. (But
we would be very disappointed if it doesn’t happen :-) )
cheers
Daniel
On Tue, Mar 26, 2024 at 1:40 PM Andrew Nenakhov
wrote:
>
> Well, on the other hand, since the only scenario I can imagine using
> in the wild has significantly different semantics from
> readdisplayed markers, I think that this is not really necessary in this XEP.
The part I was considering
On Tue, Mar 26, 2024 at 1:11 PM Dave Cridland wrote:
> 3) It's really not. Some clients and intermediaries need to know whether they
> should expect a marker or not. No need to check this prior to sending a
> , true, but useful to track missing markers afterward.
>
> Where was the discussion
ated
> 0184 instead.
The XEP has a section that explains why 184 was kept. It's not just a
different XEP it's a different semantic that many people prefer.
cheers
Daniel
___
Standards mailing list -- standards@xmpp.org
To unsubscribe send an email
Version 0.1.0 of XEP-0490 (Message Displayed Synchronization) has been
released.
Abstract:
This specification allows multiple clients of the same user to
synchronize the displayed state of their chats.
Changelog:
* Promoted to Experimental (XEP Editor: dg)
URL:
Good morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, March 26
2024 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
* LAST CALL: XEP-0333 (Displayed Markers (was: Chat Markers))
*
This message constitutes notice of a Last Call for comments on
XEP-0334.
Title: Message Processing Hints
Abstract:
This document defines a way to include hints to entities routing or
receiving a message.
URL: https://xmpp.org/extensions/xep-0334.html
This Last Call begins today and shall end at
This message constitutes notice of a Last Call for comments on
XEP-0333.
Title: Displayed Markers (was: Chat Markers)
Abstract:
This specification introduces a method to let the sender, or multiple
participants in a group chat, know that a client has displayed
messages up to a certain point.
Version 0.4.1 of XEP-0388 (Extensible SASL Profile) has been released.
Abstract:
This document describes a replacement for the SASL profile documented
in RFC 6120 which allows for greater extensibility.
Changelog:
* Add missing elements to XML Schema
* Add missing XMPP Registrar Considerations
Version 0.5.0 of XEP-0334 (Message Processing Hints) has been
released.
Abstract:
This document defines a way to include hints to entities routing or
receiving a message.
Changelog:
Incorporate last call feedback from 2017.
Differences between this specification and XEP-0079 have been
clarified.
Version 0.6.0 of XEP-0333 (Displayed Markers (was: Chat Markers)) has
been released.
Abstract:
This specification introduces a method to let the sender, or multiple
participants in a group chat, know that a client has displayed
messages up to a certain point.
Changelog:
* Add Business Rule about
On Fri, Mar 22, 2024 at 9:46 AM Florian Schmaus wrote:
> - § 7. says 'None' whereas this XEP introduces a new namespace
> 'urn:xmpp:sasl:2' which should be registered in the registrars namespace
> registry (Yes I know that the XSF registrar is not in a good shape, but
> still).
Thanks. I've
even like it.
However it is not. The XEP as proposed has major implications on the
language used in existing, stable, XEPs such as SM and CSI and every
future XEP we write. I don’t like that for the reasons outlined by
Kev, Dave, Sam and myself.
cheers
Daniel
__
Version 0.2.1 of XEP-0428 (Fallback Indication) has been released.
Abstract:
This specification proposes a mechanism by which message bodies or
parts thereof can be marked as being for fallback purposes, and
therefore to be ignored by anything that understands the original
intent of the message.
are
sometimes generated by bouncing the entire stanza, including original
contents, back to the sender, and these original contents might
include a hint; it seems sensible to always ignore these."
that also sounds like a sensible addition to me.
Maybe you have
On Mon, Mar 18, 2024 at 9:59 AM Daniel Gultsch wrote:
> 1. Is this specification needed to fill gaps in the XMPP protocol
> stack or to clarify an existing protocol?
Yes
> 2. Does the specification solve the problem stated in the introduction
> and requirements?
Yes
>
Good morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, March 19
2024 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
* LAST CALL: XEP-0388 (Extensible SASL Profile)
* LAST CALL:
This message constitutes notice of a Last Call for comments on
XEP-0388.
Title: Extensible SASL Profile
Abstract:
This document describes a replacement for the SASL profile documented
in RFC 6120 which allows for greater extensibility.
URL: https://xmpp.org/extensions/xep-0388.html
This Last
This message constitutes notice of a Last Call for comments on
XEP-0386.
Title: Bind 2
Abstract:
This specification provides a single-request replacement for several
activities an XMPP client needs to do at startup.
URL: https://xmpp.org/extensions/xep-0386.html
This Last Call begins today and
Version 1.1.1 of XEP-0313 (Message Archive Management) has been
released.
Abstract:
This document defines a protocol to query and control an archive of
messages stored on a server.
Changelog:
Add XEP-0136 to superseded specifications (gdk)
URL: https://xmpp.org/extensions/xep-0313.html
Note:
Hi,
It’s the editor with a manual update here. Our tooling couldn’t
process PRPOSED->EXPERIMENTAL and an update in the same step.¹
XEP-0425 was updated. Here is the change log.
* Remove the dependency on XEP-0422 Message Fastening
* Rename to 'Moderated Message Retraction' and focus only on
specced
> now, but there would need to be some way for the server to know that eg in
> MUC the id is in fact the stanza id vs doing the lookup in MAM for non-MUC.
What you are proposing depends on the message being archived. The
specification as written notably does not.
cheers
Daniel
_
nza to x" with "performing
an operation on the account that involves x" is a slippery slope that
I’m really trying to avoid. I don’t want to set precedence to for
example to use "" to block "foo".
This has come up in the group chat be
Good morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, March 12
2024 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
* Proposed XMPP Extension: Message Displayed Synchronization
* LAST
On Sun, Mar 10, 2024 at 4:18 PM Daniel Gultsch wrote:
>
> This message constitutes notice of a Last Call for comments on
> XEP-0360.
>
> Title: Nonzas (are not Stanzas)
> Abstract:
> This specification defines the term "Nonza", describing every top
> level s
On Sun, Mar 10, 2024 at 3:24 PM Daniel Gultsch wrote:
>
> This message constitutes notice of a Last Call for comments on
> XEP-0392.
> 1. Is this specification needed to fill gaps in the XMPP protocol
> stack or to clarify an existing protocol?
Yes
> 2. Does the specification
Version 1.25.0 of XEP-0001 (XMPP Extension Protocols) has been
released.
Abstract:
This document defines the standards process followed by the XMPP
Standards Foundation.
Changelog:
Add note that editorial changes do not affect Deferred state (XEP
Editor: dg)
URL:
Version 0.1.0 of XEP-0489 (Reporting Account Affiliations) has been
released.
Abstract:
This specification documents a way for an XMPP server to report to
other entities the relationship it has with a user on its domain.
Changelog:
* Promoted to Experimental (XEP Editor: dg)
URL:
Version 0.1.0 of XEP-0488 (MUC Token Invite) has been released.
Abstract:
This specification provides a way to generate tokens to invite users
to a MUC room.
Changelog:
* Promoted to Experimental (XEP Editor: dg)
URL: https://xmpp.org/extensions/xep-0488.html
Note: The information in the XEP
Version 1.26.0 of XEP-0060 (Publish-Subscribe) has been released.
Abstract:
This specification defines an XMPP protocol extension for generic
publish-subscribe functionality. The protocol enables XMPP entities to
create nodes (topics) at a pubsub service and publish information at
those nodes; an
This message constitutes notice of a Last Call for comments on
XEP-0360.
Title: Nonzas (are not Stanzas)
Abstract:
This specification defines the term "Nonza", describing every top
level stream element that is not a Stanza.
URL: https://xmpp.org/extensions/xep-0360.html
This Last Call begins
This message constitutes notice of a Last Call for comments on
XEP-0392.
Title: Consistent Color Generation
Abstract:
This specification provides a set of algorithms to consistently
generate colors given a string. The string can be a nickname, a JID or
any other piece of information. All entities
Version 0.5.0 of XEP-0333 (Displayed Markers (was: Chat Markers)) has
been released.
Abstract:
This specification introduces a method to let the sender, or multiple
participants in a group chat, know that a client has displayed
messages up to a certain point.
Changelog:
* Remove to not
Version 0.3.1 of XEP-0447 (Stateless file sharing) has been released.
Abstract:
This specification describes a protocol for stateless asynchronous
file sharing with integrity and transport flexibility. It allows
clients to provide a good interoperable user experience in combination
with Carbons
Version 0.3.0 of XEP-0447 (Stateless file sharing) has been released.
Abstract:
This specification describes a protocol for stateless asynchronous
file sharing with integrity and transport flexibility. It allows
clients to provide a good interoperable user experience in combination
with Carbons
Version 0.3.0 of XEP-0398 (User Avatar to vCard-Based Avatars
Conversion) has been released.
Abstract:
This specification describes a method for using PEP based avatars and
vCard based avatars in parallel by having the user’s server do a
conversion between the two.
Changelog:
* Add text to
Version 0.1.0 of XEP-0487 (Host Meta 2 - One Method To Rule Them All)
has been released.
Abstract:
This document defines an XMPP Extension Protocol for extending
XEP-0156 by modifying the JSON Web Host Metadata Link format to
support discovering all possible XMPP connection methods, for c2s and
Version 0.1.0 of XEP-0486 (MUC Avatars) has been released.
Abstract:
This specification describes how to publish and retrieve avatars in
rooms.
Changelog:
* Promoted to Experimental (XEP Editor: dg)
URL: https://xmpp.org/extensions/xep-0486.html
Note: The information in the XEP list at
Version 0.1.0 of XEP-0485 (PubSub Server Information) has been
released.
Abstract:
This document defines a data format whereby basic information of an
XMPP domain can be expressed and exposed over pub-sub.
Changelog:
* Promoted to Experimental. (dg)
URL:
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Message Displayed Synchronization
Abstract:
This specification allows multiple clients of the same user to
synchronize the displayed state of their chats.
URL: https://xmpp.org/extensions/inbox/xep-mds.html
The Council
during the Last Call.
As soon as my modifications are merged and published I will ask
Council to start another last call.
Here is a rendered version of the modified XEP:
https://gultsch.de/files/xep-0398.html
cheers
Daniel
___
Standards mailing list
Dear Editor,
please note that council has accepted the proposed XEP 'MUC Avatars'
into the historical track.
(A previous submission into standards track has been rejected by the
council at that time)
https://xmpp.org/extensions/inbox/muc-avatars.html
cheers
Daniel
Good morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, February 13
2024 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
4) Items for voting
a) xep-template: Require accessibility and
Dear Editor,
Council has voted to accept this XEP.
cheers
Daniel
On Mon, Jan 22, 2024 at 3:56 PM wrote:
>
> The XMPP Extensions Editor has received a proposal for a new XEP.
>
> Title: PubSub Server Information
> Abstract:
> This document defines a data format whereby
Good morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, December 12
2023 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
- UPDATED: XEP-0198 Stream Management
- UPDATED: XEP-0402 PEP
Dear Editor,
Council has accepted this XEP.
Dear XEP author: Council has noted some overlap with XEP-0482. Please
get in touch with the authors of that XEP to see if you can merge
and/or remove the overlap. See Marvins earlier mail for details.
cheers
Daniel
Good morning Council Members,
the next XMPP Council Meeting will take place today, on, Tuesday,
December 5 2023 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
none
4) Items for voting
none
5) Pending votes
none
Good morning Council,
the next XMPP Council Meeting will take place today, on Wednesday,
November 29th 2023 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Election of new Chair
4) Election of Board Liaison
5) Schedule regular
Good morning Council Members,
the next XMPP Council Meeting will take place on, Wednesday, November
8 2023 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
- UPDATED: XEP-0377 Spam Reporting
Good morning Council Members,
the next XMPP Council Meeting will take place today, Wednesday,
October 4 2023 at 15:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
none
4) Items for voting
a) Issue Last Call on XEP-0386:
uncil has accepted this today.
cheers
Daniel
___
Standards mailing list -- standards@xmpp.org
Info: Unsubscribe: %(real_name)s-unsubscribe@%(host_name)s
___
Good morning Council Members,
the next XMPP Council Meeting will take place on Wednesday, September
13 2023 at 15:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
none
4) Items for voting
a) XEP-0198: Add section defining
Hi Kev,
council has accepted this XEP.
cheers
Daniel
On Tue, Jul 4, 2023 at 3:56 PM wrote:
>
> The XMPP Extensions Editor has received a proposal for a new XEP.
>
> Title: Reporting Account Affiliations
> Abstract:
> This specification documents a way for an XMPP server to
Good morning Council Members,
the next XMPP Council Meeting will take place on Wednesday, July 5
2023 at 15:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
* UPDATED: XEP-0317 Hats (https://xmpp.org/extensions/xep-0317.html)
Good morning Council Members,
the next XMPP Council Meeting will take place on Wednesday, May 31
2023 at 15:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
none
4) Items for voting
a) Update BCP 14 language to comply with
Council has accepted this XEP
On Tue, Dec 20, 2022 at 7:41 PM Jonas Schäfer wrote:
>
> The XMPP Extensions Editor has received a proposal for a new XEP.
>
> Title: Stream Limits Advertisement
> Abstract:
> This specification defines a way for an XMPP entity to announce the
> limits it will
Council has accepted this XEP.
On Wed, Jan 25, 2023 at 6:04 PM wrote:
>
> The XMPP Extensions Editor has received a proposal for a new XEP.
>
> Title: XMPP Compliance Suites 2023
> Abstract:
> This document defines XMPP application categories for different use
> cases (Core, Web, IM, and
Good morning Council Members,
the next XMPP Council Meeting will take place, today, Wednesday, April
26 2023 at 15:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
none
4) Items for voting
a) XEP-0424: Remove dependency on
Hi,
since this mailing list was down for a few weeks I’m sending the
invite for our March 29th council meeting again.
Note I had not send an agenda for our April 5th meeting. (That meeting
had no new agenda items)
Good morning Council Members,
the next XMPP Council Meeting will take place
/content-types.html
d) Issue Last Call on XEP-0353: Jingle Message Initiation
https://xmpp.org/extensions/xep-0353.html
e) Reconsider 'Proposed Extension: Call Invites'
https://xmpp.org/extensions/inbox/call-invites.html
5) Pending votes
Travis and Daniel on pubsub#publish_node_full
Georg on all
for
running on the server with a reduced attack surface compared to other
scripting languages.
User can implement spam filter in whatever language they prefer.
CPU runtime can easily be limited.
Anyone more XMPP affine want's to implement a XEP and implementation ?
kind regards
Daniel
Good morning Council Members,
the next XMPP Council Meeting will take place today, Wednesday, March
1st 2023 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
4) Items for voting
a) Revert 'XEP-0424: Message
. (Marvin suggested this; I'm just
repeating this because I agree)
If fastening had security issues (I didn’t check) I don’t think it
matters anymore because we are in the process of phasing that out.
cheers
Daniel
On Tue, Feb 21, 2023 at 9:20 PM Marvin W wrote:
>
> Hi,
>
> This
;
but that can be a different discussion)
If people are happy with that suggestion (to get rid of Fastening) I
think I can very easily make a PR.
cheers
Daniel
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards
Good morning Council Members,
the next XMPP Council Meeting will take place today, Wednesday,
February 08st 2023 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
* UPDATED: XEP-0353 (Jingle Message Initiation)
might do for a migration period. But those client will be 'wrong' and
will require minor fixing.
cheers
Daniel
[1]:
https://github.com/iNPUTmice/Conversations/blob/master/src/main/java/eu/siacs/conversations/xmpp/jingle/JingleRtpConnection.java#L1371
On Wed, Jan 25, 2023 at 10:22 PM Thilo
I'd get rid of instead of
Only put into the stanza. Don’t send at all.
Stops you from having to put two elements in the message.
What in the :0 version was will just quietly go away. (In
favor of wording around proceed being carbon copied)
On Wed, Jan 25, 2023 at 3:49 AM Thilo Molitor
Good morning Council Members,
the next XMPP Council Meeting will take place today, Wednesday,
December 21st 2022 at 16:00 UTC in xmpp:coun...@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
a) NEW: XEP-0475 (Pubsub Signing)
1 - 100 of 516 matches
Mail list logo
