[Need help] Support for Misskey quote activities (_misskey_quote) in WordPress ActivityPub plugin

[Jiwoon-Kim]

English Version

Need help
Which part of the source code should I refer to in order to implement receiving and notifying Misskey quote activities in WordPress?

The WordPress ActivityPub plugin has already adopted FEP-044f, which enables quote support with Mastodon.
However, since Misskey has not yet adopted FEP-044f, interoperability is currently limited.

Although Misskey is expected to adopt FEP-044f in the future, for compatibility with smaller forked instances it may be necessary for WordPress to properly handle the _misskey_quote property.

---

日本語バージョン

ヘルプが必要です
WordPressで Misskeyの引用アクティビティ を受信し、通知を実装するためには、ソースコードのどの部分を参照すべきでしょうか？

WordPress ActivityPubプラグイン はすでに FEP-044f を採用しており、Mastodonとの引用機能に対応しています。
しかし、MisskeyはまだFEP-044fを採用していないため、現時点では相互運用性に制限があります。

将来的にはMisskeyもFEP-044fを採用すると期待されますが、小規模なフォークインスタンスとの互換性を考慮すると、WordPress側で _misskey_quote プロパティを適切に処理できるようにする必要があります。

[Jiwoon-Kim]

Automattic/wordpress-activitypub#2272

[dosubot[bot]]

Hi @Jiwoon-Kim! I'm Dosu and I’m helping the misskey team.

To support Misskey quote activities in WordPress, you’ll want to handle the custom _misskey_quote property in incoming ActivityPub payloads. Misskey uses _misskey_quote (and sometimes quoteUrl) to indicate the URI of the quoted note in its ActivityPub objects, as defined in its JSON-LD context and used throughout its backend logic. This is distinct from FEP-044f, but the mapping is conceptually similar: extract the quoted URI from _misskey_quote and treat it as a reference to the quoted post, just as you would with Mastodon’s FEP-044f quoteUrl property.

Misskey’s backend resolves and attaches the quoted note using this property, and outgoing federation populates both _misskey_quote and quoteUrl for compatibility with other platforms. For WordPress, you can adapt your existing FEP-044f quote handling logic to also check for _misskey_quote in incoming notes, extract the URI, and import/display the quote as a custom comment type or similar entity, as proposed in issue #2272. This approach will ensure compatibility with Misskey and its forks, even before full FEP-044f adoption. See the technical details and discussion in Misskey issue #16590 and the Misskey backend implementation.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[KisaragiEffective]

(and sometimes quoteUrl)

This is false claim. It always uses _misskey_quote. It's range is URI which "resolves" to the source note.