<p>XQ</p><p><a href="https://github.com/misskey-dev/xq" rel="nofollow"><span class="invisible">https://</span>github.com/misskey-dev/xq</a></p><p>This must be a part of the plan to turn Misskey into proprietary silo. ATProto and Nostr creators at least tried to solve a real problem, but arguments for creating this protocol are incredibly weak:</p><p>>Messages are in plain JSON format, which is wasteful</p><p>Message size is not a bottleneck in Fediverse.</p><p>>Having schema definitions</p><p><a href="https://json-schema.org/" rel="nofollow"><span class="invisible">https://</span>json-schema.org/</a></p><p>>Statically-typed-language-friendly structure.</p><p>Skill issue. Many Fediverse projects use statically typed languages.</p><p>>Eliminate unnecessary data and boilerplate by focusing on microblogging for its intended use</p><p>There is no boilerplate other than @context. It can be dropped without making your implementation completely incompatible with everything else.</p><p>>Allows multiple messages to be combined into a single request to reduce overhead.</p><p>Use a different inbox that supports batching:</p><p><a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/0499/fep-0499.md" rel="nofollow" class="ellipsis" title="codeberg.org/fediverse/fep/src/branch/main/fep/0499/fep-0499.md"><span class="invisible">https://</span><span class="ellipsis">codeberg.org/fediverse/fep/src</span><span class="invisible">/branch/main/fep/0499/fep-0499.md</span></a></p><p><a href="/tags/activitypub/" rel="tag">#ActivityPub</a> <a href="/tags/xq/" rel="tag">#XQ</a></p>