jdev - 2023-01-16

> <metadata/> element containing information about the archive. This element MUST include <start/> and <end/> elements Isn't the MAM XEP missing the "empty archive" use case?

Wild guess: "iq error"/"item-not-found" is the correct reply when the archive is empty?

related: if a MAM query has a "with" and no message in the archive matches this "with", should the MAM server reply with an "empty result" or with an "error/item-not-found"?

nicoco, I would lean towards an empty result

and of course we should clarify this

> empty result thanks MattJ! that's for "no match 'with'" right?

Right

For metadata, I'm not sure... looking now

awesome :)

Looking at Prosody, I think it would send back an empty <metadata/> element

Not claiming that's the right behaviour, just stating this :)

Relatedly, <metadata/> is also embedded into bind2

Where it's a bit harder to just return an error

"first implementer replying in jdev defines the right behaviour" sounds good enough to me ;)

I'll bring these things up on the list, and if there are no objections, we can push an update clarifying these cases

;)

**DOAP Software Listing at xmpp.org** Hi XMPP folks! We plan to let go of our renewal policy for the software listing on xmpp.org. Until now, every maintainer had to update "last_renewed" once per year. We now have DOAP files for many actively developed clients, servers, libraries, and tools. Software providing a DOAP file would be listed in a rich list (like it is now), and software without would be listed in a simple table below, behind a "Show List" button. Check the current state our here: https://xmpp.org/software/clients/ (The announced change as stated above to be pushed.) Cheers _____________ - XEP-0453: DOAP usage in XMPP - https://xmpp.org/extensions/xep-0453.html

Uggh, so if we can't do a soap file we get to be relegated to a second class citizen? Great.

Sam, you would need a doap file, not a soap file. And you would have the support of community members to generate doap files. And in fact, I already generated one for Mellium ;)

Heh, stupid auto correct. I'm glad you're willing, though a community maintained one just seems like it will be out of date, but unless you're willing to maintain one for every project segregating projects this way still seems gross.