When you quote a post on Threads, the platform uses a specific ActivityPub property called as:quoteUri to indicate the quoted post. This behavior differs from how Mastodon and other fediverse platforms handle quoting, which can cause confusion for users and developers. The quote appears as a link to the original post rather than an embedded quote card when viewed outside Threads. This article explains how Threads implements quoting via ActivityPub, what the as:quoteUri property means, and how it affects cross-platform visibility.
Key Takeaways: Threads Quote Posts in the Fediverse
- as:quoteUri property: Threads uses this ActivityPub extension to mark quoted posts instead of embedding the full quoted content.
- Mastodon compatibility: Mastodon does not display quote cards for
as:quoteUri— it shows only a plain link to the original post. - Quote visibility: Users on other fediverse servers see the quote as a mention or link, not as an inline preview.
What Is the as:quoteUri ActivityPub Property?
ActivityPub is the protocol that powers the fediverse — a network of social platforms that can communicate with each other. Threads joined this network in late 2023 by enabling fediverse sharing for public posts. When a Threads user quotes another post, the platform does not embed the full quoted content in the ActivityPub object. Instead, it attaches a property called as:quoteUri that contains the URL of the quoted post.
This approach is different from how Mastodon handles quotes. Mastodon uses the Quote activity type with the full quoted object embedded inside the object field. Threads chose a lighter method — referencing the quoted post by URI only — to reduce data size and simplify federation. The as:quoteUri property is part of the ActivityStreams vocabulary, which ActivityPub builds on.
Why Threads Uses a URI Instead of Embedding
Threads aims to keep its ActivityPub objects lightweight. Embedding the full quoted post would require fetching and storing the entire object, which increases bandwidth and storage costs. By using a URI, Threads signals that the quoted post exists elsewhere without duplicating its content. This design also respects the original author’s content ownership — the quote is a reference, not a copy.
How Mastodon and Other Platforms Interpret the Property
Mastodon does not recognize as:quoteUri as a standard quoting mechanism. When Mastodon receives a Threads post with this property, it treats the URI as a simple link. The post appears on Mastodon as a regular status with a URL in the text. Mastodon users see the link but not a quote card with the original post’s content or author. This limitation means that quote posts from Threads lose context when viewed outside the Threads app.
Steps to Verify Quote Behavior on Threads and the Fediverse
To see how Threads quote posts appear on other fediverse platforms, follow these steps. You need a public Threads account with fediverse sharing enabled and an account on a Mastodon server or another ActivityPub platform.
- Enable fediverse sharing on Threads
Open Threads and go to Profile > the two-line menu icon > Account > Fediverse sharing. Tap the toggle to turn on sharing. Your public posts will now be sent to the fediverse. - Create a quote post on Threads
Find any public post on Threads. Tap the repost icon (two arrows forming a square) and select Quote. Write your comment and tap Post. Wait a few minutes for the post to federate. - Check the post on Mastodon
Log in to your Mastodon account. Search for your Threads handle (e.g.,@username@threads.net) and find the quote post. The post will show your comment text with the quoted post’s URL as a link. There will be no embedded quote card. - Inspect the ActivityPub object
To see the raw data, open your Threads post in a browser and append.jsonto the URL. For example,https://www.threads.net/@username/post/ABC123.json. Look for theas:quoteUrifield. You will find the URI of the quoted post there.
Testing with a Fediverse Debugger
You can also use a fediverse debugger tool like fedidebug.com. Paste your Threads post URL into the tool. It will display the full ActivityPub object, including the as:quoteUri property. This method helps developers confirm that the quote property is present and correctly formatted.
Common Misconceptions and Limitations of Threads Quote Behavior
Threads quote posts do not appear on Mastodon as quote cards
Many users expect that quoting a post on Threads will create a quote card visible on Mastodon. This is not the case. Mastodon does not support the as:quoteUri property for rendering quote cards. The post appears as a plain text update with a link. To see the full quote context, Mastodon users must click the link and view the original post on Threads.
Quoted posts from Mastodon do not federate to Threads
Threads currently does not support receiving quote posts from other fediverse platforms. If a Mastodon user quotes a Threads post, the quote will not appear on Threads. Threads users will only see the original post, not the quote. This limitation is one-sided — Threads can send quotes out but cannot receive them from other platforms.
The as:quoteUri property is not a standard ActivityPub core property
ActivityPub core defines activities like Create, Like, and Announce. The as:quoteUri property is an extension from the ActivityStreams vocabulary. It is not required by the ActivityPub specification. This means that other platforms are not obligated to support it, and many do not. Threads is free to use this extension, but compatibility depends on other platforms choosing to implement it.
Threads Quote Behavior vs Mastodon Quote Behavior
| Item | Threads | Mastodon |
|---|---|---|
| Property used for quoting | as:quoteUri — a URI reference to the quoted post |
Quote activity type with embedded object |
| Quote card rendering | Renders quote cards only within Threads app | Renders quote cards natively in Mastodon and compatible clients |
| Cross-platform visibility | Quote appears as a link on other fediverse platforms | Quote appears as a card on other fediverse platforms that support the Quote activity |
| Receiving quotes from other platforms | Does not receive or display quotes from Mastodon or others | Can receive and display quotes from other Mastodon instances and some other platforms |
| Standard compliance | Uses an ActivityStreams extension, not core ActivityPub | Uses a custom activity type that is widely adopted but not part of the core spec |
Threads quote posts lose visual context when they leave the Threads app. Mastodon users see a link instead of an embedded quote. This difference stems from the distinct ActivityPub implementations chosen by each platform. Threads prioritizes lightweight objects, while Mastodon prioritizes rich embedded content.
You can now identify how Threads quote posts appear on the fediverse and understand the role of the as:quoteUri property. If you need to share a quote with full context to a Mastodon audience, consider including the quoted post’s text in your comment. For developers, checking the as:quoteUri field in ActivityPub objects helps confirm that Threads is sending the quote reference correctly. Future updates to Threads may improve quote compatibility with other platforms, but for now, the quote behavior remains one-directional and link-based outside Threads.