#quote-posts — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #quote-posts, aggregated by home.social.
-
@Brett Coulstock You should care if you think that Gargron has invented the Fediverse as a pure Mastodon network. If you think that e.g. Friendica and Hubzilla came into the Mastodon Fediverse after the fact. If you use this thinking as a justification to force Mastodon's rules and Mastodon's culture upon Friendica and Hubzilla users because you take them for intruders in a place where they don't rightfully belong.
Because Friendica and Hubzilla did not intrude into Mastodon's Fediverse. They were in the Fediverse before Mastodon.
You should care if you think that posting more than 500 characters is bad behaviour as it goes against "the Fediverse culture".
Because that "Fediverse culture" is only Mastodon's culture. And the culture on Friendica and Hubzilla, which pre-dates Mastodon itself by years, knows no character limits.
You should care if you think that Gargron is evil for introducing quote-posts to the Fediverse.
Because it was actually Mike Macgirvin, creator of Friendica and Hubzilla, who did that. In 2010. 16 years before now. Almost 6 years before Mastodon was even made.
And because just about everything that isn't Mastodon could quote-post Mastodon toots before Mastodon users even considered quote-posts evil.
You should care if you wish for "the Fediverse" to introduce certain new features. Like reply control. Or better list handlings. Or groups. Or even only more characters.
Because "the Fediverse" does have all these features. Just Mastodon doesn't have them. But Mastodon is not the Fediverse.
You should care if you don't want "the Fediverse" to ever introduce certain features. Like a higher default character limit. Or text formatting.
Because the Fediverse already has such features. As in, it can use these features in posts which it then sends to Mastodon. And there's nothing, absolutely nothing that Mastodon and its users can do against it. Except for muting and blocking.
You should care if you find it easier to use "Mastodon" and "Fediverse" synonymously, and all this "nitpicking" about when it's "Mastodon" and when it's "Fediverse" enrages you.
Because it enrages users in the non-Mastodon Fediverse when people say right into their faces that they toot. And/or that they're on Mastodon and therefore bound to the exact same rules and the exact same culture as everyone else on Mastodon. And they will so very much not let you have your way.
All these are things which, unfortunately, those who have never experienced anything else in the Fediverse than Mastodon will hardly ever understand.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
@craftxbox No, it's about more than every other Mastodon user thinking that the Fediverse equals Mastodon.
Most of the rest still think (or they think they know):- The Fediverse started with Mastodon. Gargron has invented the Fediverse.
- Everything that isn't Mastodon is either designed as a Mastodon add-on (Pixelfed, PeerTube etc.), or if it clearly isn't that, it's an intruder into the Mastodon Fediverse.
- If Mastodon doesn't have a feature, the Fediverse doesn't have that feature. This also means that if they succeed at keeping Mastodon from introducing a feature that they don't want, the whole Fediverse will never have it.
There are Mastodon users who wish for "the Fediverse" (they mean Mastodon because that's all they know) to introduce some feature, blissfully unaware that this feature is all over the Fediverse outside of Mastodon.
There are Mastodon users who "know for a fact" that Mastodon has just introduced quote-posts to the Fediverse, including an opt-out that works Fediverse-wide. They're blissfully unaware that a) Friendica and Hubzilla have been able to quote-post literally every single last public Mastodon toot since Mastodon's launch in 2016, and b) they both still are, opt-out or not.
And then there are those who spend two years or more thinking the entire Fediverse is a 500-character microblogging service, and who shit brix in sheer terror and hammer on the block button in sheer panic whenever a "toot" with more than 500 characters shows up in their timeline.
And, of course, those who try hard to force Mastodon's culture and Mastodon's rules, both of which are geared towards Mastodon and Mastodon only, upon users of server applications that are very very much not Mastodon. Because they think that Mastodon culture = Fediverse culture. And who, at the same time, fight everyone who suggests they do something that isn't inline with their perception of Mastodon's culture and rules.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse -
CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
When you see it, you'll shit brix: The Hubzilla timeline.
The "it" that you're supposed to see is:- The Fediverse did, in fact, not start with Mastodon.
There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
Mastodon came into an already existing Fediverse with servers and users and content and a culture.
The Fediverse has never been only Mastodon. And it will never be. - The Fediverse had quote-posts almost 6 years before Mastodon.
(Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.) - The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
- The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
- The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
- The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
- The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters. - The Fediverse had full rich-text formatting almost 6 years before Mastodon.
The Fediverse could generate bold type, italics, underline,code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.
Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse - The Fediverse did, in fact, not start with Mastodon.
-
Given the intensity of debate about and at times shrill opposition to #quoteposts here on #mastodon the actual practice over a couple of months has been surprisingly nice and relaxed.
Decent defaults and fine-grained user controls go a long way.
-
An #Appalachian saying...
What we give doesn't always return, but what we give is always what we are.
-
@Justin Crozer @Stefan Bohacek @Lentävä Kalakukko @Roni Rolle Laukkarinen Whenever I see Mastodon users talk about "culture" in a Fediverse context, I have to wonder: What exactly do they refer to when they talk about "culture"?
Is it Fediverse culture? As in, overarching, software-independent Fediverse culture?
As in, taking into consideration that Fediverse server applications that aren't Mastodon, e.g. Misskey or Sharkey or Friendica or Hubzilla, have different cultures than Mastodon?
Recognising a post or a comment from one of these applications, acknowledging that it comes from a place with a different history, a different set of features and thus a different culture than Mastodon and refraining from enforcing Mastodon's unwritten rules against it?
Or does "culture" only refer to Mastodon's culture? Does it reject or completely disregard all cultures in the Fediverse that aren't Mastodon's and demand the whole Fediverse adopt Mastodon's culture and only Mastodon's culture?
Do these "bad eggs" include users who post more than 500 characters at once (which, by the way, is perfectly normal everywhere outside of Mastodon)?
Do these "bad eggs" include users who reply to people who haven't mentioned them first, and whom they aren't mutually following either (which, by the way, is perfectly normal in large parts of the non-Mastodon Fediverse, too)?
Do these "bad eggs" include users who quote-post Mastodon toots that must not be quote-posted (because they've had quote-posts for much longer than Mastodon, but without a no-quote flag so they can't see Mastodon's no-quote flag)?
Do these "bad eggs" incllude users who "misuse" Mastodon's CW field for summaries (because they have literally had the exact same text field as a summary field for seven years longer than Mastodon has had it as a CW field, and because having a summary field makes a whole lot of sense if your character limit is not 500, but over 16.7 million)?
Do these "bad eggs" include users who use more than four hashtags in one post (because, unlike Mastodon, the places where they are have filtering as well as automatically having messages hidden behind CW buttons deeply engrained into their cultures, but this requires the appropriate keywords to be present)?
If so, then this explains why only Mastodon users can enjoy significant reach on Mastodon: Everyone else is mass-blocked for misbehaving by Mastodon's standards.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #MastodonCulture #MastodonCentricity #MastodonNormativity -
Exactly, and link-pasting is exactly what I've done ever since I got on #Mastodon
#QuotePosting was an enormous #MoralPanic about four years ago because #Twitter had it and #Mastodon didn't and all the big techy-bro rags convinced #Gargron that he was discouraging new migrants from Twitter because Mastodon didn't have #QuotePosts
Took 'em about three years to do it, and everyone pretty much ignored quote posts when they were finally implemented, a lot because people could opt-out if they wanted and no one took them seriously
IMO, YMMV...
-
As I mentioned in a post a week or 2 back, the vanilla Mastodon web app is now better for most purposes than the third-party ones I've tried
(@enafore, @elk, @phanpy, happy to go into detail on why if this helps). Plus, now that I'm home I use my laptop a lot more (on mobile I tend to use native apps, which are pretty good; @moshidon, @Fedilab (?), @pachli).Using the Mastodon web app more has helped me understand the logic behind the Quote Post feature.
(1/2)
#UX #FediverseUX #QuotePosts -
@joergi
I thought the same thing but eventually I realized the app isn't loading the toot correctly after posting rather than having an issue with actually quoting. Try quoting and then view your quoted post in a browser (or wait a while as, for some reason, fedilab will actually start displaying it correctly
@apps -
✅ Fixed: the moved quoted button was the problem for me. I saw it now by accident.
----------Does anyone else have issues doing quote posts with @apps ?
It always worked, but it's not working anymore.I already deleted and reinstalled Fedilab.
I tried the official Mastodon app, and there it worked, so it's not a problem with my account.
Asking first here before filling out the bug report tomorrow.
-
I can't. Mastodon's poorly-implemented Quote Posts just offers "Post pending" for this one. By the time permission is granted (by someone anywhere on the planet, asleep or not), the post is long gone. This is streaming media, not a blog.
https://tilde.zone/@skylar/116053584596797331
@mastodon #QuotePosts
-
@⚝ Mirko ⚝
die Adminbubble dort ist sehr viel ausgeglichener und lässt vor allem andere Plattformen in Ruhe.
Mindestens die Hälfte von denen weiß doch gar nicht, daß es auch noch andere Fediverse-Serveranwendungen gibt. Für die ist das Fediverse gleich Mastodon. Und von denen, die das wissen, wissen die allermeisten nicht, was die anderen Anwendungen können.
Warum hat die "Mastodon-Community" beispielsweise nie gefordert, Pleroma, Akkoma, Misskey, die Forkeys, Friendica, Hubzilla usw. zu deföderieren, weil die alle in der Lage sind, jeden öffentlichen Mastodon-Tröt widerstandslos zu quote-posten? Weil auf Mastodon praktisch niemand weiß, daß die dazu in der Lage sind. Wüßten die das, hätten sie längst die Messer gewetzt und die totale Deföderation gefordert.
Außerdem wird man auf diesen Serveranwendungen immer wieder von Mastodon-Nutzern diskriminiert oder gar attackiert. Man soll sich gefälligst an die "Fediverse-Kultur", will sagen, Mastodon-Kultur halten (was impliziert, daß man die eigene Kultur über Bord werfen soll). Man soll niemals mehr als 500 Zeichen posten. Man soll "alle notwendigen" CWs ins CW-Feld eintragen (also Friendicas Abstrakt-Feld bzw. Hubzillas Zusammenfassungsfeld) und es gar keinen Fall für irgendetwas anderes benutzen. Und so weiter.
Derweil beharren praktisch alle Mastodon-Nutzer darauf, daß das nie passiert. Weil sie nie mitbekommen, daß das passiert. Ihnen selbst passiert es ja nicht, weil sie sich als Mastodon-Nutzer eh an die Mastodon-Kultur halten, eh nicht mehr als 500 Zeichen haben, das CW-Feld nur als CW-Feld kennen usw. Und wenn es ihnen nicht passiert, dann sind sie der felsenfesten Überzeugung, daß es gar nicht passiert.
Das Nicht-Mastodon-Fediverse widersetzt sich ständig Mastodons Kultur und bricht ständig Mastodons ungeschriebene Regeln. Die allermeisten Mastodon-Nutzer wissen aber nicht, daß das passiert, ganz einfach, weil sie davon nichts mitbekommen. Dasselbe gilt auch für die allermeisten Mastodon-Admins.
Mastodon stellt im Fediverse irgendwo zwischen 60 und 70% der monatlich aktiven Nutzer. Aus irgendwelchen Gründen aber kommen gefühlt über 98% des Post-Aufkommens auf Mastodon von Mastodon selbst. Du kannst 4 Jahre auf Mastodon sein, 1000 Konten folgen und dich trotzdem in einer reinen Vanilla-Mastodon-Blase bewegen und erst nach diesen 4 Jahren deinen allerersten Beitrag mit über 500 Zeichen zu Gesicht bekommen. Wenn überhaupt.
Mastodon-Admins sind gegenüber dem Rest des Fediverse nicht deshalb so entspannt, weil das, was Pleroma, Misskey, Friendica usw. nach Mastodon schicken, für sie okay ist. Sondern, weil sie gar nicht wissen, was Pleroma, Misskey, Friendica usw. nach Mastodon schicken und viele von denen nie auch nur irgendwas von diesen anderen Anwendungen gehört haben. Sonst wären tausende von denen an vorderster Front mit dabei, wenn es darum geht, alles, was nicht Mastodon ist, auf Mastodon zu blockieren, das kannst du mir mal glauben.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteTröt #QuoteTröts #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebatte #QuoteTrötDebatte #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #ZeichenLimit #Zeichenlimits #ZeichenlimitMeta #CWZeichenlimitMeta #Fediverse #Mastodon #NichtNurMastodon #FediverseKultur #MastodonKultur #MastodonRegeln -
A Guide to Implementing ActivityPub in a Static Site (or Any Website) - Part 9: Quote Posts
Summary:
Quote Posts for Static Sites: A Practical Guide to FEP-044f Implementation
Transform your static blog into a consent-respecting quote-enabled node in the fediverse. This guide shows you how to implement quote post support that works with Mastodon, GoToSocial, and other ActivityPub servers while respecting author preferences.
In this guide: You’ll learn to build quote-enabled blog posts that can be responsibly shared across the fediverse
Quote Posts for Static Sites: A Practical Guide to FEP-044f Implementation
Transform your static blog into a consent-respecting quote-enabled node in the fediverse. This guide shows you how to implement quote post support that works with Mastodon, GoToSocial, and other ActivityPub servers while respecting author preferences.
In this guide: You’ll learn to build quote-enabled blog posts that can be responsibly shared across the fediverse
Why Quote Posts Matter (And Why They’re Controversial)
The User Experience Problem
Picture this: Someone finds your blog post fascinating and wants to share it with their followers, but they also want to add their own perspective or why is important. Without quote posts, they have two unsatisfying options:
- Simple share: Just boost with no commentary\
- Link sharing: Add a link to the blog post in their note
Neither option creates the rich, attributed conversations that make social media engaging.
The Solution: Consent-First Quote Implementation
We’re implementing FEP-044f: Consent-respecting quote posts in our federated blog.
What this means for your readers:
- They can quote your posts with confidence that you’ve opted in
- Their quotes include proper attribution and linking
What this means for you:
- Automatic handling of quote requests
- Future-ready for advanced moderation features (like in the fuuutuuure)
Implementation Overview
We are going to:
- Modify the Notes JSON to include that the notes are quotable.
- Modify our Index function (the only dynamic POST endpoint) to handle quote requests and send the appropriate approval back.
1. Modifying the Notes: Enhanced ActivityPub Context
What We Changed: Extended the
@contextfrom a simple string to a rich object array supporting the GoToSocial namespace.Before:
"@context": "https://www.w3.org/ns/activitystreams"After:
"@context": [ "https://www.w3.org/ns/activitystreams", { "gts": "https://gotosocial.org/ns#", "interactionPolicy": {"@id": "gts:interactionPolicy", "@type": "@id"}, "canQuote": {"@id": "gts:canQuote", "@type": "@id"}, "automaticApproval": {"@id": "gts:automaticApproval", "@type": "@id"} } ]We are also adding this section at the end of the Note:
"interactionPolicy": { "canQuote": { "automaticApproval": "https://www.w3.org/ns/activitystreams#Public" } }If you want to be specific about who can quote your post, this is where you do it, read more in here.
You can see an example of the implementation in RssUtils.cs - Updated
GetOutbox,GetNote, andGetCreateNotemethods.2: Quote Request Processing
Now we need to add the quote request handling system that processes incoming quote requests and automatically approves them based on our interaction policy.
New Components:
- QuoteRequestService: Processes incoming quote requests from the fediverse
- Auto-Approval Logic: Automatically approves public quote requests as defined in our interaction policy
- Quote Authorization: Issues authorization tokens (stamps) for approved quotes
The Quote Request Flow:
sequenceDiagram participant Requester as Fediverse User participant Inbox as Our Inbox participant QRS as QuoteRequestService participant Target as Target Instance Requester->>Inbox: QuoteRequest for our post Inbox->>QRS: Process quote request QRS->>QRS: Check interaction policy QRS->>QRS: Generate authorization stamp QRS->>Target: Send Accept + Authorization Target->>Requester: Quote approvedCheckout the implementation in the QuoteRequestService.cs.
Key Takeaways
“By implementing FEP-044f, we’re not just adding quote functionality - we’re building consent-respecting social interactions into the protocol level.”
Why This Matters:
This implementation shows how static sites can participate in modern social web standards while keeping their simplicity and performance benefits. Right now, we’re automatically allowing all public quotes, but this foundation sets us up for more granular consent controls in the future - like requiring approval for specific users or implementing follower-only quoting.
The consent-respecting approach means our content can be shared thoughtfully across the fediverse, with the infrastructure already in place to handle more sophisticated permission systems as they evolve.
Also readable in: https://maho.dev/2025/02/a-guide-to-implementing-activitypub-in-a-static-site-or-any-website-part-9-quote-posts/ by @mapache:
#fediverse #activitypub #static-sites #hugo #azure #mastodon #web-development #social-web #webfinger #http #quote-posts #fep-044f
-
The biggest and gravest crimes and sins stem from the smallest and lightest things.
#Philosophy #Quote #quotes #QuoteToots #quoteposts #Fact #facts -
#Tusky F-Droid finally has quoots and unlike the Mastodon browser interface, you can click on the number of times a post has been quoted and see all those quote posts.
(I'm slowly warming up to quotes.)
-
RE: https://mastodon.social/@MastodonEngineering/116007434602576018
Oh nice, one of the updates:
"Shorten caching of quote posts pending approval"
-
A Guide to Implementing ActivityPub in a Static Site (or Any Website) - Part 9: Quote Posts
Summary:
Quote Posts for Static Sites: A Practical Guide to FEP-044f Implementation
Transform your static blog into a consent-respecting quote-enabled node in the fediverse. This guide shows you how to implement quote post support that works with Mastodon, GoToSocial, and other ActivityPub servers while respecting author preferences.
In this guide: You’ll learn to build quote-enabled blog posts that can be responsibly shared across the fediverse
Quote Posts for Static Sites: A Practical Guide to FEP-044f Implementation
Transform your static blog into a consent-respecting quote-enabled node in the fediverse. This guide shows you how to implement quote post support that works with Mastodon, GoToSocial, and other ActivityPub servers while respecting author preferences.
In this guide: You’ll learn to build quote-enabled blog posts that can be responsibly shared across the fediverse
Why Quote Posts Matter (And Why They’re Controversial)
The User Experience Problem
Picture this: Someone finds your blog post fascinating and wants to share it with their followers, but they also want to add their own perspective or why is important. Without quote posts, they have two unsatisfying options:
- Simple share: Just boost with no commentary (or reply)
- Link sharing: Add a link to the blog post in their note
Neither option creates the rich, attributed conversations that make social media engaging.
The Solution: Consent-First Quote Implementation
We’re implementing FEP-044f: Consent-respecting quote posts in our federated blog.
What this means for your readers:
- They can quote your posts with confidence that you’ve opted in
- Their quotes include proper attribution and linking
What this means for you:
- Automatic handling of quote requests
- Future-ready for advanced moderation features (like in the fuuutuuure)
Implementation Overview
We are going to:
- Modify the Notes JSON to assert that the notes are quotable.
- Modify our Index function (the only dynamic POST endpoint) to handle quote requests and send the appropriate approval back (blanket approval).
1. Modifying the Notes: Enhanced ActivityPub Context
What We Changed: Extended the
@contextfrom a simple string to a rich object array supporting the GoToSocial namespace.Before:
"@context": "https://www.w3.org/ns/activitystreams"After:
"@context": [ "https://www.w3.org/ns/activitystreams", { "gts": "https://gotosocial.org/ns#", "interactionPolicy": {"@id": "gts:interactionPolicy", "@type": "@id"}, "canQuote": {"@id": "gts:canQuote", "@type": "@id"}, "automaticApproval": {"@id": "gts:automaticApproval", "@type": "@id"} } ]We are also adding this section at the end of the Note:
"interactionPolicy": { "canQuote": { "automaticApproval": "https://www.w3.org/ns/activitystreams#Public" } }If you want to be specific about who can quote your post, this is where you do it, read more in here.
You can see an example of the implementation in RssUtils.cs - in the
GetNotemethod.2: Quote Request Processing
Now we need to add the quote request handling system that processes incoming quote requests and automatically approves them based on our interaction policy.
New Components:
- QuoteRequestService: Processes incoming quote requests from the fediverse
- Auto-Approval Logic: Automatically approves public quote requests as defined in our interaction policy
- Quote Authorization: Issues authorization tokens (stamps) for approved quotes
The Quote Request Flow:
sequenceDiagram participant Requester as Fediverse User participant Inbox as Our Inbox participant QRS as QuoteRequestService participant Target as Target Instance Requester->>Inbox: QuoteRequest for our post Inbox->>QRS: Process quote request QRS->>QRS: Check interaction policy QRS->>QRS: Generate authorization stamp QRS->>Target: Send Accept + Authorization Target->>Requester: Quote approvedCheckout the implementation in the QuoteRequestService.cs.
Key Takeaways
By implementing FEP-044f, we’re not just adding quote functionality - we’re building consent-respecting social interactions into the protocol level.
Why This Matters:
This implementation shows how static sites can participate in modern social web standards while keeping their simplicity and performance benefits. Right now, we’re automatically allowing all public quotes, but this foundation sets us up for more granular consent controls in the future - like requiring approval for specific users or implementing follower-only quoting.
The consent-respecting approach means our content can be shared thoughtfully across the fediverse, with the infrastructure already in place to handle more sophisticated permission systems as they evolve.
Next Steps: The Quote Visualization Challenge
Now that we’ve successfully implemented the backend infrastructure for consent-respecting quote posts, we face an equally important question: How should we display these quotes on our website?
Treat quoted posts as special reply types? Quotes have different semantic meaning than replies - they’re more like “shared with commentary” So maybe create a separate “Quoted By” section similar to how we handle likes and shares?
Any ideas?
Also readable in: https://maho.dev/2026/02/a-guide-to-implementing-activitypub-in-a-static-site-or-any-website-part-9-quote-posts/ by @mapache:
#fediverse #activitypub #static-sites #hugo #azure #mastodon #web-development #social-web #webfinger #http #quote-posts #fep-044f
-
RE: https://mastodon.ml/@vint/115962398984662966
I am just really excited about this new quote-post feature. Applications include:
- translating your posts to another language (especially if you keep accounts separated)
- extending some context on-point, when you know nobody will click to read the full thread
- reiterating your old posts, with learned experience
- extending on someone else's post (I mean those that started appearing recently on supported servers), when you have something to say about it, but also want to show it off with all media attached to the original post -
Implementing QuotePosts in Loops is taking a tad longer than expected.
I don't understand why they require a QuoteRequest handshake if the interactionPolicy is public, seems overengineered and wasteful to me.
-
@Jasper Burns
Groups, part 2: Starting a thread
Okay, here comes the twist. Here is where the group magic happens.
If you want to start a new thread in that group, you have to be a member of the group account. Connected to the group account. In Mastospeak, mutually follow the group account.
Then, if you send a new post that mentions the group account, and it is not a reply to another post, then the group account will automatically quote your post and send the quote-post with your post in it to all its connections (followers).
You know quotes? Quote-posts? Like, quote-tweets? What half of Mastodon is so afraid of because it's used on Twitter only to harass and dogpile people? That's what I'm talking about. Friendica has had these quote-posts for almost 16 years, and never have they been used for harassment and dogpiling, for never has anyone used Friendica as a drop-in replacement for Twitter. Friendica calls them "shares". And Friendica has used these quote-posts in groups for almost 16 years.
That is, within Friendica (and its descendants), one thing is a wee bit different: If you're on Friendica or Hubzilla or (streams) or Forte, you have to send a DM with a special mention (!groupinstead of@groupon Friendica,@!groupon Hubzilla, (streams) and Forte) to the group account for this to happen. This automatically activates what's "mentioned only" on Mastodon and makes your post a DM.
But from Mastodon accounts and the like, it accepts public posts with@groupmentions. That's because Mastodon & Co. don't know!groupand@!groupmentions.
(2/9)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #Fediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Groups #FediGroups #FediverseGroups -
@Robert Frank Wenn man selbst nur Mastodon nutzt, fühlt es sich piepschnurzegal an. Dann nimmt man eh das ganze Fediverse als nur Mastodon wahr und die Unterschiede zwischen Mastodon und Nicht-Mastodon fast überhaupt nicht.
Wenn man selbst aber etwas ganz anderes im Fediverse nutzt als Mastodon, dann ist es immens wichtig.
Ich selbst bin nicht auf Mastodon. Ich bin auf Hubzilla (https://hubzilla.org, https://de.wikipedia.org/wiki/Hubzilla, https://hub.netzgemeinde.eu/item/0a75de76-eb27-4149-b708-f20b2f79d392). Das funktioniert völlig anders als Mastodon, das hat ein völlig anderes Konzept als Mastodon, das wird von Mastodon völlig unabhängig entwickelt. Es hat Features, die auf Mastodon unvorstellbar sind. Noch dazu ist es zehn Monate älter als Mastodon. Es geht sogar zurück auf Friendica, das mehr als fünfeinhalb Jahre älter ist als Mastodon.
Aber wie du mit eigenen Augen sehen kannst, kann ich Mastodon-Tröts nicht nur empfangen, sondern auch von Hubzilla aus kommentieren.
Wenn jemand das komplette Fediverse meint, es aber "Mastodon" nennt, dann meint er mich zwar damit, spricht mich aber nicht an. Ich bin ja nicht auf Mastodon.
Wenn jemand einen meiner Posts oder Kommentare als "Tröt" bezeichnet in der Annahme, ich sei auch auf Mastodon, dann ist beides sachlich falsch.
Wenn jemand sich wünscht, "das Fediverse" möge endlich ein bestimmtes Feature einführen, nur weil Mastodon es nicht hat, dann kann ich mir nur vor den Kopf schlagen. In den allermeisten Fällen hat Hubzilla genau dieses Feature schon zehn Monate länger, als es Mastodon überhaupt gibt. Sehr häufig hat Friendica dieses Feature schon etliche Jahre länger, als es Mastodon überhaupt gibt. Das Fediverse hat dieses Feature also. Mastodon hat es nicht, aber das Fediverse hat es.
Wenn jemand dagegen ist, daß "das Fediverse" ein bestimmtes Feature einführt, dem sei gesagt: Höchstwahrscheinlich hat das Fediverse dieses Feature schon. Mastodon nicht, aber das Fediverse. Denn höchstwahrscheinlich hatten Friendica und Hubzilla es schon immer, also auch wieder länger, als es Mastodon überhaupt gibt.
Am besten war noch der Widerstand gegen Quote-Posts. "Das Fediverse" sollte die auf gar keinen Fall einführen, sagten einige. Der Witz: Pleroma, Akkoma, Misskey, Calckey, Firefish, CherryPick, Sharkey, Iceshrimp, Catodon, GoToSocial, Mitra, Friendica, Hubzilla, (streams), Forte usw., sie alle haben Quote-Posts. Und zwar schon länger, als es diese Debatte auf Mastodon überhaupt gibt. Und sie alle (außer GoToSocial) können widerstandslos jeden, aber auch wirklich jeden Mastodon-Tröt quote-posten.
Oder damals der Widerstand gegen Volltextsuche. Auf gar keinen Fall sollte "das Fediverse" Volltextsuche haben. Nur hatte das Fediverse schon längst Volltextsuche: Friendica war schon im Mai 2010 mit eingebauter Volltextsuche an den Start gegangen.
Ach ja: Zeichenlimits. Wer "Mastodon" und "Fediverse" gleichsetzt, für den hat auch das Fediverse ein festgelegtes Limit von 500 Zeichen. Friendica und Hubzilla hatten aber nie wirklich Zeichenlimits. In deren Kultur kommen auch keine Zeichenlimits vor. Aktuell haben sie übrigens ein "Limit" von über 16,7 Millionen Zeichen. Bis auf Threads hat alles im Fediverse ein sehr viel höheres Zeichenlimit als Mastodon. Entsprechend kriegen Nicht-Mastodon-Nutzer ständig auf den Deckel, wenn sie das angeblich von Gargron für das ganze Fediverse festgeschriebene Limit von 500 Zeichen überschreiten.
Also: Das Fediverse ist nicht nur Mastodon. Das Fediverse war auch nie nur Mastodon. Das Fediverse ist nicht nur ein Twitter-Klon. Das Fediverse hat sehr viel mehr Features als Mastodon. Und das Fediverse hat auch nicht überall dieselbe Kultur und wird sie auch nie haben.
CC: @Knust @Katharina Nocun
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteTröt #QuoteTröts #QuoteBoost #QuoteBoosts #Zeichenlimit #Zeichenlimits #ZeichenlimitMeta #CWZeichenlimitMeta #Fediverse #Mastodon #NichtNurMastodon #Pleroma #Akkoma #Misskey #Calckey #Firefish #CherryPick #Sharkey #Iceshrimp #Catodon #GoToSocial #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #MastodonZentrizität #MastodonNormativität -
Yay, @medium has finally upgraded this @Mastodon instance to a version that displays #QuotePosts correctly.
(Still a version behind the latest release, so I can't actually create quote posts myself yet.)
ETA: Might have spoken too soon as it seems to be working for some posts but not others.
-
2025 updates like quote posts with anti-harassment controls boosted user growth by 30%,
https://www.webpronews.com/mastodons-2025-updates-fuel-30-growth-in-fediverse/
-
2025 updates like quote posts with anti-harassment controls boosted user growth by 30%,
https://www.webpronews.com/mastodons-2025-updates-fuel-30-growth-in-fediverse/
-
#Tusky est en passe de devenir illisible avec l'arrivée et l'utilisation à tort et à travers des #QuotePosts #QuoteToots 😩😖
-
Are there any plans to make the quotes visible to everyone, even those who are not logged in?
Since people are using quoted posts to add opinions, further context, sources, alt text and content warnings, I would really like to be able to see these in the same way that I can see who is boosting/faving a post, without being restricted by my server's mute/block list, etc.
-
Yeah I was watching it and wondering what its scope and content would be
#Gargron et al have always been suckers for mainstreaming Mastodon by adopting the most common eye-candy bling
(See, as one: #QuotePosts)
Right now I *could* download my 2025 Year-in-Review for Youtube, Twitch, Twitter, Github, etc etc
So here comes #Mastodon, always trying to stay up with All The Cool Kids
BTW I haven't seen that yet: is this on mobile of some sort?
Or it may be in the nightly that Masto dot Social is always running
*Edit*
Yeah, here it is: "End of the year recap # 22658"
"renchap
3 hours ago - SponsorMember
This has been implemented and will be there for all users in Mastodon 4.6."
Here: https://github.com/mastodon/mastodon/issues/22658#issuecomment-3655620471