Re: [Standards] Call for Experience: XEP-0048: Bookmarks

2018-03-21 Thread Kevin Smith
On 7 Mar 2018, at 19:17, Jonas Wielicki (XSF Editor) wrote: > The XEP Editor would like to Call for Experience with XEP-0048 before > presenting it to the Council for advancing it to Final status. > > > During the Call for Experience, please answer the following questions:

Re: [Standards] Call for Experience: XEP-0048: Bookmarks

2018-03-08 Thread Kozlov Konstantin
Hello! 07.03.2018, 22:18, "Jonas Wielicki (XSF Editor)" :The XEP Editor would like to Call for Experience with XEP-0048 beforepresenting it to the Council for advancing it to Final status.During the Call for Experience, please answer the following questions:1. What software

Re: [Standards] Call for Experience: XEP-0048: Bookmarks

2018-03-08 Thread Goffi
Can't make a detailed review today, so here's quickly: the XEP is implemented in SàT using both private XML storage (XEP-0049) and PEP. There are several issues with this XEP, the most important being the race condition can be specially bad as all bookmarks are saved in the same item. Also

Re: [Standards] Call for Experience: XEP-0048: Bookmarks

2018-03-08 Thread Jonas Wielicki
On Donnerstag, 8. März 2018 08:28:27 CET Daniel Gultsch wrote: > 2018-03-08 8:22 GMT+01:00 Jonas Wielicki : > > On Donnerstag, 8. März 2018 07:38:42 CET Daniel Gultsch wrote: > >> It feels a bit sad that we aren't able to advance a XEP that is widely > >> deployed (in a way)

Re: [Standards] Call for Experience: XEP-0048: Bookmarks

2018-03-07 Thread Daniel Gultsch
2018-03-08 8:22 GMT+01:00 Jonas Wielicki : > On Donnerstag, 8. März 2018 07:38:42 CET Daniel Gultsch wrote: >> It feels a bit sad that we aren't able to advance a XEP that is widely >> deployed (in a way) but I think it is just too late. > > Can’t we revert to XEP-0049 (if no

Re: [Standards] Call for Experience: XEP-0048: Bookmarks

2018-03-07 Thread Jonas Wielicki
On Donnerstag, 8. März 2018 07:38:42 CET Daniel Gultsch wrote: > It feels a bit sad that we aren't able to advance a XEP that is widely > deployed (in a way) but I think it is just too late. Can’t we revert to XEP-0049 (if no other XEP-0223 implementations show up), advance *that* to final and

Re: [Standards] Call for Experience: XEP-0048: Bookmarks

2018-03-07 Thread Daniel Gultsch
2018-03-07 20:17 GMT+01:00 Jonas Wielicki : > The XEP Editor would like to Call for Experience with XEP-0048 before > presenting it to the Council for advancing it to Final status. > > > During the Call for Experience, please answer the following questions: > > 1. What

Re: [Standards] Call for Experience: XEP-0048: Bookmarks

2018-03-07 Thread Kim Alvefur
On Wed, Mar 07, 2018 at 07:17:24PM -, Jonas Wielicki wrote: > The XEP Editor would like to Call for Experience with XEP-0048 before > presenting it to the Council for advancing it to Final status. > > > During the Call for Experience, please answer the following questions: > > 1. What

Re: [Standards] Call for Experience: XEP-0048: Bookmarks

2018-03-07 Thread Christian Schudt
> 1. What software has XEP-0048 implemented? Please note that the > protocol must be implemented in at least two separate codebases (at > least one of which must be free or open-source software) in order to > advance from Draft to Final. Enough. > 2. Have developers experienced any problems with

Re: [Standards] Call for Experience: XEP-0048: Bookmarks

2018-03-07 Thread Jonas Wielicki
On Mittwoch, 7. März 2018 20:17:24 CET Jonas Wielicki wrote: > 1. What software has XEP-0048 implemented? We have support for Private XML (XEP-0049)-based bookmarks in aioxmpp (LGPLv3) and based on that in JabberCat (GPLv3). We haven’t gotten around to implement PEP-based bookmarks, even though

[Standards] Call for Experience: XEP-0048: Bookmarks

2018-03-07 Thread XSF Editor
The XEP Editor would like to Call for Experience with XEP-0048 before presenting it to the Council for advancing it to Final status. During the Call for Experience, please answer the following questions: 1. What software has XEP-0048 implemented? Please note that the protocol must be