On Samstag, 26. Juni 2021 14:31:02 CEST Sam Whited wrote:
> Another thought:
>
> Any spec that triggers traffic to a third party JID based on other
> incoming traffic can be used for DOS amplification attacks. This one
> seems only somewhat vulnerable (max payload size of the pubsub element +
>
Another thought:
Any spec that triggers traffic to a third party JID based on other
incoming traffic can be used for DOS amplification attacks. This one
seems only somewhat vulnerable (max payload size of the pubsub element +
max JID size bytes) but any of them can also become worse if
This is looking good; thanks!
I've started an implementation here (currently only supports sending a
moved request from the client side):
https://github.com/mellium/xmpp/tree/moved2/moved
After work I'll add the server side so that I can write some round trip
test cases and then move on to what
On Fri, 25 Jun 2021 at 14:34, Andrew Nenakhov
wrote:
>
> What happens if a user has several connected clients that support this xep?
I should add a note about this to the design considerations, indeed.
The summary is, as far as I see, "nothing bad". If N clients are
concurrently connected, they
What happens if a user has several connected clients that support this xep?
On the broader subject, I think that any xep that is oriented at doing
anything on clientside should have a mandatory section dealing with
multi-device use cases.
On Fri, 25 Jun 2021, 16:07 Jonas Schäfer, wrote:
> The
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Moved 2.0
Abstract:
This specification details a way for a user to notify their contacts
about an account move.
URL: https://xmpp.org/extensions/inbox/moved2.html
The Council will decide in the next two weeks whether to
