Le lundi 3 décembre 2018, 11:17:24 CET Kevin Smith a écrit : > On 3 Dec 2018, at 10:02, Matthew Wild <[email protected]> wrote: > > > > Hi all, > > > > I'd like to allow servers to advertise status pages to their users. > > See for example https://statut.jabberfr.org/ > > > > This information could be cached by clients, and linked to in case of > > problems connecting, for example. > > > > The question is where and how to advertise it. Someone suggested it > > might fit into XEP-0157, as if you squint hard enough, it is a > > communication channel about the service. The link could also be a URL > > to a Twitter, Mastodon feed, or whatever. > > > > This is one possibility, there are others. Anyone have thoughts to > > contribute? > > 157 clearly isn’t exactly right for this, but it seems ‘close enough’ that > it’d probably be pragmatic to use it. I’d suggest registering a new field, > describing the semantics and using it in 157. We could also do not-quite-157 > by specifying a similar form extension under a different namespace but … I > don’t see a great advantage (or any great disadvantage either, really - it’s > not going to be much harder for servers or clients one way or the other, I > think. > > /K > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: [email protected] > _______________________________________________ >
Hi, That's a great idea. Not sure about XEP-0157, but if nothing better arise, why not. In addition to status page, it would be great to have a way to get future planed maintenance (at least the next one), and estimated time before service is up again. ++ Goffi _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
