XSF Discussion - 2021-10-02

hey

from the MAM XEP

> The 'start' field is used to filter out messages before a certain date/time. If specified, a server MUST only return messages whose timestamp is equal to or later than the given timestamp.

(I have issues to publish messages there)

so, I was asking if there was not a typo there, i should not be "filter out messages _after_ a certain date/time" ?

*it

filter *out* message before a certain time

(there is hell of a delay to publish messages on the room)

Oh?

Working fine here

to be sure, if I send a MAM request with a <end> but without a start AND a max=50 it will return : "only the 50 latest messages before the end date"

then I can properly request pages in the history by scrolling up

edhelas: You use plain XEP-0059 for that. `<before>$id</before>`

Not sure about the use cases for filtering by timestamp. Maybe restrictions such as "don't return messages older than two weeks" in order to avoid a flood of MAM messages?

edhelas: > `<before>$id</before>` Or simply `<before/>` without `$id` if you want the most recent messages.

with before/end, the question is the same, if there is no start/after at all, but with max, will it only take the 50 latest messages before the end date/before_id

The answer is different.

ah

With before you get the latest.

start/end just adds filters on top.

max will limit to the first n messages before or after the specified ID depending on whether your '59 request says <before/> or <after/>.

Holger: the original use case for timestamp was literally for querying specific time ranges, e.g. a calendar view or something

Ah, makes sense.