home.social

#quote-posts — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #quote-posts, aggregated by home.social.

fetched live
  1. @TeflonTrout :bc: he/him @Sharp Leaves Still, forcing Mastodon's culture and Mastodon's unwritten rules upon literally everyone in the Fediverse is bad.

    Maybe you haven't heard about this yet, but: The Fediverse is not only Mastodon. It has never been only Mastodon. It didn't even start with Mastodon. And it doesn't entirely work like Mastodon either.

    For starters, this means that just because you see it on Mastodon, it didn't necessarily originate on Mastodon.

    There are places in the Fediverse that are vastly older than Mastodon, and that are very different from Mastodon. Thus, they have their own culture, based on their own technology and their own features and where their users came from, and largely without any influences from Mastodon.

    The oldest still existing server software in the Fediverse is not Mastodon from 2016. It's Friendica (https://friendi.ca, https://en.wikipedia.org/wiki/Friendica, https://joinfediverse.wiki/Friendica). Friendica is essentially a mixture of a Facebook alternative and fully-featured long-form blogging. No Twitter or Mastodon influence anywhere. And Friendica first came out in May, 2010, five years and eight months before Mastodon.

    Friendica did not intrude into the Mastodon Fediverse that was created by Eugen Rochko as a Mastodon-only network. Mastodon was born into an already existing Fediverse that consisted of at least Friendica, Hubzilla (https://hubzilla.org, https://en.wikipedia.org/wiki/Hubzilla, https://joinfediverse.wiki/Hubzilla) and GNU social (https://en.wikipedia.org/wiki/GNU_social; now defunct).

    Here's how Friendica differs from Mastodon in ways that may disturb Mastodon hardliners:
    • Mastodon is hard-coded to 500 characters. This character limit is deeply engrained into Mastodon's culture.
      Friendica doesn't have an arbitrary character limit; it's limited by the maximum size of the database field for the post text. Currently, this is 16,777,215 characters. Thus, Friendica doesn't have keeping messages short in its culture, it never has, and it never will.
    • Mastodon users tend to be eager to block anyone who doesn't cut long posts into pieces of no more than 500 characters each.
      I know at least one Friendica veteran who blocks everyone upon first strike who does cut long posts into annoying strings of tiny chunks.
    • Mastodon introduced a CW field in 2017.
      Friendica has had the exact same field as a summary/abstract field since its own beginning in 2010. That, and Friendica has always had a much more efficient way of handling CWs, one that Mastodon itself adopted with version 4.0 in October, 2022. Thus, by its technology and culture, Friendica users despise misusing their abstract field to force the same CW upon everyone out there with a hot, flaming passion.
      So if you see someone "misusing" the CW field for "a subject or a summary or whatever that is," that might not be a clueless Mastodon user. Instead, it might be a Friendica user who has been around for a dozen years longer than you, who is used to living by Friendica's culture, and who knows tons more about the Fediverse than you do.
    • Friendica users are much less likely to add alt-texts to their images. That's for two reasons.
      One, Friendica's culture is not an idealised version of pre-Musk, very-left-wing Twitter's culture. It does not include attacking and punishing everyone who doesn't add 100% hand-written, 100% accurate, sufficiently detailed alt-texts to their images.
      Two, Friendica handles images drastically differently from Mastodon. Mastodon always has a nifty little entry field for alt-texts whenever you attach an image. On Friendica, images are embedded into posts rather than attached to them, like in a blog post. And oftentimes, you literally have to program the alt-text into the raw image embedding markup code.
    • On Mastodon, it's considered intrusive and reply-guying to reply to someone who hasn't mentioned you, and to whom you aren't mutually connected. You couldn't possibly have received the toot that you're replying to otherwise.
      On Friendica, that's perfectly normal. Friendica doesn't show you single messages by default. It always shows you the entire conversation thread, all the way up to the start post, with all branches. Thus, neither Friendica's technology nor Friendica's culture rules out replying to any comment in the thread.
    • Mastodon has only just introduced Twitter-style quote-posts a few months ago. With a safety feature that only works on Mastodon and GoToSocial for fear of that feature being used for harassment and dogpiling just like on Twitter. And because literally everyone on Mastodon comes from Twitter, it's actually being used for harassment and dogpiling.
      Friendica has had that very same feature since its inception in 2010, over a decade and a half longer. It has never not had this feature. It has always been able to quote-post any public message in the Fediverse. But since Friendica is not entirely populated by former Twitter users, it hasn't been used for harassment or dogpiling even once. It's only used to forward content. For most of the time, it literally was the only available way to forward a message.
    • Mastodon users tend to be very protective and defensive about their allegedly Mastodon-only Fediverse.
      Friendica users are used to being able to connect with everything that moves and then some. It's one of Friendica's key features that it speaks a whole lot of protocols, not just ActivityPub.
      Whereas Mastodon users see Mastodon as a "decentralised walled garden", Friendica users see Friendica as the gateway to the whole federated social Web plus some places that aren't, strictly speaking, federated.
    • Mastodon users will staunchly insist that "Fediverse" and "Mastodon" essentially mean the same because they believe they do. They will attack anyone who claims otherwise.
      Friendica users will staunchly insist that there's a huge difference between "Fediverse" and "Mastodon" because they actually know there is one. They will lecture anyone who claims otherwise.

    Of course, from a Mastodon point of view, it's both tempting and fully justified to tell the Friendica users that this is the Mastodon Fediverse, and that they will have to adapt the Mastodon culture and abolish their own culture or be thrown out. But for one, Mastodon's culture doesn't fit Friendica's technology.

    Besides, that'd literally be like European settlers holding Native Americans at gunpoint and forcing them to give up their own culture, adopt European culture and convert to Catholic Christianity or else. The only difference is that European settlers, unlike the Mastodon users, did not think that they were there first, and that everyone else is an intruder.

    I mean, sure, go ahead and attack anyone who doesn't strictly live by Mastodon's culture and Mastodon's rules if you think you have to. But prepare for a whole lot of defence and even counter-attacks from Pleroma, Akkoma, Misskey, Iceshrimp-JS, Iceshrimp.NET, Sharkey, GoToSocial, Hollo, snac2, Mitra, Socialhome, Friendica, Hubzilla, (streams), Forte and the rest of the non-Mastodon Fediverse.

    CC: @Jan Wildeboer

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #Fediverse #Mastodon #Friendica #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
  2. @TeflonTrout :bc: he/him @Sharp Leaves Still, forcing Mastodon's culture and Mastodon's unwritten rules upon literally everyone in the Fediverse is bad.

    Maybe you haven't heard about this yet, but: The Fediverse is not only Mastodon. It has never been only Mastodon. It didn't even start with Mastodon. And it doesn't entirely work like Mastodon either.

    For starters, this means that just because you see it on Mastodon, it didn't necessarily originate on Mastodon.

    There are places in the Fediverse that are vastly older than Mastodon, and that are very different from Mastodon. Thus, they have their own culture, based on their own technology and their own features and where their users came from, and largely without any influences from Mastodon.

    The oldest still existing server software in the Fediverse is not Mastodon from 2016. It's Friendica (https://friendi.ca, https://en.wikipedia.org/wiki/Friendica, https://joinfediverse.wiki/Friendica). Friendica is essentially a mixture of a Facebook alternative and fully-featured long-form blogging. No Twitter or Mastodon influence anywhere. And Friendica first came out in May, 2010, five years and eight months before Mastodon.

    Friendica did not intrude into the Mastodon Fediverse that was created by Eugen Rochko as a Mastodon-only network. Mastodon was born into an already existing Fediverse that consisted of at least Friendica, Hubzilla (https://hubzilla.org, https://en.wikipedia.org/wiki/Hubzilla, https://joinfediverse.wiki/Hubzilla) and GNU social (https://en.wikipedia.org/wiki/GNU_social; now defunct).

    Here's how Friendica differs from Mastodon in ways that may disturb Mastodon hardliners:
    • Mastodon is hard-coded to 500 characters. This character limit is deeply engrained into Mastodon's culture.
      Friendica doesn't have an arbitrary character limit; it's limited by the maximum size of the database field for the post text. Currently, this is 16,777,215 characters. Thus, Friendica doesn't have keeping messages short in its culture, it never has, and it never will.
    • Mastodon users tend to be eager to block anyone who doesn't cut long posts into pieces of no more than 500 characters each.
      I know at least one Friendica veteran who blocks everyone upon first strike who does cut long posts into annoying strings of tiny chunks.
    • Mastodon introduced a CW field in 2017.
      Friendica has had the exact same field as a summary/abstract field since its own beginning in 2010. That, and Friendica has always had a much more efficient way of handling CWs, one that Mastodon itself adopted with version 4.0 in October, 2022. Thus, by its technology and culture, Friendica users despise misusing their abstract field to force the same CW upon everyone out there with a hot, flaming passion.
      So if you see someone "misusing" the CW field for "a subject or a summary or whatever that is," that might not be a clueless Mastodon user. Instead, it might be a Friendica user who has been around for a dozen years longer than you, who is used to living by Friendica's culture, and who knows tons more about the Fediverse than you do.
    • Friendica users are much less likely to add alt-texts to their images. That's for two reasons.
      One, Friendica's culture is not an idealised version of pre-Musk, very-left-wing Twitter's culture. It does not include attacking and punishing everyone who doesn't add 100% hand-written, 100% accurate, sufficiently detailed alt-texts to their images.
      Two, Friendica handles images drastically differently from Mastodon. Mastodon always has a nifty little entry field for alt-texts whenever you attach an image. On Friendica, images are embedded into posts rather than attached to them, like in a blog post. And oftentimes, you literally have to program the alt-text into the raw image embedding markup code.
    • On Mastodon, it's considered intrusive and reply-guying to reply to someone who hasn't mentioned you, and to whom you aren't mutually connected. You couldn't possibly have received the toot that you're replying to otherwise.
      On Friendica, that's perfectly normal. Friendica doesn't show you single messages by default. It always shows you the entire conversation thread, all the way up to the start post, with all branches. Thus, neither Friendica's technology nor Friendica's culture rules out replying to any comment in the thread.
    • Mastodon has only just introduced Twitter-style quote-posts a few months ago. With a safety feature that only works on Mastodon and GoToSocial for fear of that feature being used for harassment and dogpiling just like on Twitter. And because literally everyone on Mastodon comes from Twitter, it's actually being used for harassment and dogpiling.
      Friendica has had that very same feature since its inception in 2010, over a decade and a half longer. It has never not had this feature. It has always been able to quote-post any public message in the Fediverse. But since Friendica is not entirely populated by former Twitter users, it hasn't been used for harassment or dogpiling even once. It's only used to forward content. For most of the time, it literally was the only available way to forward a message.
    • Mastodon users tend to be very protective and defensive about their allegedly Mastodon-only Fediverse.
      Friendica users are used to being able to connect with everything that moves and then some. It's one of Friendica's key features that it speaks a whole lot of protocols, not just ActivityPub.
      Whereas Mastodon users see Mastodon as a "decentralised walled garden", Friendica users see Friendica as the gateway to the whole federated social Web plus some places that aren't, strictly speaking, federated.
    • Mastodon users will staunchly insist that "Fediverse" and "Mastodon" essentially mean the same because they believe they do. They will attack anyone who claims otherwise.
      Friendica users will staunchly insist that there's a huge difference between "Fediverse" and "Mastodon" because they actually know there is one. They will lecture anyone who claims otherwise.

    Of course, from a Mastodon point of view, it's both tempting and fully justified to tell the Friendica users that this is the Mastodon Fediverse, and that they will have to adapt the Mastodon culture and abolish their own culture or be thrown out. But for one, Mastodon's culture doesn't fit Friendica's technology.

    Besides, that'd literally be like European settlers holding Native Americans at gunpoint and forcing them to give up their own culture, adopt European culture and convert to Catholic Christianity or else. The only difference is that European settlers, unlike the Mastodon users, did not think that they were there first, and that everyone else is an intruder.

    I mean, sure, go ahead and attack anyone who doesn't strictly live by Mastodon's culture and Mastodon's rules if you think you have to. But prepare for a whole lot of defence and even counter-attacks from Pleroma, Akkoma, Misskey, Iceshrimp-JS, Iceshrimp.NET, Sharkey, GoToSocial, Hollo, snac2, Mitra, Socialhome, Friendica, Hubzilla, (streams), Forte and the rest of the non-Mastodon Fediverse.

    CC: @Jan Wildeboer

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #Fediverse #Mastodon #Friendica #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
  3. @Pawlicker About "reply gating": This, or something similar, has been a standard feature at least on Hubzilla, (streams) and Forte from the get-go, i.e. from their respective creation on. Hubzilla has had it since 2012. All three rely heavily on permissions for anything and everything. They can make themselves and each other hide the reply button. When someone wants to comment from Mastodon or something else that doesn't understand these permissions, these three simply reject unpermitted comments before they even reach the inbox.

    On Hubzilla, the channel-wide permission to comment also includes a permission to like or dislike something. I can generally allow
    • only myself
    • only certain contacts
    • only my contacts
    • only my contacts plus those with an unapproved contact request
    • anyone on the same Hubzilla hub as me
    • anyone on Hubzilla (strangely, this does exclude (streams) channels)
    • anyone in the Fediverse
    • anyone anywhere on the Web, even without a Fediverse account
    to comment on my posts.

    In addition, I can turn comments on and off for specific posts. Mind you, if it's a reply, it isn't a post, it's a comment, and I've got no control over it.

    On (streams) and Forte, the channel-wide permission to comment is uncoupled from the permission to like or dislike. The channel-wide options are
    • only myself plus certain contacts
    • only my contacts
    • anyone in the Fediverse
    • anyone anywhere on the Web, even without a Fediverse account

    On top of that, I can generally allow comments only for a certain number of days.

    Again, I can turn comments on and off for specific posts. But I can also only allow my contacts to comment on specific posts, and I can define until when comments are allowed on specific posts.

    In all three cases, I can even choose to preview technically unpermitted comments and then decide whether I allow or reject them, one by one.

    In other words, where I am (I'm commenting from Hubzilla), this not only has been available for longer than Mastodon has even existed, but it's deeply engrained into the culture.

    About "quote gating": Friendica, Hubzilla, (streams) and Forte have all always (in Friendica's case, since 2010) had both actual quotes like on bulletin-board forums (remember the 2000s when forums were all the rage?) and Twitter-quote-tweet-style quote-posts (which literally were the only way for them to share content before they adopted Twitter-retweet-style forwarding).

    The former obviously only works in comments. Whether or not it's allowed is defined by whether or not comments are allowed.

    The latter doesn't have any permission setting, not even on Hubzilla, (streams) and Forte with the most advanced permissions systems in the whole Fediverse. That's because their inventor says that it's technologically impossible to keep people from forwarding or sharing your content in separate posts.

    If you disallow actual quote-posts, people can still copy-paste the content of your post into a new post. Unlike when you're actually being quote-posted, you won't even notice unless they mention you. Mind you, while an estimated 60% of all Mastodon users are on iPhones, and another estimated 39% are on Android phones, 100% of all Hubzilla, (streams) and Forte users are on desktop or laptop computers where copy-paste is easy-peasy. It's pretty much impossible to disallow copy-paste, and even if it was, people would resort to screenshots.

    You don't want people to quote-post your stuff? Then don't make it public. Once it's public, it's out there, and anyone can do with it whatever they please.

    Nobody really misses an actual permission for quote-posts. That's also because Hubzilla, (streams) and Forte aren't primarily a home for Twitter refugees. In fact, neither of them can even understand the ruckus about quote-posts on Mastodon, and neither can Friendica users. Hardly any of them have been on Twitter at any point in the 2020s. There's no influence of Twitter culture anywhere to be found.

    The typical path into Hubzilla is not Twitter > Musk buys Twitter > Mastodon > Hubzilla. Not even Twitter > Musk buys Twitter > Mastodon > Friendica > Hubzilla. It's Facebook > diaspora* > Friendica > Hubzilla. Or Facebook > Google+ > diaspora* > Friendica > Hubzilla. The typical path into (streams) is the same, but one step further beyond Hubzilla. The typical path into Forte is the same as into (streams), but another step further beyond (streams).

    About the iPhone: Whether or not the iPhone is a status symbol depends on where you are.

    In the USA, the iPhone is the Levi's jeans of phones. It's the Ford F-150 of phones. The allegedly all-American American phone. Most importantly, it's what everyone has.

    Over here in Germany, the iPhone is the higher-class Mercedes-Benz of phones. The iPhone 15 Pro is the 2026 Mercedes-Benz-AMG E 53 of phones. The iPhone 15 Pro Max is the 2026 Mercedes-Benz-AMG S 63 E Performance of phones, slammed suspensions, standing on polished 22" Lexani wheels, muffler cut-outs always open. In American terms, it's the 2026 Cadillac Escalade-V of phones, gold-foiled, with air-ride, standing on gold-plated 26" Bellagio spinnaz. The phone made for peacocking in rap music video clips. It's the Rolex of phones. For women, it's the genuine Prada or Fendi or Louis Vuitton handbag of phones.

    Well, and then there's the iPhone 4S with the cracked screen. It's the 1995 Mercedes-Benz E-Class of phones. Old, worn out, four-banger engine, often rusty as hell, may have been stolen at some point, but it's cheap. And most importantly, it's still a Benz, and it's a real Benz as opposed to "Baby Benz" C-Class and smaller. The Benz for those who need a Benz to show their folks how much of a winner they are, but who can't really afford one.

    Over here, the Samsung Galaxy S is the VW Golf of phones. The Americans' Ford F-150 of phones. It's what everyone has. It's the no-brainer that you buy when you don't know what to buy, so you buy what everyone buys. Still, it's expensive for what it does. But all the other brands are akin to "cheap imports" from, what, France or Italy or Japan or Korea or Romania.

    The choice of the hardcore nerds in the homeland of Chaos Computer Club and Chaos Communication Congress is never something that can only run stock Android. It's an iPhone even less. They rather buy a Google Pixel, and the first thing they do is root it immediately and install GrapheneOS. Or if they refuse to buy something from Google and/or run a Google OS (de-Googled or not), they acquire a Sony Experia, root it and install SailfishOS. Or they go straight for a Fairphone or even the new Jolla Phone or something like that. I'm pretty sure many want a true successor to the Nokia N900.

    If Google locks Android down, these nerds won't flock to Apple. Some may switch to SailfishOS which, on officially supported phones, has the Aliendalvik compatibility layer for Android apps, but only with F-Droid and neither with the Google Play Store proper nor with Micro-G. Many more will go entirely elsewhere like PostmarketOS or PureOS, also seeing as SailfishOS is payware that's half proprietary and closed-source. Or they'll forgo mobile phones entirely or keep old phones alive for as long as they can.

    About iOS apps: I guess the notion that the Fediverse equals Mastodon, something that the majorty of Mastodon users believe, is particularly wide-spread among iPhone users. And if it isn't only Mastodon, it doesn't extend beyond Mastodon, Pixelfed and PeerTube. Excluding Pixelfed and PeerTube, if Mastodon can't do it, the Fediverse as a whole can't. I mean, on top of the fact that apps made for Mastodon generally only support Mastodon features because the Mastodon Client API only supports Mastodon features, and the Mastodon Client API is all that these apps understand.

    It's particularly bad for Friendica users. If they're on Android, they may opt for a Mastodon app. There are several Android apps for Mastodon that have been reported to work with Friendica. Or they may want to try one of the dedicated Friendica apps which are at various levels of unfinished. Or they may choose the middle-ground and use Fedilab.

    But if they're on an iPhone, they'll discover that literally not even a single Mastodon iOS app works with Friendica. There is no Fedilab. And the iOS version of RaccoonForFriendica requires Test Flight, and it's probably even more incomplete than the Android version.

    In general, iPhone apps are rarely developed for the same reasons as Android apps. Most Android Fediverse apps are open-source and under a free license, and they're also or exclusively available on F-Droid. They're developed by FLOSS enthusiasts/idealists. However, these people don't develop for iOS. That's because the Apple App Store is inherently hostile towards free software, and it's completely incompatible with all versions of the GNU General Public License.

    Also, as you've already pointed out, you absolutely need a Mac to develop iOS apps. But if someone releases FLOSS apps on F-Droid, you can bet they're running GNU/Linux at home (more often Arch or a derivative than you may think), and they won't touch any corporate-made, closed-source OS with a 10-foot barge pole. They may even steer clear of anything where Novell, Red Hat or Canonical is involved.

    With hobbyist FLOSS enthusiasts out of the way of developing iPhone apps, this is only ever done by those who do it for money. Or fame and social status (same reason why they always have a fairly new iPhone). Or both. But then they discovered that the Fediverse, to them at least, is a hive of radical leftist tech nerds whom you can't impress with expensive bling-bling from big American gigacorps. They failed to gather the umpteen thousand followers they wanted. So they left for greener pastures: Bluesky. Or they even went back to their hundreds of thousands of followers on 𝕏. Doing so, they also abandoned their iPhone app development.

    By the way, none of this affects Hubzilla, (streams) and Forte. For starters, just like Friendica, all four can be installed as Progressive Web Apps. However, at least in the case of these three, there is no alternative to the Web interface whatsoever. There's an old Android app for Hubzilla named Nomad, but it's only available on F-Droid, it hasn't been worked on since December, 2019, it only runs on older Android versions and Aliendalvik, and it's only a wrapper for the Web interface anyway. For (streams) and Forte, there's zilch.

    There has been some talk about developing a native mobile Hubzilla app. It's kind of difficult, though. Generally, Hubzilla users use Hubzilla on desktop OS's. They can't imagine people daily-driving phones as their main or only end-user devices, so they think that a Hubzilla app only needs the features one would need when out and about because everyone will go back to their desktop or laptop computers anyway when they're back home.

    In reality, many users of the Hubzilla app will only use that app. They won't use Hubzilla's Web interface in a browser. They won't use it on a desktop or laptop computer either, usually because they simply don't have one. They'll resort to that app for everything. In fact, they'll perceive Hubzilla as a phone app rather than a Fediverse server application. This means that a Hubzilla mobile app will inevitably have to cover all of Hubzilla's features except those that really don't make sense in a phone app (e.g. the PDL editor). But a fully-featured Hubzilla app would be so complex, it'd make infamous K-9 Mail pale in comparison.

    Licensing is the least problem here. Hubzilla and Forte are released under the MIT license, (streams) was released into the public domain. So I guess putting an app for either of them under the MIT license would be an option, one that's fairly compatible with the Apple App Store even. It's just that this app would be bound to be an absolute monster.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #ReplyControl #Permissions #MastodonApp #MastodonApps #FediverseApp #FediverseApps #iOS #iOSApp #iOSApps #iPhone #iPhoneApp #iPhoneApps #Android #AndroidApp #AndroidApps
  4. @Pawlicker About "reply gating": This, or something similar, has been a standard feature at least on Hubzilla, (streams) and Forte from the get-go, i.e. from their respective creation on. Hubzilla has had it since 2012. All three rely heavily on permissions for anything and everything. They can make themselves and each other hide the reply button. When someone wants to comment from Mastodon or something else that doesn't understand these permissions, these three simply reject unpermitted comments before they even reach the inbox.

    On Hubzilla, the channel-wide permission to comment also includes a permission to like or dislike something. I can generally allow
    • only myself
    • only certain contacts
    • only my contacts
    • only my contacts plus those with an unapproved contact request
    • anyone on the same Hubzilla hub as me
    • anyone on Hubzilla (strangely, this does exclude (streams) channels)
    • anyone in the Fediverse
    • anyone anywhere on the Web, even without a Fediverse account
    to comment on my posts.

    In addition, I can turn comments on and off for specific posts. Mind you, if it's a reply, it isn't a post, it's a comment, and I've got no control over it.

    On (streams) and Forte, the channel-wide permission to comment is uncoupled from the permission to like or dislike. The channel-wide options are
    • only myself plus certain contacts
    • only my contacts
    • anyone in the Fediverse
    • anyone anywhere on the Web, even without a Fediverse account

    On top of that, I can generally allow comments only for a certain number of days.

    Again, I can turn comments on and off for specific posts. But I can also only allow my contacts to comment on specific posts, and I can define until when comments are allowed on specific posts.

    In all three cases, I can even choose to preview technically unpermitted comments and then decide whether I allow or reject them, one by one.

    In other words, where I am (I'm commenting from Hubzilla), this not only has been available for longer than Mastodon has even existed, but it's deeply engrained into the culture.

    About "quote gating": Friendica, Hubzilla, (streams) and Forte have all always (in Friendica's case, since 2010) had both actual quotes like on bulletin-board forums (remember the 2000s when forums were all the rage?) and Twitter-quote-tweet-style quote-posts (which literally were the only way for them to share content before they adopted Twitter-retweet-style forwarding).

    The former obviously only works in comments. Whether or not it's allowed is defined by whether or not comments are allowed.

    The latter doesn't have any permission setting, not even on Hubzilla, (streams) and Forte with the most advanced permissions systems in the whole Fediverse. That's because their inventor says that it's technologically impossible to keep people from forwarding or sharing your content in separate posts.

    If you disallow actual quote-posts, people can still copy-paste the content of your post into a new post. Unlike when you're actually being quote-posted, you won't even notice unless they mention you. Mind you, while an estimated 60% of all Mastodon users are on iPhones, and another estimated 39% are on Android phones, 100% of all Hubzilla, (streams) and Forte users are on desktop or laptop computers where copy-paste is easy-peasy. It's pretty much impossible to disallow copy-paste, and even if it was, people would resort to screenshots.

    You don't want people to quote-post your stuff? Then don't make it public. Once it's public, it's out there, and anyone can do with it whatever they please.

    Nobody really misses an actual permission for quote-posts. That's also because Hubzilla, (streams) and Forte aren't primarily a home for Twitter refugees. In fact, neither of them can even understand the ruckus about quote-posts on Mastodon, and neither can Friendica users. Hardly any of them have been on Twitter at any point in the 2020s. There's no influence of Twitter culture anywhere to be found.

    The typical path into Hubzilla is not Twitter > Musk buys Twitter > Mastodon > Hubzilla. Not even Twitter > Musk buys Twitter > Mastodon > Friendica > Hubzilla. It's Facebook > diaspora* > Friendica > Hubzilla. Or Facebook > Google+ > diaspora* > Friendica > Hubzilla. The typical path into (streams) is the same, but one step further beyond Hubzilla. The typical path into Forte is the same as into (streams), but another step further beyond (streams).

    About the iPhone: Whether or not the iPhone is a status symbol depends on where you are.

    In the USA, the iPhone is the Levi's jeans of phones. It's the Ford F-150 of phones. The allegedly all-American American phone. Most importantly, it's what everyone has.

    Over here in Germany, the iPhone is the higher-class Mercedes-Benz of phones. The iPhone 15 Pro is the 2026 Mercedes-Benz-AMG E 53 of phones. The iPhone 15 Pro Max is the 2026 Mercedes-Benz-AMG S 63 E Performance of phones, slammed suspensions, standing on polished 22" Lexani wheels, muffler cut-outs always open. In American terms, it's the 2026 Cadillac Escalade-V of phones, gold-foiled, with air-ride, standing on gold-plated 26" Bellagio spinnaz. The phone made for peacocking in rap music video clips. It's the Rolex of phones. For women, it's the genuine Prada or Fendi or Louis Vuitton handbag of phones.

    Well, and then there's the iPhone 4S with the cracked screen. It's the 1995 Mercedes-Benz E-Class of phones. Old, worn out, four-banger engine, often rusty as hell, may have been stolen at some point, but it's cheap. And most importantly, it's still a Benz, and it's a real Benz as opposed to "Baby Benz" C-Class and smaller. The Benz for those who need a Benz to show their folks how much of a winner they are, but who can't really afford one.

    Over here, the Samsung Galaxy S is the VW Golf of phones. The Americans' Ford F-150 of phones. It's what everyone has. It's the no-brainer that you buy when you don't know what to buy, so you buy what everyone buys. Still, it's expensive for what it does. But all the other brands are akin to "cheap imports" from, what, France or Italy or Japan or Korea or Romania.

    The choice of the hardcore nerds in the homeland of Chaos Computer Club and Chaos Communication Congress is never something that can only run stock Android. It's an iPhone even less. They rather buy a Google Pixel, and the first thing they do is root it immediately and install GrapheneOS. Or if they refuse to buy something from Google and/or run a Google OS (de-Googled or not), they acquire a Sony Experia, root it and install SailfishOS. Or they go straight for a Fairphone or even the new Jolla Phone or something like that. I'm pretty sure many want a true successor to the Nokia N900.

    If Google locks Android down, these nerds won't flock to Apple. Some may switch to SailfishOS which, on officially supported phones, has the Aliendalvik compatibility layer for Android apps, but only with F-Droid and neither with the Google Play Store proper nor with Micro-G. Many more will go entirely elsewhere like PostmarketOS or PureOS, also seeing as SailfishOS is payware that's half proprietary and closed-source. Or they'll forgo mobile phones entirely or keep old phones alive for as long as they can.

    About iOS apps: I guess the notion that the Fediverse equals Mastodon, something that the majorty of Mastodon users believe, is particularly wide-spread among iPhone users. And if it isn't only Mastodon, it doesn't extend beyond Mastodon, Pixelfed and PeerTube. Excluding Pixelfed and PeerTube, if Mastodon can't do it, the Fediverse as a whole can't. I mean, on top of the fact that apps made for Mastodon generally only support Mastodon features because the Mastodon Client API only supports Mastodon features, and the Mastodon Client API is all that these apps understand.

    It's particularly bad for Friendica users. If they're on Android, they may opt for a Mastodon app. There are several Android apps for Mastodon that have been reported to work with Friendica. Or they may want to try one of the dedicated Friendica apps which are at various levels of unfinished. Or they may choose the middle-ground and use Fedilab.

    But if they're on an iPhone, they'll discover that literally not even a single Mastodon iOS app works with Friendica. There is no Fedilab. And the iOS version of RaccoonForFriendica requires Test Flight, and it's probably even more incomplete than the Android version.

    In general, iPhone apps are rarely developed for the same reasons as Android apps. Most Android Fediverse apps are open-source and under a free license, and they're also or exclusively available on F-Droid. They're developed by FLOSS enthusiasts/idealists. However, these people don't develop for iOS. That's because the Apple App Store is inherently hostile towards free software, and it's completely incompatible with all versions of the GNU General Public License.

    Also, as you've already pointed out, you absolutely need a Mac to develop iOS apps. But if someone releases FLOSS apps on F-Droid, you can bet they're running GNU/Linux at home (more often Arch or a derivative than you may think), and they won't touch any corporate-made, closed-source OS with a 10-foot barge pole. They may even steer clear of anything where Novell, Red Hat or Canonical is involved.

    With hobbyist FLOSS enthusiasts out of the way of developing iPhone apps, this is only ever done by those who do it for money. Or fame and social status (same reason why they always have a fairly new iPhone). Or both. But then they discovered that the Fediverse, to them at least, is a hive of radical leftist tech nerds whom you can't impress with expensive bling-bling from big American gigacorps. They failed to gather the umpteen thousand followers they wanted. So they left for greener pastures: Bluesky. Or they even went back to their hundreds of thousands of followers on 𝕏. Doing so, they also abandoned their iPhone app development.

    By the way, none of this affects Hubzilla, (streams) and Forte. For starters, just like Friendica, all four can be installed as Progressive Web Apps. However, at least in the case of these three, there is no alternative to the Web interface whatsoever. There's an old Android app for Hubzilla named Nomad, but it's only available on F-Droid, it hasn't been worked on since December, 2019, it only runs on older Android versions and Aliendalvik, and it's only a wrapper for the Web interface anyway. For (streams) and Forte, there's zilch.

    There has been some talk about developing a native mobile Hubzilla app. It's kind of difficult, though. Generally, Hubzilla users use Hubzilla on desktop OS's. They can't imagine people daily-driving phones as their main or only end-user devices, so they think that a Hubzilla app only needs the features one would need when out and about because everyone will go back to their desktop or laptop computers anyway when they're back home.

    In reality, many users of the Hubzilla app will only use that app. They won't use Hubzilla's Web interface in a browser. They won't use it on a desktop or laptop computer either, usually because they simply don't have one. They'll resort to that app for everything. In fact, they'll perceive Hubzilla as a phone app rather than a Fediverse server application. This means that a Hubzilla mobile app will inevitably have to cover all of Hubzilla's features except those that really don't make sense in a phone app (e.g. the PDL editor). But a fully-featured Hubzilla app would be so complex, it'd make infamous K-9 Mail pale in comparison.

    Licensing is the least problem here. Hubzilla and Forte are released under the MIT license, (streams) was released into the public domain. So I guess putting an app for either of them under the MIT license would be an option, one that's fairly compatible with the Apple App Store even. It's just that this app would be bound to be an absolute monster.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #ReplyControl #Permissions #MastodonApp #MastodonApps #FediverseApp #FediverseApps #iOS #iOSApp #iOSApps #iPhone #iPhoneApp #iPhoneApps #Android #AndroidApp #AndroidApps
  5. If you think replies and boosts are few and far between on Mastodon, wait until (improved) client support to make and show quote posts.

    #Mastodon #quotePosts #socialmedia

  6. If you think replies and boosts are few and far between on Mastodon, wait until (improved) client support to make and show quote posts.

    #Mastodon #quotePosts #socialmedia

  7. @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
  8. @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
  9. @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
  10. @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
  11. 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.
    And if you've really paid attention:
    • 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
  12. 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.
    And if you've really paid attention:
    • 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
  13. 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.

  14. 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.

  15. @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
  16. @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
  17. @davetron5000

    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...

  18. @davetron5000

    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...

  19. 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

  20. 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

  21. @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

    #quoteposts #Fedilab #bug #mastodon

  22. @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

  23. ✅ 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.

    #quoteposts #Fedilab #nobug #mastodon

  24. ✅ 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.

    #quoteposts #Fedilab #nobug #mastodon

  25. 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.

    tilde.zone/@skylar/11605358459

    @mastodon #QuotePosts

  26. 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.

    tilde.zone/@skylar/11605358459

    @mastodon #QuotePosts

  27. @⚝ 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
  28. A Guide to Implementing ActivityPub in a Static Site (or Any Website) - Part 9: Quote Posts

    Summary:

    Find the index and earlier parts of this series here.

    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

    Find the index and earlier parts of this series here.

    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:

    1. Simple share: Just boost with no commentary\
    2. 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:

    1. Modify the Notes JSON to include that the notes are quotable.
    2. 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 @context from 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, and GetCreateNote methods.

    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 approved
    

    Checkout 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

  29. #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.)

    #quotes #QuotePosts #quoots

  30. #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.)

    #quotes #QuotePosts #quoots

  31. A Guide to Implementing ActivityPub in a Static Site (or Any Website) - Part 9: Quote Posts

    Summary:

    Find the index and earlier parts of this series here.

    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

    Find the index and earlier parts of this series here.

    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:

    1. Simple share: Just boost with no commentary (or reply)
    2. 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:

    1. Modify the Notes JSON to assert that the notes are quotable.
    2. 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 @context from 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 GetNote method.

    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 approved
    
    

    Checkout 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

  32. A Guide to Implementing ActivityPub in a Static Site (or Any Website) - Part 9: Quote Posts

    Summary:

    Find the index and earlier parts of this series here.

    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

    Find the index and earlier parts of this series here.

    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:

    1. Simple share: Just boost with no commentary (or reply)
    2. 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:

    1. Modify the Notes JSON to assert that the notes are quotable.
    2. 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 @context from 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 GetNote method.

    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 approved
    
    

    Checkout 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

  33. RE: mastodon.ml/@vint/115962398984

    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

    #Mastodon #MastodonWeb #QuotePosts #QuoteToots #QuoteBoost

  34. RE: mastodon.ml/@vint/115962398984

    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

  35. 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.

    #ActivityPub #QuotePosts #FEP044f

  36. 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.

    #ActivityPub #QuotePosts #FEP044f

  37. @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 (!group instead of @group on Friendica, @!group on 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 @group mentions. That's because Mastodon & Co. don't know !group and @!group mentions.

    (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
  38. @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 (!group instead of @group on Friendica, @!group on 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 @group mentions. That's because Mastodon & Co. don't know !group and @!group mentions.

    (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
  39. @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
  40. @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
  41. 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.

  42. 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.

  43. #Tusky est en passe de devenir illisible avec l'arrivée et l'utilisation à tort et à travers des #QuotePosts #QuoteToots 😩😖

  44. 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.

    #Mastodon #QuotePosts