ActivityPub (Fediverse) — Connect it to MokonyxSocial

Connect ActivityPub and MokonyxSocial will publish your content as a Create/Note activity into your actor's outbox, so it federates out to your followers on Mastodon, Pleroma, and the wider Fediverse. One heads-up before you start: ActivityPub is a raw federation protocol, not a hosted API, so you'll need an actor whose outbox you can actually write to — a plain hosted Mastodon account usually won't expose one.

What you need

• An ActivityPub actor you control on a server that exposes a writable outbox.
• A bearer token allowed to POST activities to that outbox.
• The full HTTPS URL of your actor's outbox.

Get your credentials

Access token access_token (required)

This is the bearer token that lets MokonyxSocial post to your outbox on your behalf. How you get it depends on where your actor lives:

• On a Mastodon-compatible instance: log in, head to Preferences → Development → New application (https:///settings/applications), tick the write:statuses and read scopes, save, and copy the Your access token value it shows you.
• On your own server / custom actor: mint a bearer token through your admin panel or OAuth flow that's allowed to post to the outbox.

Paste just the raw token — no Bearer in front.

Actor outbox URL actor_outbox (required)

This is the exact address your posts get delivered to. To find it, fetch your actor object (your profile URL requested with Accept: application/activity+json) and look for the "outbox" field in the JSON — it'll look like https:///users//outbox. Copy that value in verbatim.

Set it up in MokonyxSocial

1. In Joomla admin, go to Components → MokonyxSocial → Services → New.
2. Choose ActivityPub.
3. Enter the credentials above.
4. Click Send Test to check it, then Save & Close and make sure it's Published.

Verify

Once Send Test goes green, look at your actor's public timeline or ask a follower to check their Fediverse app for the test note. When you publish something real, confirm it shows in the outbox and lands on remote instances.

Troubleshooting

• Getting 401 or 403? Your token probably lacks write:statuses or has expired — regenerate it with write scope.
• 404 on the outbox? The actor_outbox URL is off — re-fetch your actor JSON and copy the outbox field exactly.
• Posted but nobody sees it? Remote folks may not follow your actor yet, or your server's HTTP signature delivery needs attention.
• 415 error? Your host wants application/activity+json — that's a server-side setting on your instance.

Notes & limits

• Your home instance sets the character cap (Mastodon defaults to 500); anything longer gets trimmed by the receiver.
• Whether media attaches depends on your actor's host.
• Federation is asynchronous, so give it a few seconds to minutes to reach other servers.
• This is the most technical connector here — if all you have is a standard hosted Mastodon login without outbox access, a dedicated Mastodon connector will be far easier.