On 7/19/19 7:52 AM, Florian Schmaus wrote:
> On 19.07.19 07:36, Travis Burtrum wrote:
>>> If the initiating party cannot connect via either SRV record, it
>> SHOULD perform A/ fallback to port(s) of it's choice (perhaps 443,
>> 5223, etc) because, in the absence of DNSSEC, SRV records cannot be
On Fri, Jul 19, 2019, at 18:14, Maxime Buquet wrote:
> Apart from the fact that you use the abomination that is 393, I am
> mostly curious what you're expecting with all this.
Ignoring whether it's a good fallback for reactions, I would like to
defend the beautiful XEP-0393. It's a great XEP. Mayb
On 19.07.19 19:42, Marvin W wrote:
> Hi,
>
> On 19.07.19 16:52, Georg Lukas wrote:
>> This is a long overdue feature. However, I have some principal and some
>> practical issues with that.
>>
>> 1. Referencing messages
>>
>> This is yet another XEP that creates its own encoding for "this message
>
I assumed this does not apply only to reactions, as you mentioned on
xsf@ yesterday, so I'm using this as a start for these comments.
On 2019/07/19, Georg Lukas wrote:
> 2. Backward compatibility
>
> This XEP does not provide any way for legacy clients to see reactions.
>
> This (silently) prec
Hi,
On 19.07.19 16:52, Georg Lukas wrote:
> This is a long overdue feature. However, I have some principal and some
> practical issues with that.
>
> 1. Referencing messages
>
> This is yet another XEP that creates its own encoding for "this message
> is related to that message". With MAM and "t
* Jonas Schäfer [2019-07-15 17:59]:
> Title: Message Reactions
> This specification defines a way for adding reactions to a message.
This is a long overdue feature. However, I have some principal and some
practical issues with that.
1. Referencing messages
This is yet another XEP that creates i
On 19.07.19 07:36, Travis Burtrum wrote:
> On 7/17/19 9:57 AM, Tedd Sterr wrote:
>
>> *3b) PR #796 - XEP-0368: clarify what happens when a `.` target is
>> published* - https://github.com/xsf/xeps/pull/796
>> Jonas: +1
>> Link: +1 (definitely!)
>> Georg: +1 (this is just a clarification of RFC 278
On 17.07.19 15:57, Tedd Sterr wrote:
> *3b) PR #796 - XEP-0368: clarify what happens when a `.` target is
> published* - https://github.com/xsf/xeps/pull/796
> Jonas: +1
> Link: +1 (definitely!)
> Georg: +1 (this is just a clarification of RFC 2782)
> Dave: [pending]
> Kev: [pending]
This PR adds
