jdev - 2022-11-16

fead (if you come back): I don't understand the question, but SleekXMPP is not updated anymore, I would advice to use slixmpp, its successor

I am trying to fill this doap.xml thingy for my gateway thingy. For some XEPs I don't know if it makes sense to include them as supported. For instance, I do nothing with carbons and MAM, but if the server my component is attached to support them, well... they work. Any guidance on how I should fill this?

Skipping them is fine in that case. An `<xmpp:note>` with comments is also fine.

In the Prosody DOAP I've included some things that are indirectly supported, like PEP payloads, so eh.

no xmpp:status, no xmpp:version, just an xmpp:note is OK? that would be perfect I think

Hm, is there a status for "not implemented" ?

... Link Mauve ?

A "indirectly supported" or "not directly relevant but not blocked" status might be handy

Or something in the XEPs themselves indicating relevance for clients, servers, transports, or combinations of those

nicoco: `"https://linkmauve.fr/ns/xmpp-doap#category-component"` would be fitting status can be in 'complete', 'partial', 'planned', 'deprecated', 'removed' or 'wontfix'

see https://linkmauve.fr/ns/xmpp-doap#

'wontfix' ... doesn't feel right, but might be closest

Component category is fitting indeed. I would not want to give the idea that slidge is incompatible with these XEPs, "not-implemented" or "wontfix" sounds scary. I find carbons and MAM very useful… I guess I won't list them then.

Zash: how would the compliancer handle this? ``` <implements> <xmpp:SupportedXep> <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0280.html"/> <xmpp:note>Indirectly supported by the server the component is being hosted on</xmpp:note> </xmpp:SupportedXep> </implements> ```

Without checking the code, IIRC it will assume that status is 'complete' if absent

that's alright I guess?

hi, is it possible to use an external api to handle file upload in ejabberd ?

basically, I want the file content( base64 or binary), name and or metadata, plus the room and id of the user posting it