Re: [Standards] XEP-0191 leads to stale presence?

2019-06-22 Thread Dave Cridland
On Sat, 22 Jun 2019 at 19:12, Dave Cridland wrote: > > > On Thu, 20 Jun 2019 at 20:32, Kim Alvefur wrote: > >> Hi, >> >> While working on a fix for Prosodys XEP-0191 implementation¹ regarding >> presence sent to a blocked JID to pretend that the blocking user is >> offline, and then re-send

Re: [Standards] XEP-0191 leads to stale presence?

2019-06-22 Thread Dave Cridland
On Thu, 20 Jun 2019 at 20:32, Kim Alvefur wrote: > Hi, > > While working on a fix for Prosodys XEP-0191 implementation¹ regarding > presence sent to a blocked JID to pretend that the blocking user is > offline, and then re-send presence again if they unblock. > > However, since if you block

Re: [Standards] XEP-0191 leads to stale presence?

2019-06-22 Thread Kim Alvefur
Hi, Also consider clients that do not understand XEP-0191, for which it would be even more confusing, as they would not have any way to know that the presence they've seen is stale. (Clients that implement '191 can know via blocklist push.) Having server generate unavailable presence when

[Standards] PR #793 - XEP-0166: Relax transport element requirement

2019-06-22 Thread Sergey Ilinykh
In response to Council Minutes 2019-06-19 quote from https://wiki.xmpp.org/web/XEP-Remarks/XEP-0260:_Jingle_SOCKS5_Bytestreams_Transport_Method Another problem with early (before accept) transport replace is the fact we have to send the same offer twice. For example we have S5B and IBB. The

Re: [Standards] XEP-0191 leads to stale presence?

2019-06-22 Thread Tedd Sterr
Thanks for the explanation - I obviously didn't read that very carefully (don't post late at night!) Still, it should be as if you just came online with regard to the unblocked contact - that means for both sending and receiving presence. Blocking will most likely last longer than five minutes,