[Standards] LAST CALL: XEP-0402 (Bookmarks 2 (This Time it's Serious))

Florian Schmaus flo at geekplace.eu
Mon Feb 3 18:54:31 UTC 2020


On 03.02.20 18:34, Dave Cridland wrote:
> Very quick note: I've picked up an entertaining virus while at FOSDEM -
> hopefully not *that* coronavirus - so I'm not thinking clear enough to
> respond to the comments here but I am reading them.
> 
> At the moment, I don't think there's anything I find myself moved to
> argue against; Maxime's point about autojoin is interesting but I'm not
> entirely sure that Inbox works (well) with '45 at all at the moment.

I've questioned in a previous mail if inbox is the right venue for such
a thing. I actually tend to believe that information regarding the
currently open conversations (and probably their order, which is
nice-to-have for TUI clients) belongs not into inbox but in bookmarks.
This means that we do not view XMPP bookmarks as MUC (xep45) specific,
but to be generic to contain any sort of conversation bookmark (MUC,
1:1, MIX, Muc-light, MUC-sub, …).

- Florian

> On Wed, 29 Jan 2020 at 16:33, Jonas Schäfer <jonas at wielicki.name
> <mailto:jonas at wielicki.name>> wrote:
> 
>     This message constitutes notice of a Last Call for comments on
>     XEP-0402.
> 
>     Title: Bookmarks 2 (This Time it's Serious)
>     Abstract:
>     This specification defines a syntax and storage profile for keeping a
>     list of chatroom bookmarks on the server.
> 
>     URL: https://xmpp.org/extensions/xep-0402.html
> 
>     This Last Call begins today and shall end at the close of business on
>     2020-02-12.
> 
>     Please consider the following questions during this Last Call and send
>     your feedback to the standards at xmpp.org <mailto:standards at xmpp.org>
>     discussion list:
> 
>     1. Is this specification needed to fill gaps in the XMPP protocol
>     stack or to clarify an existing protocol?
> 
>     2. Does the specification solve the problem stated in the introduction
>     and requirements?
> 
>     3. Do you plan to implement this specification in your code? If not,
>     why not?
> 
>     4. Do you have any security concerns related to this specification?
> 
>     5. Is the specification accurate and clearly written?
> 
>     Your feedback is appreciated!
>     _______________________________________________
>     Standards mailing list
>     Info: https://mail.jabber.org/mailman/listinfo/standards
>     Unsubscribe: Standards-unsubscribe at xmpp.org
>     <mailto:Standards-unsubscribe at xmpp.org>
>     _______________________________________________
> 
> 
> _______________________________________________
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: Standards-unsubscribe at xmpp.org
> _______________________________________________
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 618 bytes
Desc: OpenPGP digital signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20200203/64834d55/attachment.sig>


More information about the Standards mailing list