#QuoteBoost

2025-11-28
 Jupiter Rowland schrieb den folgenden Beitrag Sun, 21 Sep 2025 21:42:56 +0200 How broken-by-design are Mastodon's quote-posts? This broken.
The various issues with quote-posts on Mastodon that nobody on Mastodon is aware of; CW: long (almost 6,800 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, Mastodon looking bad in comparison with the rest of the Fediverse, quote-post meta
Okay, everyone, sit down. I'll tell you a few things about Mastodon's quote-post feature that you know nothing about. Definitely not if all you know is Mastodon. Oh, and by the way, in case you don't know yet in spite of following me: The Fediverse is not only Mastodon.

Mastodon has been quote-post-able for as long as it has been around


Eugen Rochko is bringing quote-posts to Mastodon. But he is not bringing quote-posts to the Fediverse. The Fediverse has had quote-posts for 15 years.

It was Mike Macgirvin who introduced quote-posts to the Fediverse in July, 2010, when he launched something called Mistpark back then and Friendica today (https://friendi.ca, https://en.wikipedia.org/wiki/Friendica). That was five and a half years before Mastodon was launched.

In fact, when Mastodon was launched, it immediately federated itself with Friendica and with Hubzilla, a fork of a fork of Friendica by Friendica's own creator which has quote-posts, too. So when Mastodon was launched, it immediately became possible to quote-post Mastodon toots. Not on Mastodon itself, but on Friendica and Hubzilla.

Just about everything that isn't Mastodon has already got quote-posts right now


Here are a few (but not even all) Fediverse server applications that already have quote-posts:



And they're all part of the Fediverse which means that they're all connected to Mastodon. People on all of these can theoretically read your Mastodon toots. And people on all of these can theoretically quote-post your Mastodon toots.

Mastodon's quote-post opt-in is not a water-tight defence against being quote-posted


So you can choose not to be quote-posted. But you can only choose not to be quote-posted by Mastodon users. This opt-in does not work with the rest of the Fediverse.

First of all, that's because Mastodon's quote-post feature is not compatible with anything else out there. Mastodon's developers have chosen to re-invent the quote-posting wheel from scratch. They've intentionally chosen to do so in a way that's completely incompatible with everything else out there.

Their intention was to reinforce Mastodon's appearance to its own users as the one and only Fediverse and ActivityPub gold standard and to make Pleroma, Akkoma, Misskey, Firefish, Iceshrimp, Sharkey, CherryPick, Catodon, Mitra, Friendica, Hubzilla, (streams), Forte etc. look broken. It's part of their plan to keep Mastodon users on Mastodon in the wake of Mastodon's market share in the Fediverse shrinking.

Also, they did not publish any specifications on their quote-post implementation, so even those non-Mastodon developers who are fast enough didn't have a chance to implement support for Mastodon's opt-in.

This means that even if you've set your posts to un-quote-post-able on Mastodon, everything I've listed above can still quote-post you with no resistance.

Absolute Fediverse-wide protection against being quote-posted is impossible


And don't get your hopes high that the day will come when nobody on the Fediverse will be able to quote-post you, whether they're on Mastodon or not. Such a setting is technologically impossible.

Who says that? Mike Macgirvin says that. The guy who launched Friendica and brought quote-posts to the Fediverse 15 years ago, remember? This guy has built the Fediverse's most elaborate, most complex, most fine-grained, most advanced permissions system into (streams) and Forte.

These two have reply control, the kind of which you couldn't image in your wildest dreams. I'm serious. They have permissions settings for almost everything on two or three levels, for your whole channel, individually per contact and sometimes even per post or per file or folder in the file storage.

But they don't have quote-post permission settings. Because that's impossible to enforce Fediverse-wide. And even if it was possible, it'd be pointless. If they can't quote-post you, they'll copy-paste you. If they can't copy-paste you either because they're on a phone, they'll post screenshots of your toots.

Mike also says, there is exactly one way to keep people from quote-posting you, and that's by not posting in public. Unfortunately, unlike what he has created, Mastodon has little between "public" and "DM", if anything.

Mastodon cannot quote-post the non-Mastodon Fediverse


This may be the big surprise: It has recently been discovered by chance that Mastodon's quote-post feature only works with Mastodon toots.

On the one hand, Pleroma, Akkoma, Misskey, Sharkey, Friendica, Hubzilla etc. can quote-post just about everything that comes in from Mastodon. But on the other hand, no Mastodon 4.5 user will be able to quote-post anything from either of these. Or from Pixelfed or PeerTube or Loops or Castopod or WriteFreely or whatever.

That's because Mastodon is looking for a quote-post opt-in. But nothing else in the Fediverse supports Mastodon's quote-post opt-in, also seeing as it's still officially in development. And it's highly unlikely that everything in the Fediverse will adopt another piece of non-standard, proprietary Mastodon tech.

"Quote" actually means something else


Lastly, Mastodon has the audacity to call this feature "quote".

A "quote" is something else. Remember forums? Like, bulletin-board forums with subforums and all? Where posts are quoted in follow-ups, entirely or only partially? That's what a quote is. That has got nothing to do with quote-posts.

Why I say that there's a difference? Because I also say that Friendica has had both quotes and quote-posts.

It has had them for 15 years, both quotes (which it calls "quotes", go figure) and quote-posts (which it calls "quoted shares", and which include the original author of the quoted post, complete with their profile picture and a clickable link to them, as well as a clickable link to the original post).

Hubzilla has both. (streams) has both. Forte has both. And I wouldn't be surprised if other Fediverse server software had both, too.

The irony is that Mastodon itself has been able to render actual quotes since version 4.0 from October, 2022. At the same time, it will continue to be unable to render any quote-posts done outside of Mastodon for the foreseeable future.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Firefish #Iceshrimp #Sharkey #CherryPick #Catodon #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares


#mastodon #fediverse #activitypub #hubzilla #friendica #forte #streams
2025-11-20
@Tuxi ⁂ Von den größeren Hubs ist z. B. hub.hubzilla.de ganz interessant. Ich bin mir nur nicht sicher, ob da schon der neue Hotfix installiert ist.

Ansonsten hat auch @Der Pepe (Hubzilla) ⁂ zwei Hubs, Whoville und KlackerHub; ersterer stellt ein paar mehr Apps zur Verfügung, darunter auch diaspora*.

Bezüglich Videos empfehle ich den monatlichen @Hubzilla auf BigBlueButton. Den gab es schon zweimal, jeweils mit Videoaufzeichnungen. Beim zweiten Mal ging es um den Einstieg an sich und die Konfiguration des neuen Kanals.

RE: Hubzilla Workshop wrote the following post Thu, 30 Oct 2025 00:52:16 +0100 Hubzilla Workshop #2
Mi., 29. Oktober 2025

Einstieg in Hubzilla

  • Server-Auswahl
  • Unterschiede Account/Kanal
  • verschiedene Registrierungstypen
  • Account anlegen
  • Kanal anlegen
  • Profil vervollständigen
  • Apps installieren
  • Die fünf wichtigen Apps
  • Verbindungen eingehen
  • Anzeige-Einstellungen - Themes
  • Einstellungen
  • Wir erstellen eine "Features-App"
  • Privacy Gruppen und Kontaktrollen


Video zum Workshop

Ausflug in die Privacy Gruppen und die Kontakt-Rollen mit Jupiter

Aufzeichnung https://hub.hubzilla.hu/item/64646444-a9a7-43c0-89c7-830eb9171931

#hubzilla #workshop

Das erste Mal war eher ein Testballon, da ging es um bestimmte Einstellungen und um Filter.

RE: Hubzilla Workshop wrote the following post Fri, 19 Sep 2025 19:12:22 +0200 Hubzilla Workshop #01
Mi., 17. September 2025
  • Anhand praktischer Beispiele verschiedene Einstellungen & deren Auswirkungen
  • Filter - Welche gibt es? Wozu dienen sie? Wie kann ich sie nutzen?
  • Tipps für Account-Nutzer wie auch für Instanzbetreiber


Dokumente

Aufzeichnung

Ausblick https://hub.hubzilla.hu/item/508391b0-bf9a-4378-baab-678a11be8cec

Der erste Hubzilla-Workshop ist recht ordentlich gelaufen.

Und hier findet Ihr eine Übersicht, sowie Links zur Aufzeichnung, zu den Dateien (Präsentation und Tabelle mit Item-Feldern, die für die Filterung sinnvoll sind), sowie den "Ausblick", wo wir Themen für die kommenden Workshops sammeln und gerne auch Feedback entgegennehmen.

#hubzilla #workshop #fediverse

Mittwoch nächste Woche, also am 26. November, findet der dritte Hubzilla-Workshop statt, in dem es ums Posten geht.

RE: https://top-netz.de/@Doris/115581383017134078

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuoteTweet #QuoteToot #QuoteTröt #QuoteBoost #Hubzilla #HubzillaWorkshop
2025-11-18
I'm usually friendly. But challenge me, and I'll fight. If you fight dirty, then so will I.

And this time I'll fight for accessibility. Against someone who is actively fighting against accessibility and intentionally acting in most ableist ways.

In the below post, @Mat B explains that he adds content into his alt-texts that isn't available anywhere else in the post.

RE: https://beige.party/@TwoClownsEating/115571481219795582

You may or may not know, but this is actually ableist behaviour because it discriminates against those who cannot access alt-text, for example, people who don't have at least one working hand.

I have explained it in the wiki about alt-texts and image descriptions that I'm working on. For Mastodon users' convenience, here are the links as URLs in plain sight:

https://hub.netzgemeinde.eu/wiki/jupiter_rowland/How(20)to(20)describe(20)images(20)in(20)the(20)Fediverse/Don(27)t(20)explain(20)things(20)or(20)give(20)other(20)information(20)only(20)in(20)alt-text(21)

https://hub.netzgemeinde.eu/wiki/jupiter_rowland/How(20)to(20)describe(20)images(20)in(20)the(20)Fediverse/Don(27)t(20)use(20)alt-text(20)to(20)write(20)around(20)your(20)character(20)limit(21)

https://hub.netzgemeinde.eu/wiki/jupiter_rowland/How(20)to(20)describe(20)images(20)in(20)the(20)Fediverse/Can(20)everyone(20)access(20)alt-text(3f)

See also this post, https://www.kwbell.eu/mastonotes/alt-text-for-mastodon-images/, by @KB.

So I did what I feel is my duty. I told him how and why this is wrong. Thousands upon thousands of Mastodon users see it as absolutely justified to tell everyone to write alt-text, so why shouldn't I tell people how to write proper alt-text as opposed to misusing it?

RE: https://hub.netzgemeinde.eu/item/11550d0a-a8d1-42b6-9924-973ef9cc7652

@Mat B, however, did not accept that he has been wrong all the time. Instead, he chose to attack me to defend his utterly ableist ways.

RE: https://beige.party/@TwoClownsEating/115572513612903964

Obviously, he doesn't know whom he is picking on. I have been in the Fediverse under various guises for about five years longer than Mastodon has even been around. I have spent much more time on Fediverse server software that is vastly more powerful than Mastodon than he has spent on Mastodon.

Congrats, @Mat B, YOU ABSOLUTELY MOTHERFUCKING HORRID STEAMING FERMENTING PILE OF MISANTHROPIC AND ABLEIST SHIT. you left me no other option than to take the Teller-Ulam thermonuclear option.



@Velocirooster adminensis :bc:: @Mat B is an absolute disgrace to beige.party, a Mastodon server that I got to know as a lighthouse of inclusivity and accessibility. He is deliberately and intentionally breaking sever rule number 2, defending his misbehaviour and attacking those who try to educate him about how to actually be inclusive and accessible. In the name of beige.party and the entire Fediverse, I hereby demand he be permanently banned from beige.party, effective immediately.

In addition, I recommend everyone who treasures and fights for actual accessibility and full inclusivity to block @Mat B.

#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #QuotePost #QuoteTweet #QuoteToot #QuoteBoost #Ableist #Ableism #AbleismMeta #CWAbleismMeta
2025-11-18
I'm usually friendly. But challenge me, and I'll fight. If you fight dirty, then so will I.

And this time I'll fight for accessibility. Against someone who is actively fighting against accessibility and intentionally acting in most ableist ways.

In the below post, @Mat B explains that he adds content into his alt-texts that isn't available anywhere else in the post.

RE: https://beige.party/@TwoClownsEating/115571481219795582

You may or may not know, but this is actually ableist behaviour because it discriminates against those who cannot access alt-text, for example, people who don't have at least one working hand.

I have explained it in the wiki about alt-texts and image descriptions that I'm working on. For Mastodon users' convenience, here are the links as URLs in plain sight:

https://hub.hubzilla.de/wiki/jupiter_rowland/How(20)to(20)describe(20)images(20)in(20)the(20)Fediverse/Don(27)t(20)explain(20)things(20)or(20)give(20)other(20)information(20)only(20)in(20)alt-text(21)

https://hub.hubzilla.de/wiki/jupiter_rowland/How(20)to(20)describe(20)images(20)in(20)the(20)Fediverse/Don(27)t(20)use(20)alt-text(20)to(20)write(20)around(20)your(20)character(20)limit(21)

https://hub.hubzilla.de/wiki/jupiter_rowland/How(20)to(20)describe(20)images(20)in(20)the(20)Fediverse/Can(20)everyone(20)access(20)alt-text(3f)

See also this post, https://www.kwbell.eu/mastonotes/alt-text-for-mastodon-images/, by @KB.

So I did what I feel is my duty. I told him how and why this is wrong. Thousands upon thousands of Mastodon users see it as absolutely justified to tell everyone to write alt-text, so why shouldn't I tell people how to write proper alt-text as opposed to misusing it?

RE: https://hub.hubzilla.de/item/11550d0a-a8d1-42b6-9924-973ef9cc7652

@Mat B, however, did not accept that he has been wrong all the time. Instead, he chose to attack me to defend his utterly ableist ways.

RE: https://beige.party/@TwoClownsEating/115572513612903964

Obviously, he doesn't know whom he is picking on. I have been in the Fediverse under various guises for about five years longer than Mastodon has even been around. I have spent much more time on Fediverse server software that is vastly more powerful than Mastodon than he has spent on Mastodon.

Congrats, @Mat B, YOU ABSOLUTELY MOTHERFUCKING HORRID STEAMING FERMENTING PILE OF MISANTHROPIC AND ABLEIST SHIT. you left me no other option than to take the Teller-Ulam thermonuclear option.



@Velocirooster adminensis :bc:: @Mat B is an absolute disgrace to beige.party, a Mastodon server that I got to know as a lighthouse of inclusivity and accessibility. He is deliberately and intentionally breaking sever rule number 2, defending his misbehaviour and attacking those who try to educate him about how to actually be inclusive and accessible. In the name of beige.party and the entire Fediverse, I hereby demand he be permanently banned from beige.party, effective immediately.

In addition, I recommend everyone who treasures and fights for actual accessibility and full inclusivity to block @Mat B.

#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #QuotePost #QuoteTweet #QuoteToot #QuoteBoost #Ableist #Ableism #AbleismMeta #CWAbleismMeta
myrmepropagandistfuturebird@sauropods.win
2025-11-08

Doing a quote on here feels surreal. Sadly I can't quote most posts ... I wonder if my old posts are locked like that... is there a way to unlock them?

#quoteboost #quotepost

2025-11-06

Being able to retroactively change who can quote post you is great, but I wish I could change the visibility of already published posts as well...

#QuotePost #QuoteToots #QuotePosts #QuoteBoost #QuoteBoosts

2025-10-25
@0%/100% TAX ✅ ✅
(but not quote it since quoting is a Mastodon "neologism"?)

What Mastodon refers to as "quoting", and what 𝕏 calls "quote-tweets", has been available on Friendica (which @Grow Fediverse is on, by the way) since its inception a bit over 15 years ago, only that Friendica calls it "quoted sharing".

What Friendica calls "quoting" is what I've done up there at the top of this comment (I'm on Hubzilla, created by Friendica's creator in 2015 from a fork of a fork of Friendica).

Both features have been available in the Fediverse since five and a half years before Mastodon was launched.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Hubzilla #Quote #Quotes #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares
2025-10-22
How much of a nuisance have Mastodon users working around Mastodon's hard-coded 500-character limit become, at least from a non-Mastodon point of view?

Enough of a nuisance for the main developer of Hubzilla to speak up against it.

Mario Vavti wrote the following post Wed, 22 Oct 2025 11:47:16 +0200 Dear people of the Fediverse,
Please STOP tearing your carefully crafted essays to pieces. This is no longer necessary. If your preferred instance does not allow this, consider asking your instance admin to increase the limit or switch to a different instance. Besides, it is so last decade :face_with_rolling_eyes:

See? If Mastodon users can complain about "long posts" from outside Mastodon, namely anything that exceeds 500 characters, then those of us who did not come into the Fediverse via Mastodon can complain about Mastodon users chopping long posts up into lots of little pieces.

Little nitpick: It has never been necessary. Friendica and Hubzilla have had a nearly unlimited character count since before Mastodon came with 500 characters.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuoteToot #QuoteBoost #Fediverse #Mastodon #LongPostMeta #CWLongPostMeta #CharacterLimit #CharacterLimits
2025-10-22
How much of a nuisance have Mastodon users working around Mastodon's hard-coded 500-character limit become, at least from a non-Mastodon point of view?

Enough of a nuisance for the main developer of Hubzilla to speak up against it.

Mario Vavti schrieb den folgenden Beitrag Wed, 22 Oct 2025 11:47:16 +0200 Dear people of the Fediverse,
Please STOP tearing your carefully crafted essays to pieces. This is no longer necessary. If your preferred instance does not allow this, consider asking your instance admin to increase the limit or switch to a different instance. Besides, it is so last decade :face_with_rolling_eyes:

See? If Mastodon users can complain about "long posts" from outside Mastodon, namely anything that exceeds 500 characters, then those of us who did not come into the Fediverse via Mastodon can complain about Mastodon users chopping long posts up into lots of little pieces.

Little nitpick: It has never been necessary. Friendica and Hubzilla have had a nearly unlimited character count since before Mastodon came with 500 characters.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuoteToot #QuoteBoost #Fediverse #Mastodon #LongPostMeta #CWLongPostMeta #CharacterLimit #CharacterLimits
2025-10-19
@Maxi 11x 💉
Das Fediverse wird immer mehr zu Facebook und ich hab da wenig Lust drauf.

Das Fediverse war Facebook, bevor es von Millionen von ahnungslosen Mastodon-Newbies zu Twitter gemacht wurde.

Mehr als die Hälfte der Mastodon-Nutzer glaubt, das Fediverse sei nur Mastodon. Der weit überwiegende Teil derer, die eines Besseren belehrt wurden, glauben immer noch, das Fediverse sei
  • (frühestens) 2016
  • von Eugen Rochko
  • als reine Microblogging-Plattform und Twitter-Klon
  • mit einem Zeichenlimit von 500 Zeichen
erfunden worden. Und alles, was davon abweicht und nicht "offensichtlich (wie PeerTube & Co.) als Extra an Mastodon drangeklebt" worden ist, wird aufgefaßt als lästige Eindringlinge im Mastodon-Fediverse, die sich nicht an die Regeln des Mastodon-Fediverse halten und sich auch nicht an die Kultur des Mastodon-Fediverse anpassen.

Um das mal zurechtzurücken:

Im Januar 2016 ging Mastodon an den Start.

Im Juli 2010, fünfeinhalb Jahre vor Mastodon, startete Friendica (https://de.wikipedia.org/wiki/Friendica, https://friendi.ca) als Facebook-Alternative.
  • Ohne Zeichenbegrenzung (tatsächlich 16.777.215 Zeichen).
  • Mit allem, was eine gute Bloggingplattform an Textformatierung hergibt.
  • Mit Inhaltswarnungen, die jeder für sich selbst automatisch generieren lassen kann mittels einer Liste von Schlüsselwörtern.
  • Mit Titeln und Zusammenfassungen, und die Zusammenfassungen waren schon immer in dem Datenfeld, das Mastodon seit 2017 für CWs verwendet.
  • Mit der Fähigkeit, andere Posts als Komplettzitate zu teilen. Und nicht ein einziges Mal ist das mißbräuchlich verwendet worden.

Jetzt regen sich Mastodon-Nutzer darüber auf, daß Friendica auf so infame und rücksichtslose Art und Weise ins Mastodon-Fediverse eingedrungen ist und seine Nutzer
  • sich nicht ans 500-Zeichen-Limit halten
  • alle mit ihren Textformatierungen nerven
  • keine CWs schreiben
  • dafür das CW-Feld mißbrauchen mit "Titeln oder was weiß ich, was das ist"
Daß Friendica schon seit über 15 Jahren quote-posten kann, weiß zum Glück beinahe niemand auf Mastodon.

Fakt ist aber: Friendica gab es nicht nur schon fünfeinhalb Jahre, als Mastodon startete, sondern es war auch schon fünfeinhalb Jahre im Fediverse, als Mastodon startete. Und es hatte auch schon gut fünf Jahre lang seine eigene Kultur, als Mastodon startete.

In dem Augenblick, wo Mastodon startete, verband es sich sofort mit StatusNet (von 2008, wofür Mastodon ursprünglich nur eine Alternativoberfläche war; heute GNU social, https://de.wikipedia.org/wiki/GNU_Social, https://gnusocial.rocks/), Friendica und Hubzilla (von 2015, basiert auf einem Fork eines Forks von Friendica von 2012; https://de.wikipedia.org/wiki/Hubzilla, https://hubzilla.org). Und nicht umgekehrt.

Wir waren zuerst hier. Findet euch damit ab.

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NichtNurMastodon #MastodonZentrizität #MastodonNormativität #StatusNet #GNUsocial #Friendica #Hubzilla #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Zeichenlimit #Zeichenlimits #ZeichenlimitMeta #CWZeichenlimitMeta #500Zeichen #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteTröt #QuoteTröts #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebatte #QuoteTrötDebatte
2025-10-14
@~n Ich dachte, Mastodon führt die für Drukos nötige Technologie erst jetzt gerade ein? Die es übrigens woanders im Fediverse schon bis zu gut 15 Jahren gibt?

(Druko = Quote-Post, wo das Original oben und der Kommentar drunter steht)

#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteTröt #QuoteTröts #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebatte #QuoteTrötDebatte
2025-10-07
@Stefan Bohacek Another thing where Hubzilla, (streams) and Forte truly shine, by the way.

First of all, Hubzilla distinguishes between a "contact" (someone has sent you a connection request) and an "approved contact" (either you've confirmed the connection request, thus creating what's a mutual follower/followed connection on Mastodon, or you've requested a connection request, and it has been confirmed). It's much like on Facebook. This distinction also exists in permissions: You can give certain permissions to contacts or only to approved contacts.

On (streams) and Forte, the concept of a non-approved contact doesn't exist; unless the connection request is confirmed, it doesn't count as a contact, and it doesn't have the privileges of a contact. This means that nobody can acquire certain permissions simply by following you.

Next, even if someone is a contact of yours, doesn't mean that they're always permitted to send you their posts. You can configure your channel in such a way that you can only allow certain contacts of yours to send you posts. I've actually done that.

Also, on all three, being notified when someone who isn't a contact mentions you is off by default and has to be activated manually. Even then, it only works if their post that mentions you makes it onto the server that you're on. This isn't even a case of "they mention you, your channel receives the message, but you aren't notified". This is a case of "they mention you, but your channel outright rejects the message, and if no other channel on your server accepts it, the whole server rejects it".

This means the whole attack vector does not work, especially not against neatly configured channels. By default, you won't see any non-contact mention you out of the blue. And even if someone requests a connection, and you approve it and thereby establish a full, mutual connection, that doesn't mean that you have to endure what they post.

Oh, by the way: Hubzilla, (streams) and Forte understand Mastodon's "followers only" as "public" because it doesn't come with limited permissions, because Mastodon doesn't have a permissions system. And al three have had quote-posts since their inception. This gives you the power to fight back by quote-posting the offending post in a DM to the admin of the offender's home instance. And on Hubzilla, (streams) and Forte, the quote in a quote-post is not a reference by link; it's a dumb copy of the original, inserted into the quoting post with a link to the original post and to the original poster, that cannot be altered by the original poster after the fact in any way.

Lastly, you can raise the shields even further, namely against harassment by DM. You don't have to accept DMs from non-contacts. You don't even have to accept DMs from all your contacts. You can literally cherry-pick those contacts from whom you want to receive DMs.

CC: @Mastodon Migration

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Harassment #Permissions #FediverseSafety #FediverseSecurity
2025-09-28

@tsvenson@fosstodon.org Just to avoid confusion or surprise, pls note that your

At least in Mastodon v4.4.5, as on #Fosstodon, you can already now set how others will be able to #quote you
really should be amended as
At least in Mastodon v4.4.5, as on #Fosstodon, you can already now set how others who also use Mastodon will be able to #quote you.
There are numerous other software platforms in the Fediverse, many much older than Masto, & many of which can already #quoteboost anyone's post, regardless of their Masto setting.

FYI.

2025-09-23
@silverpill @Julian Fietkau In the background, yes.

At first, I expected this implementation to be exactly like Misskey and require this line in plain sight in the content so that the quoted post is rendered dynamically. Which has never been the case in Mike's software family.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #FEP_e232
2025-09-23
@silverpill @Julian Fietkau In the background, yes.

At first, I expected this implementation to be exactly like Misskey and require this line in plain sight in the content so that the quoted post is rendered dynamically. Which has never been the case in Mike's software family.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #FEP_e232
2025-09-22
@Julian Fietkau
I don't know if translating the absence of a FEP-044f quote policy as “not quotable” was the right decision. Maybe it wasn't.

If you use server software that has quote-posts implemented with no quote policy, I think it's rather safe to assume that you're okay with being quote-posted.

I mean, if you're on Misskey, complaining about being quote-posted is like complaining about emoji reactions, MFM shenanigans or the overall genki feeling. Misskey is not Mastodon with 3,000 characters; deal with it. And I haven't even mentioned "Speak as Cat" yet that's popular around the Forkeys.

You might have seen my comment in the forum thread on a way to make it easier for platforms like Friendica to signal a free-for-all quoting permission.

I was just about to say that this goes doubly for those server applications where quote-posts are an integral part of the communication culture.

Seriously, if you're on one of these, but you don't want anyone to quote-post you, and you still insist in always posting in public, you're doing something wrong. And just as seriously, unlike Mastodon, especially the Friendica/Hubzilla/(streams)/Forte family won't mollycoddle you. If you come to stay, we expect you to know what you're doing and why.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Misskey #Forkey #Forkeys #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #FEP_044f
2025-09-22
@Julian Fietkau
I don't know if translating the absence of a FEP-044f quote policy as “not quotable” was the right decision. Maybe it wasn't.

If you use server software that has quote-posts implemented with no quote policy, I think it's rather safe to assume that you're okay with being quote-posted.

I mean, if you're on Misskey, complaining about being quote-posted is like complaining about emoji reactions, MFM shenanigans or the overall genki feeling. Misskey is not Mastodon with 3,000 characters; deal with it. And I haven't even mentioned "Speak as Cat" yet that's popular around the Forkeys.

You might have seen my comment in the forum thread on a way to make it easier for platforms like Friendica to signal a free-for-all quoting permission.

I was just about to say that this goes doubly for those server applications where quote-posts are an integral part of the communication culture.

Seriously, if you're on one of these, but you don't want anyone to quote-post you, and you still insist in always posting in public, you're doing something wrong. And just as seriously, unlike Mastodon, especially the Friendica/Hubzilla/(streams)/Forte family won't mollycoddle you. If you come to stay, we expect you to know what you're doing and why.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Misskey #Forkey #Forkeys #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #FEP_044f
2025-09-22
@Julian Fietkau I'm surprised to read that (streams) allegedly has FEP-e232 implemented. As I happen to have two (streams) channels myself, and as (streams) allows me to have a look at the whole source code of any activity (whereas Hubzilla only shows me that of the content), I've checked a fairly recent post of mine that includes a link. And while it does define the hashtags just like Mastodon and Hubzilla, it does not define links in a way that conforms to FEP-e232. Either that, or (streams)' implementation of FEP-e232 is newer than the software was when I sent that post.



Next, I wanted to see if (streams) had its way of quote-posting changed in the last seven years or so of development and forking. I expected it to quote-post like Hubzilla, namely by turning a BBcode short code into a dumb copy of the original upon sending, but I wanted to see proof. As (streams) is a fork of a fork of three forks of a fork (of a fork) of Hubzilla that's still maintained by Hubzilla's own creator, I would have been surprised if he had changed the way (streams) quote-posts at some point on the way.

So I quote-posted my own post on (streams) just to see what happens. And (streams) acted exactly like Hubzilla and not at all like described in FEP-044f on the surface. It still inserts a dumb copy.

Good thing I have access to the full source code of any message on (streams). So here's what happened, namely what I expected to happen: (streams) quote-posts like Hubzilla.

First of all, when I clicked the "Share" button, this short code was inserted into the post editor:

[share⁠=1198713][/share]

The number, by the way, is the running number of the message to quote-post on the server.

Upon sending the post, (streams) automatically "expanded" the short code into the dumb copy I had expected.

[⁠share author='Jupiter+Rowland' profile='https://hub.netzgemeinde.eu/channel/jupiter_rowland' portable_id='_moYLN61-o3FbP3jyThygMDf-bjF2cApXgkrwlAE77iKy19xM1_6F06V4b71eTkqqNaTUjGiN0lfw2dyn5nXRw' avatar='https://streams.elsmussols.net/xp/6b50efa4bb804860f6128bba791b74fab4a0a5e09dbcbee8d8ca77cee00f0330-6' link='https://hub.netzgemeinde.eu/item/0a1cdda5-eb1c-4a33-9574-ddd896977b4f' auth='true' posted='2025-09-21 19:42:56' message_id='https://hub.netzgemeinde.eu/item/0a1cdda5-eb1c-4a33-9574-ddd896977b4f'] ...(the source code of the original message goes here)... [/share]

Both Hubzilla and (streams) render this the same way, namely with a header line above the copy that includes the profile picture of the original author, the name of the original author with a Zot/Nomad-type link to their channel/account and a Zot/Nomad-type link to the original of the post ("Zot/Nomad-type" means that [zrl][/zrl] is used rather than [url][/url] which means that the ID of an observer on Hubzilla/(streams)/Forte is attached to the link for OpenWebAuth identity recognition purposes.)

At the same time, curiously, (streams) includes the line "rel": "https://misskey-hub.net/ns#_misskey_quote" and a line that starts with "name": "RE: and continues with the URL of the original message into the code for the link to the original message. The latter is identical to what Misskey and all Forkeys have in quote-posting notes in plain sight, only that (streams) only reveals it in the source code rather than in the content as well.

So this part of FEP-044f is implemented, albeit concealed from most people and only happening in the code.



Now, looking at the quote policy part, that looks like it could be possible to add to the Fediverse's permission champions Hubzilla, (streams) and Forte. After all, they already have comment controls with no FEP backing it (and if GoToSocial's quote policy can be made into an FEP, maybe so can (streams)' and Forte's comment controls so that they actually do blank out reply buttons on the farther ends of the Fediverse if the software on the farther ends implement support for that FEP).

This could be done at three levels again. I'll illustrate this with (streams) and Forte because they're quite a bit less complex than older Hubzilla.

At channel level, quote-posting (and maybe quoting as well) could be set as usually, namely to semi-public (= everyone in the Fediverse = no quote policy), restricted (= only your contacts) and only yourself. (Seriously, you don't want random passersby with no accounts to quote-post you. Even though you can allow them to comment on your posts if you dare.)

"Only yourself" could be overridden at contact level by permitting certain contacts to quote-post (and maybe quote) your messages. This is actually standard behaviour on (streams) and Forte.

And then there is the per-post level which would be similar to (streams)' and Forte's comment controls. These allow you to limit who may comment on a post to only your contacts and those who have already participated in the same conversation, and they allow you to turn off comments altogether.

Quote authorisation would not be much different in handling from manually moderating comments from those who technically aren't permitted to comment (only that spammers don't quote-post, at least not yet, and they probably never will because that simply makes no sense). So that'd be nothing really new.

Of course, this would have some limitations which come from how Hubzilla, (streams) and Forte work and from their conversation architecture.

The first limitation is that you could only give certain contacts permission to quote-post your posts if you didn't give it to the whole Fediverse. Channel-wide permissions are always inherited by contact-specific permissions, and this cannot be overridden. So you couldn't generally allow everyone to quote-post your posts except for one certain contact of yours.

The second limitation is that you can only control the permissions of contacts, but not of non-contacts. So you can't disallow some stranger whom you aren't connected to to quote-post your posts while everyone else is allowed.

Then again, FEP-044f doesn't make either of these two possible either. It can only define who is permitted to quote-post a post, not who isn't.

The third limitation is that, on Hubzilla, (streams) and Forte, comments always have the same permissions as the post that they belong to because comments always have the same owner as the post that they belong to. Basically, if FEP-044f was to be defined for each comment individually, it would have a chance of clashing with conversation containers as per FEP-171b.

Here on Hubzilla, as well as from (streams)' point of view, everyone's comments in this thread are owned by me because I've started the thread. And the permissions on all these comments are defined by my post. I've seen my share of permission clashes whenever someone on Mastodon replied to a public post or a public comment with a DM, and Hubzilla overrode this by forcing the permissions of the post on that reply.

In practice, this means that the quote policies of all comments would be the same as that of the post. At least that's how Hubzilla, (streams) and Forte would understand them because the concept of comments having different permissions than the post is alien to them. So if you say that I'm not permitted to quote-post your comment, but I say that anyone can quote-post my post, Hubzilla and (streams) override the quote policy that you've given your comment on Mastodon with the quote policy that I've given my post on Hubzilla, and I can quote-post you.

So the actually difficult part would be to implement an exception in how Hubzilla, (streams) and Forte handle comment permissions for quote policies and make them individual for each comment rather than making comments inherit them from the post.

Well, and lastly, if you permitted all your contacts to quote-post a post of yours, and you had a few more contacts, the "canQuote" section would end up monstrous. (A bit less so if you could cherry-pick those who are allowed to quote-post you on a per-post base, just like you can cherry-pick those who are allowed to see the post in the first place.) Also, I'm wondering just how well policies as per FEP-044f (and their implementations in various server applications) will work with DIDs as per FEP-ef61 which (streams) and Forte use, and I guess, so does Mitra now.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Misskey #Forkey #Forkeys #GoToSocial #Hubzilla #Streams #(streams) #Forte #Mitra #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Permission #Permissions #FEP_044f #FEP_171b #FEP_e232 #FEP_ef61
2025-09-22
@Julian Fietkau I'm surprised to read that (streams) allegedly has FEP-e232 implemented. As I happen to have two (streams) channels myself, and as (streams) allows me to have a look at the whole source code of any activity (whereas Hubzilla only shows me that of the content), I've checked a fairly recent post of mine that includes a link. And while it does define the hashtags just like Mastodon and Hubzilla, it does not define links in a way that conforms to FEP-e232. Either that, or (streams)' implementation of FEP-e232 is newer than the software was when I sent that post.



Next, I wanted to see if (streams) had its way of quote-posting changed in the last seven years or so of development and forking. I expected it to quote-post like Hubzilla, namely by turning a BBcode short code into a dumb copy of the original upon sending, but I wanted to see proof. As (streams) is a fork of a fork of three forks of a fork (of a fork) of Hubzilla that's still maintained by Hubzilla's own creator, I would have been surprised if he had changed the way (streams) quote-posts at some point on the way.

So I quote-posted my own post on (streams) just to see what happens. And (streams) acted exactly like Hubzilla and not at all like described in FEP-044f on the surface. It still inserts a dumb copy.

Good thing I have access to the full source code of any message on (streams). So here's what happened, namely what I expected to happen: (streams) quote-posts like Hubzilla.

First of all, when I clicked the "Share" button, this short code was inserted into the post editor:

[share⁠=1198713][/share]

The number, by the way, is the running number of the message to quote-post on the server.

Upon sending the post, (streams) automatically "expanded" the short code into the dumb copy I had expected.

[⁠share author='Jupiter+Rowland' profile='https://hub.netzgemeinde.eu/channel/jupiter_rowland' portable_id='_moYLN61-o3FbP3jyThygMDf-bjF2cApXgkrwlAE77iKy19xM1_6F06V4b71eTkqqNaTUjGiN0lfw2dyn5nXRw' avatar='https://streams.elsmussols.net/xp/6b50efa4bb804860f6128bba791b74fab4a0a5e09dbcbee8d8ca77cee00f0330-6' link='https://hub.netzgemeinde.eu/item/0a1cdda5-eb1c-4a33-9574-ddd896977b4f' auth='true' posted='2025-09-21 19:42:56' message_id='https://hub.netzgemeinde.eu/item/0a1cdda5-eb1c-4a33-9574-ddd896977b4f'] ...(the source code of the original message goes here)... [/share]

Both Hubzilla and (streams) render this the same way, namely with a header line above the copy that includes the profile picture of the original author, the name of the original author with a Zot/Nomad-type link to their channel/account and a Zot/Nomad-type link to the original of the post ("Zot/Nomad-type" means that [zrl][/zrl] is used rather than [url][/url] which means that the ID of an observer on Hubzilla/(streams)/Forte is attached to the link for OpenWebAuth identity recognition purposes.)

At the same time, curiously, (streams) includes the line "rel": "https://misskey-hub.net/ns#_misskey_quote" and a line that starts with "name": "RE: and continues with the URL of the original message into the code for the link to the original message. The latter is identical to what Misskey and all Forkeys have in quote-posting notes in plain sight, only that (streams) only reveals it in the source code rather than in the content as well.

So this part of FEP-044f is implemented, albeit concealed from most people and only happening in the code.



Now, looking at the quote policy part, that looks like it could be possible to add to the Fediverse's permission champions Hubzilla, (streams) and Forte. After all, they already have comment controls with no FEP backing it (and if GoToSocial's quote policy can be made into an FEP, maybe so can (streams)' and Forte's comment controls so that they actually do blank out reply buttons on the farther ends of the Fediverse if the software on the farther ends implement support for that FEP).

This could be done at three levels again. I'll illustrate this with (streams) and Forte because they're quite a bit less complex than older Hubzilla.

At channel level, quote-posting (and maybe quoting as well) could be set as usually, namely to semi-public (= everyone in the Fediverse = no quote policy), restricted (= only your contacts) and only yourself. (Seriously, you don't want random passersby with no accounts to quote-post you. Even though you can allow them to comment on your posts if you dare.)

"Only yourself" could be overridden at contact level by permitting certain contacts to quote-post (and maybe quote) your messages. This is actually standard behaviour on (streams) and Forte.

And then there is the per-post level which would be similar to (streams)' and Forte's comment controls. These allow you to limit who may comment on a post to only your contacts and those who have already participated in the same conversation, and they allow you to turn off comments altogether.

Quote authorisation would not be much different in handling from manually moderating comments from those who technically aren't permitted to comment (only that spammers don't quote-post, at least not yet, and they probably never will because that simply makes no sense). So that'd be nothing really new.

Of course, this would have some limitations which come from how Hubzilla, (streams) and Forte work and from their conversation architecture.

The first limitation is that you could only give certain contacts permission to quote-post your posts if you didn't give it to the whole Fediverse. Channel-wide permissions are always inherited by contact-specific permissions, and this cannot be overridden. So you couldn't generally allow everyone to quote-post your posts except for one certain contact of yours.

The second limitation is that you can only control the permissions of contacts, but not of non-contacts. So you can't disallow some stranger whom you aren't connected to to quote-post your posts while everyone else is allowed.

Then again, FEP-044f doesn't make either of these two possible either. It can only define who is permitted to quote-post a post, not who isn't.

The third limitation is that, on Hubzilla, (streams) and Forte, comments always have the same permissions as the post that they belong to because comments always have the same owner as the post that they belong to. Basically, if FEP-044f was to be defined for each comment individually, it would have a chance of clashing with conversation containers as per FEP-171b.

Here on Hubzilla, as well as from (streams)' point of view, everyone's comments in this thread are owned by me because I've started the thread. And the permissions on all these comments are defined by my post. I've seen my share of permission clashes whenever someone on Mastodon replied to a public post or a public comment with a DM, and Hubzilla overrode this by forcing the permissions of the post on that reply.

In practice, this means that the quote policies of all comments would be the same as that of the post. At least that's how Hubzilla, (streams) and Forte would understand them because the concept of comments having different permissions than the post is alien to them. So if you say that I'm not permitted to quote-post your comment, but I say that anyone can quote-post my post, Hubzilla and (streams) override the quote policy that you've given your comment on Mastodon with the quote policy that I've given my post on Hubzilla, and I can quote-post you.

So the actually difficult part would be to implement an exception in how Hubzilla, (streams) and Forte handle comment permissions for quote policies and make them individual for each comment rather than making comments inherit them from the post.

Well, and lastly, if you permitted all your contacts to quote-post a post of yours, and you had a few more contacts, the "canQuote" section would end up monstrous. (A bit less so if you could cherry-pick those who are allowed to quote-post you on a per-post base, just like you can cherry-pick those who are allowed to see the post in the first place.) Also, I'm wondering just how well policies as per FEP-044f (and their implementations in various server applications) will work with DIDs as per FEP-ef61 which (streams) and Forte use, and I guess, so does Mitra now.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Misskey #Forkey #Forkeys #GoToSocial #Hubzilla #Streams #(streams) #Forte #Mitra #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Permission #Permissions #FEP_044f #FEP_171b #FEP_e232 #FEP_ef61

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst