<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/doap/xmpp-style.xsl" type="text/xsl"?>
<rdf:RDF
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:doap="http://usefulinc.com/ns/doap#"
  xmlns:xmpp="https://xmpp.org/ns/doap#">
  <doap:Project>
    <doap:name>Wimsy</doap:name>
    <doap:shortdesc xml:lang="en">Cross-platform XMPP client built with Flutter.</doap:shortdesc>
    <doap:description xml:lang="en">
      Wimsy is a cross-platform XMPP client focused on modern server support and TLS-first connections.
    </doap:description>

    <doap:homepage rdf:resource="https://github.com/dwd/Wimsy"/>
    <doap:download-page rdf:resource="https://github.com/dwd/Wimsy/releases"/>
    <doap:bug-database rdf:resource="https://github.com/dwd/Wimsy/issues"/>
    <doap:logo rdf:resource="https://raw.githubusercontent.com/dwd/Wimsy/main/web/icons/Icon-512.png"/>

    <doap:repository>
      <doap:GitRepository>
        <doap:location rdf:resource="https://github.com/dwd/Wimsy.git"/>
        <doap:browse rdf:resource="https://github.com/dwd/Wimsy"/>
      </doap:GitRepository>
    </doap:repository>

    <doap:programming-language>Dart</doap:programming-language>
    <doap:license rdf:resource="https://opensource.org/licenses/MIT"/>

    <doap:os>Android</doap:os>
    <doap:os>Linux</doap:os>
    <doap:os>macOS</doap:os>
    <doap:os>Windows</doap:os>
    <doap:os>Web</doap:os>

    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0004.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0016.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0030.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0045.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0047.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0054.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0055.html"/>
        <xmpp:status>partial</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0059.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0066.html"/>
        <xmpp:status>partial</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0084.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0085.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0115.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0122.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0141.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0153.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0156.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0166.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0167.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0293.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0163.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0184.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0191.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0198.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0199.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0203.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0234.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0237.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0245.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0249.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0261.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0280.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0320.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0258.html"/>
        <xmpp:status>partial</xmpp:status>
        <xmpp:note xml:lang="en">Renders an incoming message's security label as a coloured chip, for both one-to-one chats and MUC rooms, preferring a marking derived by parsing the primary label against a known security policy and falling back to the server-provided display marking (flagged with a warning) when that isn't possible. On connect, fetches and caches the SPIF security policies loaded on the user's own server via the Spiffing Openfire plugin's policy IQHandler (urn:xmpp:sec-label:policy:0), registering them so subsequent labels can be parsed. For outgoing messages, also fetches the label catalog (urn:xmpp:sec-label:catalog:2) once per session on connect and offers a compose-bar picker (for both one-to-one chats and MUC rooms) to attach a catalog entry, or to build a brand-new label against a known policy using an interactive classification/category editor; the chosen label is attached to the next outgoing message only (not sticky across messages) and previewed as a chip while staged. The catalog is currently fetched without a "to" attribute, so it is not scoped/filtered by the intended recipient's clearance; peer-clearance-aware catalog filtering is not yet implemented, which is why status remains partial.</xmpp:note>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0308.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0313.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0333.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0338.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0352.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0359.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0363.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0368.html"/>
        <xmpp:status>complete</xmpp:status>
        <xmpp:note xml:lang="en">Certificates that fail standard CA validation (e.g. self-signed) are not accepted automatically: the user is shown the certificate's subject, issuer and SHA-256 fingerprint and asked to trust it before the connection proceeds, with the decision remembered per-server for future connections.</xmpp:note>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0373.html"/>
        <xmpp:status>complete</xmpp:status>
        <xmpp:note xml:lang="en">OpenPGP for XMPP (OX): per-account OpenPGP key pair generated via the vendored dart_pg library, with the public key published to the urn:xmpp:openpgp:0:public-keys:&lt;fingerprint&gt; and urn:xmpp:openpgp:0:metadata PEP nodes; the private key is stored only in secure storage, never in the Hive database.</xmpp:note>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0374.html"/>
        <xmpp:status>complete</xmpp:status>
        <xmpp:note xml:lang="en">OpenPGP for XMPP: Instant Messaging. Outgoing 1:1 messages are wrapped in an &lt;openpgp xmlns='urn:xmpp:openpgp:0'/&gt; element whose base64 content is an OpenPGP message encrypted to the recipient's (and the sender's own) public key and signed with the sender's private key, carrying an XML envelope/payload/body document; selectable per-conversation alongside OMEMO/OMEMO2.</xmpp:note>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0384.html"/>
        <xmpp:status>complete</xmpp:status>
        <xmpp:note xml:lang="en">OMEMO. Supports both the legacy eu.siacs.conversations.axolotl namespace (pinned to XEP-0384 v0.3.0, as deployed by Conversations/Gajim/Dino) and the modern urn:xmpp:omemo:2 namespace ("OMEMO2"), selectable per 1:1 conversation. Both share X3DH/Double Ratchet session establishment via the vendored omemo_dart library; device lists/bundles are published and fetched via PEP under each namespace's own node names. Trust is tracked per-device (TOFU by default, promotable to verified via manual fingerprint comparison) and surfaced as a padlock indicator in the chat header. The legacy-namespace payload cipher correctly uses AES-128-GCM as specified by XEP-0384 v0.3.0 (which has no ciphersuite negotiation), distinct from OMEMO2's AES-256-CBC+HMAC-SHA-256, via a small additive hook in the vendored omemo_dart library that lets the payload cipher be substituted while reusing its X3DH/Double Ratchet session machinery. For the legacy namespace, our own identity key is a genuine Curve25519 (X25519) keypair signed via XEdDSA (see https://signal.org/docs/specifications/xeddsa), matching real libsignal-based clients (Conversations/Gajim/Dino), rather than a genuine Ed25519 identity key as used by OMEMO2 -- implemented in lib/encryption/xeddsa.dart plus small additive patches to the vendored omemo_dart library (see its VENDORING.md).</xmpp:note>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0386.html"/>
        <xmpp:status>complete</xmpp:status>
        <xmpp:note xml:lang="en">Bind 2 inline resource binding via SASL2. Sends bind element with tag in authenticate, parses bound JID from success, skips legacy IQ bind when Bind 2 completes. Also recognizes resource binding when the server conveys the bound resource solely via a full-JID authorization-identifier (XEP-0388) with an empty &lt;bound/&gt; element.</xmpp:note>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0388.html"/>
        <xmpp:status>complete</xmpp:status>
        <xmpp:note xml:lang="en">Includes SCRAM authentication, user-agent binding, stream resumption inline, and IAP config-version pipelining.</xmpp:note>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0398.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0402.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0410.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0420.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0424.html"/>
        <xmpp:status>partial</xmpp:status>
        <xmpp:note xml:lang="en">Renders incoming "live retractions" (observing the &lt;retract/&gt; request itself) with struck-through body text and a "Retracted at" timestamp chip, for both 1:1 chats and MUC rooms. Authorises each retraction against the original sender: bare JID for 1:1, and XEP-0421 occupant-id (falling back to nickname) for MUC. Also renders MAM-replayed retraction tombstones - a top-level &lt;retracted stamp='.../&gt; that has already replaced a message's body in the archive, since no live &lt;retract/&gt; was seen - with a generic placeholder body ("This message was retracted.") shown struck through and the "Retracted at" chip using the tombstone's stamp; no original body or sender authorisation is available/needed in that case, since the archive is trusted. Sends outgoing retractions for our own messages (1:1 and MUC), surfaced as a "Retract" icon on the message action card for our own messages only, after a confirmation dialog; includes the recommended XEP-0428 legacy-client fallback body/&lt;fallback/&gt; marker, and applies the retraction locally immediately rather than waiting for a server echo/carbon.</xmpp:note>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0425.html"/>
        <xmpp:status>partial</xmpp:status>
        <xmpp:note xml:lang="en">Renders incoming MUC message moderation notices (the room's XEP-0422 &lt;apply-to/&gt; wrapping a &lt;moderated/&gt;/&lt;retract/&gt; element, sent by the room's own bare JID) the same way as a XEP-0424 retraction - struck-through body text - but with a "Moderated at" chip instead of "Retracted at"; when the moderator supplied a reason, the body is replaced entirely with that reason instead of being struck through. The notice is matched to the original message by its XEP-0359 archive stanza-id. No sender/occupant authorisation check is performed beyond that, since the notice itself only ever arrives from the room, which has already verified the moderator's authority. Also renders MAM-replayed moderation tombstones (a &lt;moderated by='...'&gt; wrapping &lt;retracted stamp='.../&gt; and an optional &lt;reason/&gt;, replacing the message in the archive since no live notice was seen): when a reason is present it is shown plainly in place of the lost body, otherwise a placeholder ("This message was removed by a moderator.") is shown struck through, with the "Moderated at" chip using the tombstone's stamp. Sends outgoing moderation requests (a &lt;moderate xmlns='urn:xmpp:message-moderate:0'&gt; SET IQ wrapping &lt;retract xmlns='urn:xmpp:message-retract:1'/&gt; and an optional &lt;reason/&gt;, targeting the message's XEP-0359 archive stanza-id) for other occupants' messages, surfaced as a "Moderate" icon on the message action card only when we hold the room's `moderator` role, after a dialog prompting for an optional reason (omitted from the request entirely if left blank); applies the moderation locally immediately on success rather than waiting for the room's own notice.</xmpp:note>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0428.html"/>
        <xmpp:status>partial</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0444.html"/>
        <xmpp:status>partial</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0461.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0490.html"/>
        <xmpp:status>complete</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0491.html"/>
        <xmpp:status>complete</xmpp:status>
        <xmpp:note xml:lang="en">Sending and hosting WebXDC widgets (thread-linked file-sharing/OOB attachment plus urn:xmpp:webxdc:0 state updates with document/summary/JSON payload), using the vendored flutter_webxdc plugin to render the sandboxed mini-app, for both 1:1 chats and MUC rooms; selfAddr uses the room's XEP-0421 occupant-id when disclosed via presence, falling back to the xmpp:&lt;bare jid&gt; form otherwise, and selfName derived per-chat as specified. The hosted mini-app's "share to chat" requests are relayed as an outgoing text message or file attachment to the same chat. Reopening a widget replays its full, ordered update history observed during the current app session (falling back to only the latest merged state after a restart).</xmpp:note>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0484.html"/>
        <xmpp:status>complete</xmpp:status>
        <xmpp:note xml:lang="en">FAST tokens with HT-SHA-256-NONE and HT-SHA-512-NONE, token rotation, and replay-counted QUIC 0-RTT when explicitly advertised; TLS tickets persist encrypted across restarts, with durable single-use consumption and stable client identity.</xmpp:note>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0509.html"/>
        <xmpp:status>partial</xmpp:status>
      </xmpp:SupportedXep>
    </doap:implements>
    <doap:implements>
      <xmpp:SupportedXep>
        <!-- XEP number TBD; tracked as urn:xmpp:webtransport:0 -->
        <xmpp:xep rdf:resource="https://xmpp.org/extensions/inbox/xmpp-quic-redux.html"/>
        <xmpp:status>partial</xmpp:status>
        <xmpp:note xml:lang="en">Reliable multi-stream XMPP over QUIC and WebTransport. Discovery uses the host-meta link relation urn:xmpp:webtransport:0. Datagrams are not supported.</xmpp:note>
      </xmpp:SupportedXep>
    </doap:implements>
  </doap:Project>
</rdf:RDF>
