Re: [Standards] Syncing multi-device on XEP-0384: OMEMO

2021-02-23 Thread Paul Schaub
Hi Paul! You raise some valid points. Am 24.02.21 um 01:37 schrieb Paul L'Allier: *General message sending / carbon copy mechanism, including offline sending.* Consider that Alice and Bob each have two devices (say a desktop and a mobile, some of which may be offline at any given time).

[Standards] Syncing multi-device on XEP-0384: OMEMO

2021-02-23 Thread Paul L'Allier
Hello, I'm new here - my apologies if I ask some stupid questions or commit some terrible faux-pas. I've tried to do some searching on the mail archive with Google and not come up with answers to these questions / thoughts. Firstly, thank you for developing all those interesting and

[Standards] Message Styling Test Suite

2021-02-23 Thread Sam Whited
Hi all, After chatting earlier with someone who was implementing XEP-0393: Message Styling and answering a few questions about how things should be styled, I decided to export my tests in a language-agnostic format. Feel free to use these to test your own implementations. I'm ~99% sure they're

Re: [Standards] XEP-0393 styling directive logic still incorrect

2021-02-23 Thread Sam Whited
Nevermind then; got confused after a discussion over chat. This is exactly what I wanted, thanks for the help. —Sam On Tue, Feb 23, 2021, at 13:22, Tedd Sterr wrote: > Greedy matching means take as many characters as you can while still > satisfying the condition, i.e. find the longest match.

Re: [Standards] XEP-0393 styling directive logic still incorrect

2021-02-23 Thread Tedd Sterr
Greedy matching means take as many characters as you can while still satisfying the condition, i.e. find the longest match. Lazy matching means take the first match you find, i.e. find the shortest. In the form of regular expressions, we have: * greedy = /\*.+\*/ * lazy = /\*.+?\*/ The text

[Standards] XEP-0393 styling directive logic still incorrect

2021-02-23 Thread Sam Whited
Hi all, I recently made a change to XEP-0393 that attempted to clarify the rules for span selection (https://github.com/xsf/xeps/pull/1001). However, the text is *still* wrong and does not match the examples. The text says: > Spans are always parsed from the beginning of the byte stream to the

Re: [Standards] XML Element Ordering

2021-02-23 Thread Kevin Smith
On 23 Feb 2021, at 09:30, Dave Cridland wrote: > > > > On Mon, 22 Feb 2021 at 19:02, Florian Schmaus > wrote: > On 2/18/21 12:16 AM, Dave Cridland wrote: > > On Wed, 17 Feb 2021 at 19:22, Kevin Smith > > >

Re: [Standards] XML Element Ordering

2021-02-23 Thread Dave Cridland
On Mon, 22 Feb 2021 at 19:02, Florian Schmaus wrote: > On 2/18/21 12:16 AM, Dave Cridland wrote: > > On Wed, 17 Feb 2021 at 19:22, Kevin Smith > > wrote: > > > > On 17 Feb 2021, at 18:42, Florian Schmaus > > wrote: > > > > >