@BotKit by Fedify :botkit: Be aware that quotes and quote-posts are two different things, and both exist in the Fediverse. At least Friendica, Hubzilla, (streams) and Forte can generate both.

This is a quote, like in every bulletin-board forum out there:

Coming soon in #BotKit 0.2.0: Native #quote post support!

Or this, but it has to be coded manually into the comment's source code:

BotKit by Fedify :botkit: wrote:

Coming soon in #BotKit 0.2.0: Native #quote post support!

This is a quote-post a.k.a. shared post a.k.a. quoted share:

BotKit by Fedify :botkit: wrote the following post Mon, 21 Apr 2025 05:51:28 +0200 Coming soon in #BotKit 0.2.0: Native #quote post support!

We're excited to share a preview of the upcoming quoting features in BotKit 0.2.0. This update will make it easier for your bots to engage with quoted content across the fediverse.

The quoting feature set includes:

• Detecting when someone quotes your bot's posts with the new Bot.onQuote event handler
• Accessing quoted content through the Message.quoteTarget property
• Creating quote posts using the quoteTarget option in Session.publish() and Message.reply() methods

Here's a quick example of how you can use the quote detection:
bot.onQuote = async (session, quote) => {
  // The quote parameter is a Message object representing the post that quoted your bot
  await quote.reply(text`Thanks for quoting my post, ${quote.actor}!`);
  
  // You can access the original quoted message
  const originalPost = quote.quoteTarget;
  console.log(`Original message: ${originalPost?.text}`);
};
And creating quote posts is just as simple:
// Quote in a new post
await session.publish(
  text`I'm quoting this interesting message!`,
  { quoteTarget: someMessage }
);

// Or quote in a reply
await message.reply(
  text`Interesting point! I'm quoting another relevant post here.`,
  { quoteTarget: anotherMessage }
);
Remember that quoting behavior may vary across different #ActivityPub implementations—some platforms like Misskey display quotes prominently, while others like Mastodon might implement them differently.

Want to try these features right now? You can install the development version from JSR:
deno add jsr:@fedify/botkit@0.2.0-dev.90+d6ab4bdc
We're looking forward to seeing how you use these quoting capabilities in your bots!

#fedidev

Also, Friendica, Hubzilla, (streams) and Forte handle quote-posts a lot differently from Misskey and the Forkeys.

Misskey and the Forkeys do quote-posts like so:

RE: https://hollo.social/@botkit/01965678-eb56-7003-9c91-07e4418bf63a

At least on Hubzilla, (streams) and Forte, a quote-post starts out like this:

[share⁠=74153074][/share]

Upon sending the post, this piece of BBcode is changed into a full, dumb copy of the original post, led in by a line that says who posted this first, complete with a link to the profile, and that also links to the original. The original poster is being notified about this (unless they chose not to), but if the original post is edited, the edit is not forwarded to quote-posted copies.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Misskey #Forkey #Forkeys #Friendica #Hubzilla #Streams #(streams) #Forte #Quotes #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts

@Mitex Leo Short answer: no.

To my best knowledge, Hubzilla cannot import anything from Mastodon. No posts, no followed, especially no followers.

(streams) can import CSV-formatted follow lists; I don't know if Mastodon can export them, or if Mastodon has its own proprietary follow list format. But (streams) cannot make your followers on Mastodon your followers on (streams) because it cannot make people follow you. Also, (streams) cannot import posts from Mastodon.

Mass-importing 5,000+ connections from Mastodon to Hubzilla or (streams) would be a stupid idea anyway. You'd have to go through all of them and configure them. Yes, whereas Mastodon only has "I follow you" and "I don't follow you", Hubzilla and (streams) have extensive configuration options for connection. And you will need them.

You'd have to edit 5,000+ connections, one by one, and

• assign them the appropriate contact role (Hubzilla)/permission role ((streams)) so that they have the right permissions (on Hubzilla and (streams), everything is permissions, and permissions are everything)
• add them to one or multiple privacy groups (Hubzilla)/access lists ((streams)) (think Mastodon lists, but on lots of coke and 'roids; optional on Hubzilla, but highly recommended)
• maybe also adjust the (optional) affinity (Hubzilla)/friend zoom ((streams)) slider
• maybe even add lines to the (optional, but recommended) per-contact filter lists (you'll need to do this on Hubzilla to keep contacts from spamming you with boosts)

Neither Hubzilla nor (streams) is something that you can join and use away on 100% bone-stock default settings just like that.

And truth be told: If you give 5,000+ Fediverse actors full permissions to send you all their stuff, your unread activities counter (this exists, yes) will be up to "99+" every few minutes. I myself don't even have 100 active connections that are allowed to send me anything. On some of them, I filter boosts out. And yet, I get well over 100 unread activities per day that I have to catch up with.

In fact, Hubzilla and (streams) will suck even more content onto your stream than Mastodon. That's because they support threaded conversations. They don't show you single posts. They show you whole threads, including comments by people whom you don't follow and who didn't mention you.

I don't know if you follow Eugen Rochko. But if you do, imagine he posts something. 200 people reply. On Mastodon, you get Rochko's post. On Hubzilla and (streams), you get Rochko's post and 200 replies flooding onto your stream by and by.

Seriously, if you really want to move to Hubzilla (or (streams)), start over from scratch. And go slowly instead of following shit-tons of people right off the bat to have your stream abuzz like on Twitter or Facebook.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla #Streams #(streams)

@Alison Wilder Because if you want full-blown user rights and all the same features as a local user on all over 30,000 Fediverse instances, you need a local user account on each one of them.

This means two things:

• If you come over to the Fediverse for the first time, and you register your first account on Mastodon, you automatically also register an account on 30,000+ more instances.
• If you decide to host your own instance of whatever, and you spin it up for the first time, your instance immediately creates tens of millions of user accounts. One for everyone who has ever joined the Fediverse. Because anyone may decide to come over to your instance and use it, just like so.

For one, this is utter overkill.

Besides, this is technologically impossible. This would require all Fediverse instances to know all other Fediverse instances. With no exceptions. Like, if I start up my own (streams) instance for the first time, and half a second later, someone on the other side of the globe starts up a Gancio instance, they would immediately have to know each other. And all the other instances in the Fediverse.

And, of course, it would require a newly-launched instance to know all Fediverse users. Again, with no exception.

How and from which source are they supposed to know?

That said, there is a single sign-on system for the Fediverse. It's called OpenWebAuth. It was created by @Mike Macgirvin (creator of Friendica and all its descendants) in the late 2010s already for now-defunct Zap, a fork (of a fork?) of Hubzilla which, in turn, is a fork of the currently hyped Facebook alternative Friendica. It was backported to Hubzilla in 2020. Everything that came after Zap, including the still existing streams repository, got it, too.

However, first of all, OpenWebAuth is only fully implemented on Hubzilla, (streams) and Forte. Plus, it has client-side support on Friendica. This means that Hubzilla, (streams) and Forte recognise logins on all four, but Friendica doesn't recognise logins from anywhere.

As for Mastodon, OpenWebAuth implementation was actually developed to the point of an official merge request in Mastodon's GitHub repository. As far as I know, it was rejected. Mastodon won't implement OpenWebAuth, full stop.

Besides, it doesn't give you all the same power as a local user. You can't log into Friendica, go to a Hubzilla hub and create a wiki or a webpage or a CalDAV calendar, just like so.

OpenWebAuth is only for guest permissions. Because on Hubzilla, (streams) and Forte, permissions are everything.

For example, let's assume you have an account and a channel on (streams). Let's also assume that your (streams) channel and this Hubzilla channel of mine here are connected. Furthermore, let's assume that I've decided to only allow my own full connections to see my profile.

If you're logged out, and you go to my profile page, you see nothing.

But then you log in. And you come back to my profile page (provided your browser is configured so that the Hubzilla hub that I call home is allowed to create cookies). My home hub recognises your login on (streams). It identifies you as you, as one of my contacts. Thus, it identifies you as someone who is permitted to see my profile.

And all of a sudden, you see my profile.

That, for example, is what OpenWebAuth is for.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Hubzilla #Zap #Streams #(streams) #Forte #SingleSignOn #OpenWebAuth

@Droid Boy :coolified: Eine Option ist ein WordPress-Blog mit der ActivityPub-Erweiterung von @Matthias Pfefferle. Offenkundigster Nachteil: Du wirst höchstwahrscheinlich zumindest aktuell dein Blog tutto kompletto selber hosten müssen. Ich weiß nicht, ob es irgendwo fix und fertig gehostete WordPress-Blogs mit ActivityPub gibt.

Option 2: WriteFreely. Einfache, cleane, ablenkungslose Oberfläche in der Art wie Medium. Nachteile: Kommentare gibt's nicht (also gar nicht), du kannst von WriteFreely aus nichts und niemandem folgen (sondern nur selber bloggen), und Bilder wirst du selber nochmal woanders hosten müssen, von wo aus du sie in deine Posts hotlinken mußt.

Option 3: Plume. Auch sehr aufgeräumt, kann Kommentare, hat eingebauten Filespace für Bilder. Die Entwicklung ist aber komplett eingeschlafen, weil die Entwickler keine Zeit haben, und sie selbst empfehlen aktuell sogar WriteFreely.

Optionen 4, 5 und 6: Friendica, Hubzilla, (streams). Alle vom selben Schöpfer, @Mike Macgirvin : Friendica ist vom 2010, Hubzilla ist ein Friendica-Fork von 2012 und 2015 zu Hubzilla geworden, (streams) ist noch einen Haufen Forks später von 2021. Hier habe ich mal Vergleichstabellen gemacht, die auch Mastodon einschließen für die, die nur Mastodon kennen und Mastodon als Maßstab nehmen.

Friendica und (streams) können alles, Hubzilla noch mehr. Du kannst sie als Facebook-Ersatz nutzen, du kannst sie, wenn du willst, als Twitter-Ersatz nutzen, du kannst sie gleichzeitig als vollwertige Blogging-Plattform mit allem Schickimicki nutzen. Titel, Zusammenfassung (auf Friendica und (streams) als Tagpaar, auf Hubzilla als eigenständiges Feld), sehr viele Zeichen (Friendica: 200.000, (streams): über 24 Millionen), beliebig viele Bilder in Posts einbetten, alles Mögliche an Textformatierung und -gestaltung, Hashtag-Cloud, separate Kategorien, die teilweise auch als Cloud gehen, usw. usf.

Hubzilla hat sogar noch eine separate, optionale Artikel-"App", mit der du sowas wie Blogposts veröffentlichen kannst, die dann aber nicht über ActivityPub rausgehen und Mastodon-Nutzer nicht nerven. (Dafür gehen sie aber auch nicht als Atom-Feed raus.)

Dazu hast du eingebauten Filespace, den du auf Hubzilla und (streams) sogar per WebDAV einbinden kannst. Auf Friendica und (streams) kannst du im Filespace für jedes Bild einen Alt-Text eingeben, der dann automatisch mit dem Bild in den Post eingebettet wird. Du hast auch Berechtigungssteuerungen, die auf Hubzilla und (streams) noch leistungsfähiger sind als auf Friendica. Zumindest auf Hubzilla und (streams) hast du Kommentarkontrolle auf drei Ebenen, die auf (streams) auf Per-Post-Ebene sogar noch etwas ausgefuchster sein kann.

Hubzilla und (streams) haben sogar die sonst fast überall im Fediverse übliche bombenfeste Verbindung zwischen Konto und Identität aufgelöst. Du kannst beliebig viele, völlig separate Identitäten ("Kanäle") auf demselben Konto haben und lustig dazwischen hin- und herschalten, ohne dich aus- und wieder einloggen zu müssen. Persönlicher Social-Networking-Kanal + vier davon (und voneinander) separate Blogs + ein, zwei Gruppen/Foren, alles auf einem Login? Kein Problem.

Falls du selbst hosten willst: Alle drei kommen mit einem LAMP-Stack klar. Kein exotisches Zeugs nötig.

Falls du nicht selbst hosten willst: Hubzilla und (streams) bieten nomadische Identität. Du kannst also einzelne Kanäle über mehrere Serverinstanzen klonen, und die werden wie bidirektionale Live-Backups immer gegeneinander synchronisiert. Wenn ein Server ausfällt, hast du immer noch mindestens eine Reserve.

Okay, jetzt kommen die Nachteile: Alle drei sind mächtig. Friendica ist sehr mächtig, (streams) sehr sehr mächtig, Hubzilla sehr sehr sehr mächtig. Entsprechend sind auch die Lernkurven, zumal keins von den dreien eine UI hat, die aussieht, als wäre sie erst gestern von einem Startup für ein paar Millionen an Risikokapital von Profis designt worden.

Außerdem sind es keine puristischen, spezialisierten Blogginganwendungen. Sie haben also auch für den Leser nicht unbedingt die aufgeräumte Oberfläche eines WordPress-Blog, geschweige denn von Medium.

Für Friendica gibt's keine iOS-App, und Mastodon-Apps gehen eher so lala, wenn überhaupt. Für Hubzilla und (streams) gibt's gar keine Apps, und Mastodon-Apps gehen gar nicht und werden das auch nie.

Noch dazu hat (streams) aktuell nur zwei öffentliche Instanzen mit offener Registrierung, die obendrein fast unmöglich zu finden sind, davon nur eine in Europa. Beide haben allerdings sehr kompetente Admins.

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #WordPress #WordPress_ActivityPub_Plugin #WriteFreely #Plume #Friendica #Hubzilla #Streams #(streams) #Blog #Blogs #Blogging