~samwhited/xmpp

e62e47f8f890088a25a76c037f8cb98b1144fabf — Sam Whited 9 months ago 5c80921
design: answer question in MAM design doc

The difference between after and after-id is the value of count (if
set), so no changes need to be made and this question can be removed and
counted as answered.

Signed-off-by: Sam Whited <sam@samwhited.com>
1 files changed, 1 insertions(+), 3 deletions(-)

M design/110_mam.md
M design/110_mam.md => design/110_mam.md +1 -3
@@ 1,7 1,7 @@
# Title

**Author(s):** Sam Whited <sam@samwhited.com>  
**Last updated:** 2021-02-23  
**Last updated:** 2021-02-24  
**Discussion:** https://mellium.im/issue/110

## Abstract


@@ 118,8 118,6 @@ func (*Iter) Set() paging.Set {}
  before allowing the user to make requests that include extended querying?
- Instead can we discover the form first and check if it has these fields (which
  presumably also means it supports `<flip-page/>` as well)?
- Does it matter if you include `<after>` in Result Set management, but also set
  `after-id` in the MAM form? Does the latest ID win?
- How do we query for metadata?
- Can we recommend a good querying strategy for clients in this package and make
  it the default or a special easy to use function?