jrollans.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
I was scrolling @pixelix and discovered @ghostbyte is getting the instance statistic data from new fediverse tracker they built called https://fedisea.surf
Also open source with their own crawler https://github.com/ghostbyte-dev/fedisea-web #fedidev #fediverse #ActivityPub
This is the main discussion thread for the draft FEP-c0d0: Context Locking
Context locking (and its inverse, unlocking) refer to the action whereby a topic no longer accepts new replies.
This proposal introduces a locked property on the context object, and a new activity type, Lock, to signal changes to a topic's locked state across the fediverse. Unlocking is expressed with the standard ActivityStreams Undo activity, applied to the original Lock. It builds on FEP 1b12: Group federation for audience identification (the audience property) and the Announce wrapping pattern, and on FEP fe34: Origin-based security model for authorization.
This FEP is a sibling of FEP f15d: Context Relocation and Removal, which covers the Move and Remove moderation actions.
The full FEP text can be found at https://github.com/julianlam/feps/blob/context-locking/fep/c0d0/fep-c0d0.md
Week in Fediverse 2026-09-18
Servers
- Wafrn v2026.09.11
- TinyAP v0.2.0
- Mastodon v4.7.2
- PeerTube v8.3.0
- NodeBB v4.16.0
- NeoDB v0.19.0
- Gush! v0.0.42
- PieFed v1.7.16
- Lemmy Dev Update August 2026 and 1.0.0-beta.2
- Trunk & Tidbits, August 2026 (Mastodon)
Clients
- Fedilab v3.43.4
- Smither v3.6.5
- Voyager v2.49.1
- mlmym v26.4.0
Protocol
- FEP-22cd: Attributing translations
- FEP-7628: Move actor (Final)
Articles
- People, Algorithms, Social media and the Fediverse
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/01a091f1-ecbc-7923-ad6a-e9bd3bae78e3
Kleine Bestandsaufnahme: Von Mastodon aus mit Pixelfed-Leuten quatschen, Lemmy-Diskussionen liken, PeerTube-Videos boosten, alles ein Konto, alles ein Netzwerk, kein Algorithmus fragt mich vorher um Erlaubnis. Wenn das mal keine Zauberei ist?! Bei Twitter hätte ich dafür sieben Apps gebraucht und trotzdem nur Werbung bekommen.
#fediverse #activitypub #dezentralisierung #opensource #schicksalsjahreeineskaisers
What will littleFedi's official-ish Plushie end up being ?
Whatever it is,
I want one.
Or two.
Or a few.
| #littleFedi #ActivityPub #Plushies #Plushie #Stuffies #Stuffie #Stuffy
Welcome back to another minor release of NodeBB, at a blistering pace after the last release about three weeks ago! 
Here's what changed since v4.15.0, and what you can expect to see in v4.16.0. [...]
As always, we spent quite a bit of time here improving NodeBB's AP support.
cavage-12 draft standard, so moving to the RFC is a step in the right directionrelay.fedi.buzz or tags.pub), and automatically categorize content into NodeBB<details> tagAnnounce, which is like a Mastodon-style boostKurzer Hinweis an andere Mastodon-Admins: Diese Registrierungs-Spam-Welle ist noch nicht überstanden.
Bei lsbt.me kamen zunächst massenhaft API-Registrierungen mit Python/aiohttp rein. Auffällig waren Nutzernamen nach dem Muster bp plus 16 Hex-Zeichen und als Antragstext immer Automated protocol deliverability probe. Eine enge Sperre auf diesen User-Agent hat die erste Welle gestoppt.
Heute kamen trotzdem fünf neue Registrierungen mit denselben Nutzernamen und demselben Antragstext. Der Bot gab sich diesmal einfach als Chrome 126 aus. Genau deshalb taugt ein User-Agent nur als kurzfristiger Filter. Er ist ein frei wählbarer Header.
Die Requests laufen über POST /api/v1/accounts. Dieser Endpoint erlaubt Client-Apps, einen neuen lokalen Account direkt in der App anzulegen. Für OAuth-Verbindungen bestehender Accounts braucht ihn keine App. Auch #FediSuite nutzt ihn nicht. Sie registriert sich über /api/v1/apps, holt die Zustimmung über /oauth/authorize und arbeitet danach mit einem User-Token. Die normale Registrierung über die Mastodon-Webseite läuft ebenfalls getrennt über POST /auth.
Ich habe die API-Kontoerstellung auf lsbt.me deshalb komplett abgeschaltet. Webregistrierung, OAuth und bestehende Clients laufen unverändert weiter. Wer einen neuen Account möchte, registriert sich einmal ganz normal wie bisher im Web und kann danach jeden Client nutzen.
Falls ihr diesen optionalen Native-Sign-up-Weg ebenfalls nicht anbieten wollt, könnt ihr in eurem Nginx-Serverblock vor dem allgemeinen location /-Block Folgendes ergänzen. Das Beispiel setzt den in vielen Mastodon-Nginx-Configs vorhandenen @proxy voraus:
location = /api/v1/accounts {
limit_except GET {
deny all;
} try_files $uri @proxy;
}
Damit erhält nur POST /api/v1/accounts ein 403. Der lesende GET-Endpoint bleibt erreichbar. Danach wie immer nginx -t und erst bei erfolgreichem Test reloaden.
#Mastodon #Fediverse #MastoAdmin #FediAdmin #FediMod #FediBlock #Moderation #Registration #Spam #Nginx #SelfHosting #SysAdmin #ActivityPub
Quick heads-up for other Mastodon admins: this registration spam wave isn't over yet.
On lsbt.me, we first saw a flood of API registrations using Python/aiohttp. The telltale signs were usernames following the pattern bp plus 16 hex characters, and the sign-up reason was always "Automated protocol deliverability probe". A narrow block on that user agent stopped the first wave.
Today, however, five new registrations came in with the same usernames and the same sign-up reason. This time the bot simply identified itself as Chrome 126. That's exactly why a user agent is only useful as a short-term filter. It's a header the client can set to anything.
The requests go to POST /api/v1/accounts. This endpoint lets client apps create a new local account directly in the app. No app needs it for OAuth connections to existing accounts. #FediSuite doesn't use it either. It registers itself via /api/v1/apps, obtains consent via /oauth/authorize, and then works with a user token. Regular sign-up through the Mastodon website is also handled separately via POST /auth.
So I've completely disabled API account creation on lsbt.me. Web sign-up, OAuth, and existing clients keep working as before. Anyone who wants a new account just signs up once on the web as usual and can then use any client.
If you'd also rather not offer this optional native sign-up path, you can add the following to your Nginx server block, before the general location / block. The example assumes the @proxy location that many Mastodon Nginx configs already include:
location = /api/v1/accounts {
limit_except GET {
deny all;
} try_files $uri @proxy;
}
This returns a 403 only for POST /api/v1/accounts. The read-only GET endpoint remains reachable. As always, run nginx -t afterwards and only reload once the test passes.
#Mastodon #Fediverse #MastoAdmin #FediAdmin #FediMod #FediBlock #Moderation #Registration #Spam #Nginx #SelfHosting #SysAdmin #ActivityPub
A couple quick notes on ActivityPub
A few weeks ago, I made this site publish to ActivityPub (really mostly thinking about Mastodon, although as an open standard other software can consume it). Just wanted to write down a few notes on the experience for posterity. …
»Trunk & Tidbits, August 2026« https://blog.joinmastodon.org/2026/09/trunk-tidbits-august-2026/?Fedizen.EU #Fedizen #Fediverse #ActivityPub #News
Als Admin von #Friendica beschäftigt mich schon länger eine Frage:
Warum zeigen viele entfernte #Threads beim normalen Lesen nur zwei, drei Antworten und der Rest taucht erst auf, wenn ich (in friendica als Nutzer) „Vollständiger Thread“ anklicke, oft erst Tage später?
Die Ursache ist mir bekannt: #ActivityPub liefert nur adressiert aus, was nie zugestellt wird, kann mein Knoten schlicht nicht anzeigen.
Wie aber gehen andere Admins damit um? Ist das für euch eine akzeptierte Grenze des #Fediverse, oder justiert ihr aktiv an fetch_replies und max_fetchreplies_depth?
Mich würde interessieren, ob die Thread-Lücken bei #Mastodon, #Pleroma, #Akkoma und Co. genauso auftreten oder ob ich das primär in der Friendica-Welt zu spüren bekomme. Bei Mastodon sollte es IMHO jedenfalls genauso sein.
Wer von euch überlässt das Nachziehen der Replies-Collection komplett dem eigenen Server, wer greift manuell ein, oder hat einen pragmatischen Weg dazwischen gefunden?
Eigentlich sollte man erwarten, dass die ausliefernden Server ihre Replies-Collection halbwegs zuverlässig pflegen, statt dass jeder Betreiber auf eigene Faust nachhelfen muss.
Über konkrete Erfahrungen und Einstellungen würde ich mich freuen.
Ok, people of #Mastodon, can anyone explain to me why it is not possible to somehow connect #ActivityPub and #ATProto. It seems a bit ridiculous to me that we have #alternatives to #BigTech that seem to work against each other.
Links to posts or blogs that explain the problem a bit further would also be super helpful. Please share! Thank you! #Fediverse #Bluesky #Eurosky
Just finished listening to this interview with Eli Mallen (@iameli) of https://stream.place (from last year) talk about taking on Twitch in the open social web. He talked about his history in other protocol spaces like SSB and Ethereum and why he chose to work with #ATProto and not #ActivityPub
https://devtools.fm/episode/140
Laravel + PHP gains a batteries included package for ActivityPub support, with both draft-cavage and RFC 9421 HTTP Sig support and the ability to extend every aspect, with before() and after() hooks for easy custom processing.
It's quite amazing.
I'll be tagging a new release this week.
The social web is evolving: into open, decentralized spaces no single organization controls. The Social Web Foundation is building a global town square that works for everyone: E2E encryption, GDPR-ready privacy, a healthier fediverse.
laravel-activitypub, a batteries included ActivityPub package for laravel.
Soon will power @pixelfed and @joinloops
Shoutout to @FediverseSymbol
Okay, laravel-activitypub is near ready to ship!
I'll be testing it with shutter, a single user activitypub server for image sharing.
Making real progress on laravel-activitypub, a batteries included ActivityPub package for laravel.
This will replace federation logic in @pixelfed and @joinloops and make it really easy to implement AP in your own laravel apps!
LOLA is a proposal for live online account portability between two ActivityPub servers at the request of a user. The goal is to allow the user to pursue the following workflow:
- Request a destination server to copy an ActivityPub account from a source server
- Authorize the destination server to the source server
- See the content in its new location after the destination server completes copying it over
- Optionally, at a later time, ask the source server to send notifications to followers that the account is moving
- Optionally, at a later time, redirect the content at the source server to the destination server
I do host my own single user #snac server and want to keep it that way. I do have more than one account, but since I am by myself - my local timeline is useless. If I only could have geographically close messages in there!
This feature belongs into #ActivityPub and not in one implementation of it!
Also pinging @grunfink@comam.es - maybe you're insterested
I just added a new watchlist to the fediverse.party wiki, for CMS that have ActivityPub plugins;
https://codeberg.org/fediverse/fediparty/wiki/CMS+with+ActivityPub+plugins+-+watchlist.-
As always, if you see any gaps or errors, sing out!
RE: https://mastodon.social/@dansup/117246306213045632
I swore not to speak about #FediHood any more, but what #Pixelfed is doing is great news for #ActivityPub.
Pixelfed already sends the location as a Place object with latitude and longitude, so FediHood can read it and put markers on a map.
Local timelines used to mean one instance. Now they can mean people actually around you.
RE: https://mastodon.social/@dansup/117246306213045632
I swore not to speak about #FediHood any more, but what #Pixelfed is doing is great news for #ActivityPub.
Pixelfed already sends the location as a Place object with latitude and longitude, so FediHood can read it and put markers on a map.
Local timelines used to mean one instance. Now they can mean people actually around you.
Week in Fediverse 2026-09-11
Servers
- Hubzilla v11.4.1
- Bookwyrm v0.9.3
- Cookifed v0.1.0
- Ktistec v3.12.1
- Misskey v2026.9.0
- gathio v1.6.7
- NeoDB v0.18.2
- Appy v0.7.0
- PieFed v1.7.15
- Wafrn v2026.09.01
Clients
- Voyager v2.49.0
- Miria v4.0.1
- Aria v1.5.13
Tools and Plugins
- Enable Mastodon Apps v1.6.4 (WordPress plugin)
Articles
- Static ActivityPub Publishing
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/01a06eb0-8683-70d3-bb1d-19ef2967e02b
🆕 blog! “Scattered thoughts on social geolocation”
I want to be able to share my location with my friends on social media. Twitter (RIP) had a way to attach an optional location to a post. Facebook still lets me check in to venues. But neither ActivityPub (Mastodon) nor AT Protocol (BlueSky) allow me …
👀 Read more: https://shkspr.mobi/blog/2026/07/scattered-thoughts-on-social-geolocation/
⸻
#ActivityPub #BlueSky #fediverse #FourSquare #geolocation #json #openstandards #OpenStreetMap
The EFF is promoting the Fediverse in an online event next week!
We've put it on our community calendar: https://fediforum.org/events
FediForum Fall 2026 starts in four weeks, exactly.
Registrations and proposed topics are coming. Check some of what has been proposed so far on https://fediforum.org/2026-10/
Right after @berlinfediday is over, I am hosting another edition of
Berlin Federated Network Exploration Circle / #BFNEC
Sept 13th at 7pm at @offline
✸ @pukkamustard will talk about their work on ERIS and give us the backstory on their initiation of the fediverse's FEP process.
⁂ @f will discuss his work on @sutty, a platform aimed at giving organizations and collectives the means to publish and host more secure websites. He will also talk about how they recently added #ActivityPub federation.
do australian fedi conferences exist? I've seen a few but they're always at like, 1am aest
#Loops has entered #beta with #ActivityPub support, allowing users to connect with creators across the #fediverse. This means users can follow and interact with creators on platforms like #Mastodon and #Pixelfed, and vice versa. Loops has implemented several technical features to ensure smooth federation, including a shared inbox, HTTP signatures, and smart content representation. https://blog.joinloops.org/loops-joins-the-fediverse/?Fedizen.EU #Fedizen #Fediverse #ActivityPub #News
Hashtag following also allow URLs to RSS feeds of ActivityPub objects (like e.g. https://mastodon.social/tags/ThankYouTuesday).
Users can now configure a webhook to receive an HTTP POST for every notification. This can be useful for implementing bots that react to activities, like autorepliers, chatbots or interactive textual games (see snac(1) for more information).
The number of pending follow confirmations is shown next to the "people" link.
Faster performance metrics (contributed by dandelions).
Improved lowercasing in hashtags (contributed by postscriptum).
A search-by-url tweak for implementations that return 200 for invalid webfinger queries (e.g. piefed).
Mastodon API: added follow confirmation endpoints, fixed collisions in attachment file names.
Fixed potential crashes in attachment uploads.
If you find #snac useful, please consider buying grunfink a coffee or contributing via LiberaPay.
Notifications are now shown in a more compact way (i.e. all reactions are shown just above your post, instead of repeating the post ad nauseam for every reaction).
New command-line option unmute to, well, no-longer-mute an actor.
The private timeline now includes an approximate mark between new posts and "already seen" ones.
Fixed a spurious 404 error in the instance root URL for some configurations.
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
This release has been inspired by the song The Answers to the Questions by #Christabell and #DavidLynch.