Re: [Standards] XEP-0045: How to signal tombstones for destroyed rooms?

2018-07-11 Thread Daniel Gultsch
Either include status code 110 in the unavailable presence or use an error presence. The XEP is a bit fuzzy on when to use what. But I won’t be able to parse an unavailable w/o 110 So in your case (a join attempt to the tombstone) I have a slight personal preference toward error; But I’m ok with

Re: [Standards] XEP-0045: How to signal tombstones for destroyed rooms?

2018-07-11 Thread Florian Schmaus
On 11.07.2018 07:52, Jonas Wielicki wrote: > On Mittwoch, 11. Juli 2018 04:02:23 CEST Kim Alvefur wrote: >> Hello list, >> >> I have implemented tombstones for destroyed MUC rooms. My reading of the >> sacred texts did not give me enlightenment as how to inform someone >> who's attempting to enter

Re: [Standards] XEP-0045: How to signal tombstones for destroyed rooms?

2018-07-11 Thread Kevin Smith
On 11 Jul 2018, at 03:02, Kim Alvefur wrote: > > Hello list, > > I have implemented tombstones for destroyed MUC rooms. My reading of the > sacred texts did not give me enlightenment as how to inform someone > who's attempting to enter the remains of such a place. I've so far opted > to return

Re: [Standards] XEP-0045: How to signal tombstones for destroyed rooms?

2018-07-11 Thread Kim Alvefur
On Wed, Jul 11, 2018 at 07:52:55AM +0200, Jonas Wielicki wrote: > Is there a reason to not use a presence type="error"? I’d expect clients to > handle those already. Mostly becasue I simply copied code from the room destruction handler. > I’d use a type error, which encodes the semantics

[Standards] Exact hint for Result Set Management

2018-07-11 Thread Florian Schmaus
I recently submitted PR #672 to the xeps repo https://github.com/xsf/xeps/pull/672 to make users of RSM, like MAM, aware whether the result is exact or not. It received some scepticism from the council members in today's council meeting. I am to blame here as I thought the abstract motivation in

Re: [Standards] Exact hint for Result Set Management

2018-07-11 Thread Florian Schmaus
On 11.07.2018 18:01, Matthew Wild wrote: > On 11 July 2018 at 16:33, Florian Schmaus wrote: >> I recently submitted PR #672 to the xeps repo >> >> https://github.com/xsf/xeps/pull/672 >> >> to make users of RSM, like MAM, aware whether the result is exact or >> not. It received some scepticism

Re: [Standards] Exact hint for Result Set Management

2018-07-11 Thread Matthew Wild
On 11 July 2018 at 16:33, Florian Schmaus wrote: > I recently submitted PR #672 to the xeps repo > > https://github.com/xsf/xeps/pull/672 > > to make users of RSM, like MAM, aware whether the result is exact or > not. It received some scepticism from the council members in today's > council