Search

Items tagged with: Fediverse


Mutual Aid Request Roundup 21 Oct 2026


The media in this post is not displayed to visitors. To view it, please go to the original post.

1,929 words
8–12 minutes

How Many More Victims?


Hundreds of people broke through the barricades at the Central Kalimantan governor’s office in Palangka Raya on Monday afternoon, on the eve of the Prabowo-Gibran government’s second anniversary. The Aliansi Masyarakat Kalteng Melawan came with student councils, among them BEM UI, whose members flew in from Jakarta. Their central demand was that Jakarta declare the fires in Central Kalimantan a national disaster. Governor Agustiar Sabran came out and sat with them, then left to pray at the Asr call and did not return. The crowd took the courtyard. Organisers say a fourth and larger demonstration is coming. The haze has run for four months.

The Health Ministry counted 314,124 acute respiratory infection cases in fire-affected areas between 20 August and 20 October, across seven provinces and 65 districts and cities. Children aged 0 to 5 make up 70,890 of them. Tuesday alone added 3,269. As of Tuesday afternoon, Central Kalimantan had 295 “oxygen houses” running, South Kalimantan 127 and West Kalimantan 35. On 16 October, IQAir recorded air pollution in Palangka Raya in the hazardous range, with an air quality index above 300. Kompas reported on 17 October the death of a six-year-old, suspected to be from a respiratory infection, whose uncle asked: “Nunggu korban berapa lagi?” How many more victims are we waiting for? The smoke disrupted 390 flights across Kalimantan, with Central Kalimantan hit worst. The ministry’s advice is to stay home, work or study online where possible and wear an N95 or KN95 mask. It carves out field workers and public service staff. The people whose jobs cannot move online keep breathing it.

On 14 October anti-corruption investigators named five suspects over alleged corruption involving emergency funds at the national disaster agency, BNPB, following raids earlier that week. Among the suspects was the brother of BNPB head Suharyanto, who was replaced the next day. Two days before the suspects were named, Prabowo had expressed surprise at a report that only 639.23 hectares remained burning across six provinces, having expected tens of thousands. The Cabinet Secretariat’s own account described those 639 hectares as land undergoing firefighting operations. Syahganda Nainggolan, who heads the government communications office, has called the fires “beyond human error” and “truly nature”.

Arniyanti of Lembaga Gemawan says over 70 percent of the fire spots sit inside company concessions. Police were investigating 96 companies in August and the government had imposed administrative sanctions on 26. Environmental group Pantau Gambut identifies industrial-scale plantation development and peatland drainage as causes of the degradation that leaves peatlands vulnerable to fire. Boy Jerry Even Sembiring, executive director of Walhi, says accountability must reach those who control and profit from land ownership. In Pontianak a coalition led by Nafas Kalbar, with Indigenous people and religious youth groups among the plaintiffs, is suing the president, the vice-president, ministers and the national police chief for negligence, and asking for a national emergency declaration, free health care for vulnerable groups and prosecutions. Seven residents did this after the 2015 fires, won at district court, and saw the decision overturned in 2022. The plantation is a colonial invention and the concession is its descendant: land organised around a return collected somewhere other than where the smoke settles. Singapore has raised the prospect of fines or charges against companies responsible for the fires. Smoke that crosses a border gets a lawyer. Smoke that stays inside it gets “truly nature.”

I write as an Indonesian, and the part I will not let a ministry’s advice bury is that this ledger runs in one direction everywhere. In Palangka Raya the price of cheap land is booked to children’s lungs. In Gaza it is booked to a flour price, while WFP pleads for $450 million against the $2.8 billion in bombs Washington approved for Israel in September. Households in Iran absorb a blockade whose squeeze on raw materials reaches the medicine they depend on. Jakarta sits inside the same arrangement. In February Prabowo pledged 8,000 troops “or more” to Trump’s Gaza stabilisation force, and Al Jazeera’s 13 October roundup records that no stabilisation force has deployed. The state that signs up to Washington’s arrangements and the state that issued the concessions are one state, and neither answers to the people downwind of either.

The people behind the requests below are downwind of the same decisions. A concession map, a bomb sale and a blockade look like three different stories, and they share one method: capital extracts, the cost is booked to whoever lives closest to it, and the institutions meant to catch the fall are underfunded, looted or answering to someone else. In Kalimantan the fall is a six-year-old’s lungs, while the national disaster agency’s emergency funds are under investigation. In Gaza, it is the soaring cost of staple foods. For a person with overdue rent, medication running out in days or a stalled disability payment, it arrives as a bill. These struggles connect because one system produces them, and because the same absence meets each one: nobody official is coming.

Direct action here means closing the gap ourselves, this week. The ministry says to stay home and buy an N95, which assumes the money exists. Mutual aid supplies it: a transfer from someone with a little to someone with none, with no concession, ministry or committee in between. Every request below belongs to a person who has already tried the official routes. Give to the ones you can, share each one in the group chats where you already hold trust, and ask one person with money to match what you gave. The state is still deciding what to call this. A household needs its answer now.


A note before the list: mutualaidspace.org’s submission form is live. Submitting a request there gets it federated as @comrade, automatically tagged for wider reach, and listed publicly under Comrades & Community or Victims of Empire, whether or not the person asking has a Fediverse account of their own. No verification process, no proof of suffering required. More on the project itself: mutualaidspace.org/about

✨Mutual Aid Roundup✨

@ctrlaltglitch @starryeyes @blaurascon @kitwinter @KestrelSWard @thereaders @sickandtired @tiredpinklover @roxy @lowroarrawr


✨Palestinian Campaign Spotlight✨

95140201 1761672052643598 R

Together for Marah & Mila: Surviving the War in Gaza

Marah has been running a fever above 39°C and was too weak to post for days. She says she has not received enough support, and her health is not okay. Her campaign carries her family through the siege [View original post]

@marahismail


REDISTRIBUTE

107476417 1790618829695995 R

Save Hadeel and her children

Hadeel is a mother of two young daughters living in a tattered tent in Gaza. With winter, storms and bitter cold arriving, rainwater floods the space. She urgently needs a tent and tarpaulins to protect her children [View original post].

@jojojulia


REDISTRIBUTE

Gaza Verified Archive
Verified Palestinian campaigns under $200
These are verified Palestinian accounts whose campaigns received less than $200 in the past 7 days.

Nine of many. The archive holds the rest.
@EngFarahGaza@mastodon.social @HadeelMohammed@mastodon.social @hadeel_2026@mastodon.world @samour1997@mastodon.social @tareqradi@mastodon.social @danyarelkhodari@mastodon.social @mhoeed@mastodon.social @aseelfromgz@mastodon.social @maher553533@mastodon.social
Open the archive, find the campaign link on each account, give directly where possible, and share the campaign links that need movement.
View underfunded campaign list About Gaza Verified Campaigns


@mutualaid @mutualaid @disability @disability @autistics @actuallyadhd @theleftistlawyer @frugalcoffee @wrzky @wrzky @edendestroyer @QasimRashid #Gaza @palestine @indonesia @indonesia #Palestine #genocide #mutualaid #anarchism #internationalism #MutualAidRequest #DisabilityMutualAid #MutualAidSpace #DisabilityCrowdfund #TransMutualAid #QueerMutualAid #lgbtq #politics #EmergencyCrowdfund #GazaMutualAid #poverty #healthcare #mentalhealth #disability #neurodivergence #activism #fedihelp #fediverse #HelpFolksLive2026 #socialmedia #BlackMutualAid #writer #MutualAidVoid #helpsky #press #SEAblings #fediforgaza #Indonesia #wildfires #iran

🗣️Support Corner🗣️

📱Share this article far and wide. Subscribe to get this update in your inbox!

This space is held together by a disabled Indonesian Muslim woman. Monthly support keeps me fed, medicated, and connected, and helps me keep resisting corporate funding and the humanitarian-industrial complex through my writing and mutual aid projects.

If you find this voluntary work worth supporting, please do so by pledging as little as $1 monthly via Liberapay or other tiers available across Liberapay, ko-fi, and Patreon. One-off support helps too. Any amount genuinely helps.

Paid Membership on Patreon

Ko-fi voluntary monthly support

Liberapay voluntary monthly support

Monthly Support Package





Week in Fediverse 2026-11-06


Servers

- Mitra v5.12.0
- ties v0.4.0
- Mastodon v4.7.5
- ActivityPub for WordPress v9.4.3
- NeoDB v0.20.0
- NodeBB v4.16.7
- Wafrn v2026.11.01
- PieFed v1.7.19
- FitPub v1.3.1
- Lemmy Development Update October 2026

Clients

- Smither v3.7.0
- Aria v1.5.16
- Snowdrop v0.0.10

Tools and Plugins

- FediFetcher v8.2.4

For developers

- APx v0.28.0

Protocol

- FEP-f12e: Consent-respecting attributions
- FEP-2fa1: Federated Categories
- FEP-5837: Content Credentials for Media Attachments

Articles

- Noodling on Nodeinfo

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: mitra.social/objects/01a18e8f-…


Week in Fediverse 2026-10-30


Servers

- Pleroma v2.11.0
- Hollo v0.9.25
- Betula v1.9.0
- Mastodon v4.7.4
- ActivityPub for WordPress v9.4.0
- Bookwyrm v0.9.4
- PeerTube v8.3.2
- Misskey v2026.10.1
- Ktistec v3.14.0
- NeoDB v0.19.10
- Iceshrimp.NET v2026.1.3-beta
- NodeBB v4.16.5
- wanderer v0.21.2
- Wafrn v2026.10.03
- Lemmy v0.19.21
- snac v2.97
- Trunk & Tidbits, September 2026 (Mastodon)

Clients

- Pachli v3.10.0
- tooi v0.28.0
- RaccoonForFriendica v1.1.8

Tools and Plugins

- Event Bridge for ActivityPub v2.0.0 (WordPress plugin)

For developers

- Fedify v2.4.5

Protocol

- FEP-65ca: Common Client Configuration
- FEP-d1cb: Same-origin actor re-identification
- FEP-f799: Coordinated Inbox Delivery Suspension

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: mitra.social/objects/01a16a51-…


9.4.0 — Picture This


The media in this post is not displayed to visitors. To view it, please go to the original post.

Someone replies to your post from Mastodon with a photo. Until now, your blog showed the text and dropped the photo. With 9.4.0 that can change.

This release is mostly about what you and your visitors see: images in replies, quotes, and your blog profile. It also contains another round of security fixes, so please update.

Images in Replies


There is a new option in the ActivityPub settings: Show images attached to replies. When you turn it on, images in replies from the Fediverse show up below the comment text. Image descriptions come along, so the images stay accessible. Replies that are only an image, with no text, are accepted too.
A Fediverse reply in the comment section, with the photo of a steaming coffee mug shown below the comment text.
The images are cached on your own server, so your visitors never load them from the other server. Up to three images per reply are shown. Images only appear on approved comments. Pending, spam and trashed comments show only their text, and their images are never downloaded.

The option is off by default. WordPress itself does not show images in comments, so this changes how your comment section looks, and we did not want to do that without asking. One thing to keep in mind: if your site approves comments automatically, images from other servers become visible without anyone looking at them first.

If you turn the option off again, the images disappear and the descriptions show as text. Turn it back on and they come back.

Quote Posts From the Fediverse


Since 7.7.0, your site can receive quotes. Now it can quote, too.

The new Federated Quote block works like the Reply block. Paste the link of a Fediverse post, and the block embeds it in your post. When you publish, your site asks the author of the quoted post for permission. If they agree, your quote is marked as verified on their server. If they decline, your post stays, but the quote turns into a plain link.
The Federated Quote block in the editor, with the URL of the quoted post, a note that the author will be asked for permission, and an embed of the post.
The editor shows where the request stands, approved or declined. It also warns you if the author does not allow quotes at all. You can still publish in that case, but the author will probably say no.

There is also a quote bookmarklet on the Tools screen, next to the reply one. Click it on any Fediverse post and you get a new draft with the Quote block already in place.

This depends on the other server. Mastodon supports the permission request since version 4.5. Other software might not answer yet, and then your quote stays unverified.

On the receiving side, the Comments screen has a new Source column. It links incoming replies and quote posts to the post they came from.

A Name and Face for Your Blog Profile


Until now, your blog profile on the Fediverse used your site title as its name and your site icon as its avatar. You can now give it its own. Under Settings → ActivityPub → Blog Profile there is a new name field and an avatar picker. If you leave them empty, nothing changes, and the site title and site icon are used as before.
The Blog Profile settings with the new name field set to "Slow Mornings" and a custom avatar.

Security, Again


As in 9.3.0, this release fixes vulnerabilities that were reported to us.

  • Signed requests are checked more strictly. They have to be addressed to your site, and signing keys from other servers are verified more carefully.
  • Blocks are respected everywhere. Accounts you blocked can no longer reply to, like, repost or quote your posts and comments, and only the sender of a reply or like can change or remove it.
  • Content from other servers is handled more safely when it is imported as posts or comments.
  • Apps you connect can only do what you allowed them to do, and only on content the connected user is allowed to change.

If you run the plugin, please update.

Smaller Things You Might Notice


  • More languages. Posts are federated with the language Polylang assigned, and posts from Mastodon apps keep the language the app set. Handles like @renée@café.example now work in mentions and search.
  • Blocks that fit your theme. The Followers and Following blocks take their colors and font from your theme, and the Reactions block has a new Counts style that can replace the comments link in a query loop.
  • Your uploads folder stops growing. Profile pictures were downloaded again on every page view, leaving a copy behind each time. The update removes the extra copies.
  • Fewer duplicate emails when another server delivers the same message twice, or when a reply also mentions you.
  • Comments: replies are no longer auto-approved because the account liked a post before, likes and reposts no longer leak into comment lists, and comment links open the right page.
  • What your followers get: no extra image under your posts, summaries that stop at the “Read more” tag, podcast files from outside your media library, and account moves that are verified and reach your followers.
  • Apps and the ActivityPub API: mentions from Mastodon apps are federated again, and replies to posts on other servers are delivered.
  • Compatibility: fixes for WordPress 7.1 and 7.2, PHP 8.5, Polylang, and sites behind a proxy.
  • Under the hood: remote content is cached through the object cache, and endpoints that other servers call now have a rate limit.

The full changelog is in the GitHub repository.

Get It


Download from WordPress.org or grab it on GitHub. If your site updates automatically, you already have it.

Turn on images in replies, try quoting a post, and let us know how it looks on your site. Which servers answer your quote requests, and which ones stay silent?

Thank You


A huge thank you to everyone who contributed code, tested early builds, filed bug reports, or reported a security issue for this release.


littleFedi: a Fediverse Server That Doesn't Need a Data Centre


I was fifteen, and there were no BBSes in my city. So every call was long distance, once a day, sometimes twice. I'd start the dialer and wait for that sound - the handshake, the negotiation, the hiss settling into a carrier - and then I was connected to a computer sitting in somebody's bedroom, a few hundred kilometres away. I was a co-sysop of a local board and a national moderator of a FidoNet area. None of my friends understood what I was doing, and they'd stopped asking to avoid an incomprehensible monologue. But I liked it, and that was enough for me.

Here's the thing about that computer in someone's bedroom. There was no data centre. No domain, no certificate authority, no hosting provider, no cloud. Just a machine, a phone line, and a person who'd decided to run it. If you wanted to reach it, you called it.

Now look at what it takes today to put a small server on the network so other people can talk to it. A public address, which most home connections no longer have. A domain, which you rent. A certificate, which somebody has to issue you. And, increasingly, a VPS somewhere, because the software won't fit on the hardware you already own.

We've added a lot of infrastructure between two people who just want to talk. That's what littleFedi is about.

What it is


A single Go binary. No Ruby, no Sidekiq, no Redis, no separate worker processes to babysit. You run init, answer a few questions, and you've got a working instance. It speaks ActivityPub, and it speaks the Mastodon client API well enough that existing apps just work.

It also runs on hardware that would make Mastodon - or even Akkoma - struggle. Most software in this space assumes a VPS with a few gigabytes of RAM and a database server next to it. We assumed a Raspberry Pi Zero W behind a home router. There's a low_power mode that tunes memory use, image decoding and thumbnail generation for exactly that kind of box, and it's tested on that kind of box, not just on a fast dev machine.

In spirit this puts littleFedi close to snac, which I've always liked a lot. Same conviction: a personal server shouldn't need a fleet of services behind it.

Federating without a public address


littleMesh is the part I'm most attached to, and it's the part that goes back to the modem.

Your instance generates an Ed25519 key pair. That key is its identity - the node's address is derived from the public key, so reaching that address means reaching the holder of that key and nobody else. No registrar, no certificate authority, nobody to ask permission from.

A small set of public lighthouse nodes help two instances find each other. Once they're introduced, the traffic runs over a second TLS session pinned to both node IDs. The lighthouse copies encrypted bytes back and forth. It never sees plaintext, and it can't impersonate either side. And if the two nodes can reach each other directly, they drop the relay after the introduction and talk peer to peer.

Which is, more or less, calling the BBS directly. Just without the phone bill.

The gateway into ordinary HTTPS


Mastodon and other regular servers can't resolve a mesh address on their own. There's no domain and no certificate for them to find.

That's what the optional HTTPS gateway is for. A lighthouse operator can run one alongside the relay, and it bridges the mesh into ordinary HTTPS for the rest of the web. The gateway has to terminate TLS to do that, so it can technically see the traffic passing through it. Which is exactly why it's a separate, opt-in piece and not something every node exposes by default.

It has two independent settings: one controls what the gateway lets ordinary internet visitors reach at all, and a second one applies again at the destination node. Left at their defaults, both allow only federation traffic - ActivityPub delivery, discovery, public media. Web login, API and media proxy stay closed unless an operator deliberately opens them.

Mesh peers talking to each other directly never touch the gateway at all. That exposure only applies to the bridge into the wider web. And all of this can be self-hosted.

Chronological timelines


Timelines are chronological. Nothing gets reordered by an engagement model.

If you want something closer to "what did I miss", there's a separate /catchup page you visit on purpose. It ranks posts using signals your own instance already has - how many people you follow boosted something, whether it continues a conversation you took part in. No external popularity score, no telemetry, nothing leaves the machine. You press "mark as read", it moves a divider, and that's the only thing it remembers.

Self-expiring posts


You can set a post to expire, with its own timer, instead of a fixed instance-wide setting.

This isn't a client-side trick that hides the post from view. The expiry goes on the same durable job queue that runs the rest of littleFedi's background work, so the deletion survives restarts and isn't lost if the process happens to be down at the moment the timer fires. When it does fire, the post is deleted and a real Delete activity goes out to everyone who received it - so it actually disappears from remote instances too, not just locally. Editing the post before then can push the timer back or cancel it.

Static blogs, with real threaded replies


littleFedi can take a Fediverse post and publish it as a page on a plain static blog, with its own Atom feed and permalinks that don't move even if you edit the post later. No JavaScript, no database hit on page load.

The part I find more interesting is that the replies aren't left out. If the author turns the option on, littleFedi pulls the public replies that were actually federated to the post, threads them the same way the timeline does, and bakes the whole tree into the generated HTML at build time. So a blog post can show a real comment thread, in the same static file, with the same guarantee as the rest of the page - no JavaScript, no live queries. Only public and unlisted replies qualify, obviously. Anything followers-only or direct never enters the picture.

Why it looks like this


This isn't minimalism for its own sake. It's about how many people simply can't run their own server today, because the requirements are too steep. The hardware, the ops complexity, or just needing a domain and a public address before you can start. We're trying to remove those barriers one at a time, while still shipping a real, federating, reasonably complete server: polls, quotes, scheduled posts, MFA, PostgreSQL and S3 if you want to scale up later.

I've written before about taking a semi-truck to buy salad. Hardware keeps getting more expensive and the software running on it keeps asking for more of it every year. That's backwards. If the machines cost more, the operational cost of what sits on them should go down, not up. Same with complexity: the default direction is to keep adding it, and we'd rather strip it out.

And there's the other half, which is closer to why any of us are doing this at all. It's the same thing that drew me to snac and to the way grunfink works on it, and the same thing that had me dialing a stranger's computer at fifteen. People building tools so that people can talk to each other. Nothing more dressed up than that. We'd rather show the servers running, talk about the Pi sitting in the corner, share a tiramisu photo if it comes up. The joy in this was never about the money it brings in. It's about what we end up building, humanly, because of it.

It's beta software, still short of a first release, and I'd rather say that plainly than oversell it. But it runs, and it federates. That's the part I wanted to write about.

#littleFedi #Fediverse


Week in Fediverse 2026-10-23


Servers

- Hubzilla v11.4.2
- TinyAP v0.2.1
- Iceshrimp v2026.5.4
- GoToSocial v0.22.3
- Wafrn v2026.10.02
- Castopod v1.15.6
- NeoDB v0.19.9.1
- Merp Relay v0.4.3
- NodeBB v4.16.4
- Loops Server v1.0.0-beta.15
- PieFed v1.8.6
- wanderer v0.21.1
- 5.0: A closer look (Mastodon)

Clients

- mlmym v26.4.1
- Summit v1.88.0
- RaccoonForFriendica v1.1.5

Tools and Plugins

- Analytodon v2.5.0

For developers

- Mastodon.py v2.3.2

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: mitra.social/objects/01a1464f-…


!Friendica Admins
📢 Einladung zum nächsten Friendica-Admin-Treffen

📅 Mittwoch, 28.10.2026
🕢 19:30 Uhr (MEZ)
💻 Online-Konferenzraum

Am kommenden Mittwoch treffen sich wieder Friendica-Administrator:innen, Instanzbetreiber:innen und Entwickler:innen zum gemeinsamen Austausch rund um den Betrieb von Friendica. 🌐

Diesmal stehen besonders die Themen im Mittelpunkt, die uns im Admin-Alltag ganz praktisch beschäftigen: Stabilität, Performance, Sicherheit und eine möglichst zuverlässige Föderation.

Unter anderem wollen wir uns mit folgenden Punkten beschäftigen:

🔹 Herausforderungen durch Anfragen von Lemmy- und GoToSocial-Servern
🔹 Gzip-Bomben und ähnliche problematische Anfragen, die beispielsweise als vermeintliche Nutzerprofile anderer Instanzen auftreten können
🔹 Möglichkeiten zur Verbesserung der Föderation einer Friendica-Instanz
🔹 Tipps zur Abstimmung von Friendica auf das eigene System – etwa bei Apache, MariaDB, PHP-FPM, Redis und den Friendica-Admin-Einstellungen
🔹 Wechsel des Addon-Repositories von GitHub zu Forgejo auf git.friendi.ca
🔹 und natürlich weitere Fragen und Erfahrungen aus dem laufenden Betrieb

💬 Wie immer soll das Treffen keine starre Vortragsveranstaltung sein. Eigene Erfahrungen, Probleme, Lösungsansätze und Fragen sind ausdrücklich willkommen.

Gerade beim Betrieb einer Friendica-Instanz profitieren wir davon, Wissen miteinander zu teilen. Was auf einer Instanz bereits gelöst wurde, kann vielleicht auch anderen weiterhelfen – und manchmal entsteht die beste Lösung erst im gemeinsamen Gespräch.

Ein herzliches Dankeschön an @Matthias (feb), der sich bereits Gedanken gemacht und die Themen für diesen Abend vorbereitet und zusammengestellt hat. 👍

Denn am Ende haben wir alle dasselbe Ziel:
Friendica stabil, sicher, schnell und zuverlässig als festen Bestandteil des Fediverse zu betreiben und weiterzuentwickeln. 🐋🌐

Wir freuen uns auf einen interessanten, konstruktiven und sicherlich wieder sehr praxisnahen Abend.

📣 Gerne weitersagen und andere Friendica-Admins, Instanzbetreiber:innen und Entwickler:innen auf das Treffen aufmerksam machen!

#Friendica #Fediverse #FriendicaAdmin #AdminTreffen #Föderation #OpenSource #Selfhosting


I'm in a somewhat awkward position - but since it's about security, and the only way to (hopefully) reach all Sharkey admins and bring this to their attention is by making a public post, I'll do just that.

You probably know that Sharkey is now based on a Misskey version that is 18 months old - falling behind is very understandable, especially for a long standing fork. But since almost 500 fediverse servers are running on Sharkey (495 according to fedidb), at least security releases are essential.

So I have to let you know that we have now notified the Sharkey devs twice about several upstream vulnerabilities we found (and fixed) in Catodon, with the first time being over a month ago. The latest stable Sharkey release was almost 5 months ago, which means they have yet to be patched in a stable release. In the meantime Misskey has also released security fixes, which have also not landed in a stable release yet.

This is not an attack on Sharkey, I hope this comes as a wakeup call, because Sharkey has truly been a great platform. But the hundreds of Sharkey admins (and users) should know about the unpatched vulnerabilities the software currently carries.

#sharkey #sharkeyadmin #misskey #fediverse


Week in Fediverse 2026-10-16


Servers

- GoToSocial v0.22.2
- Hollo v0.9.23
- snac v2.96
- Funkwhale v2.0.12
- Vernissage Server v1.44.0
- FitPub v1.3
- Hometown v1.3.1
- yukimochi/Activity-Relay v2.0.12
- Iceshrimp v2026.5.2
- NeoDB v0.19.8
- Forgejo v0.17.0
- NodeBB v4.16.3
- PieFed v1.8.5

Clients

- IceCubesApp v2.1.6
- Mastodon Bird UI v4.7.3-2026-10-11
- RaccoonForFriendica v1.1.3
- chan-fe v0.5.0

Tools and Plugins

- Poduptime v6.3.3
- FediFetcher v8.2.3
- Enable Mastodon Apps v1.7.0 (WordPress plugin)

For developers

- DrFed v0.1.0
- Fedify v2.4.4

Articles

- Some quick thoughts on Unit Testing ActivityPub
- Threads and the Fediverse: The Threat That Wasn’t

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: mitra.social/objects/01a12226-…



🚨 Currently there is a spam wave going on many #Fediverse servers

DO NOT click on the links send in the DM

Instead REPORT the account so we can take care of them ❤️

Thank you! :boost_requested:


Friendica-Umfrage: Was wünscht ihr euch?

Friendica-Umfrage: Was wünscht ihr euch?

Ich möchte mal sammeln, was sich Friendica-Nutzer für zukünftige Funktionen wünschen.
Deshalb starte ich hier eine kleine Umfrage, die einen Monat läuft, bis zum 13. November.

Schreibt mir in die Kommentare, welche Funktion ihr euch wünscht, verbessert oder neu dazu haben möchtet.

Bitte keine allgemeinen Meinungen, ob euch Friendica gefällt oder nicht, sondern nur konkrete Funktionswünsche.

Am Ende sammle ich alles und reiche es gebündelt als Vorschlag bei den Entwicklern ein.

#Friendica #Fediverse #FediTips #Umfrage #Feedback @Friendica Support


Friendica-Umfrage: Was wünscht ihr euch?

Friendica-Umfrage: Was wünscht ihr euch?

Ich möchte mal sammeln, was sich Friendica-Nutzer für zukünftige Funktionen wünschen.
Deshalb starte ich hier eine kleine Umfrage, die einen Monat läuft, bis zum 13. November.
Schreibt mir in die Kommentare, welche Funktion ihr euch wünscht, verbessert oder neu dazu haben möchtet.

Bitte keine allgemeinen Meinungen, ob euch Friendica gefällt oder nicht, sondern nur konkrete Funktionswünsche.

Am Ende sammle ich alles und reiche es gebündelt als Vorschlag bei den Entwicklern ein.

#Friendica #Fediverse #FediTips #Umfrage #Feedback !Friendica Support


I had a little chuckle to myself when I read your post. I'm reasonably educated artist (painter), MA etc. but wondered what exactly you meant by concept art so I looked it up in chatgpt..........
#fediverse #mastodon #lindasgoluppiArt


Week in Fediverse 2026-10-09


Servers

- Hollo v0.9.22
- PieFed v1.8.0
- Mitra v5.11.0
- Mbin v1.11.0
- Catodon v26.10.0
- NeoDB v0.19.6.3
- NodeBB v4.16.2
- Lemmy Development Update September 2026

Clients

- Tusky v33.0
- Pachli v3.9.1
- IceCubesApp v2.1.4
- Summit v1.87.0
- Pixelfed Mobile App v2.0.0
- Aria v1.5.15

For developers

- Fedify security updates: 2.0.30, 2.1.26, 2.2.15, 2.3.10, and 2.4.0

Protocol

- FEP-4f18: ActivityPub Network Time

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: mitra.social/objects/01a0fe1a-…


#Mitra v5.11.0

codeberg.org/silverpill/mitra/…
codeberg.org/silverpill/mitra-…

- Posts from followed FEP-1b12 groups are displayed in home timeline. Reposts attributed to a group account are no longer generated.
- Posts can be quoted on Mastodon (contributed by @lnkr)
- Support for text/plain post format.
- Database integrity violations that occurred when multiple queue workers were running have been fixed (contributed by @nak).



Week in Fediverse 2026-10-02


Servers

- PeerTube v8.3.1
- Hollo v0.9.20
- Mastodon v4.7.3
- Ibis v0.3.4
- Wafrn v2026.10.01
- Hometown v1.3.0
- Misskey v2026.10.0
- NeoDB v0.19.5
- Hatsu v0.3.5
- Wanderer v0.21.0

Clients

- Pachli v3.9.0
- Fedilab v3.45.0
- chan-fe v0.4.0
- PeerTube Mobile v2.3.0

For developers

- Fedify v2.4.0
- activitypub-federation-rust v0.6.6
- Fedipub v0.10.0

Protocol

- FEP-070c: Block synchronization across servers
- FEP-302f: QuantPub — federated personal metrics for quantified-self sharing
- FEP-6757: Content License Metadata in ActivityPub

Articles

- Why Does Nobody Use Lemmy?
- Fediverse News – Summer 2026

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: mitra.social/objects/01a0dbf1-…


Week in Fediverse 2026-09-25


Servers

- Pixelfed v0.14.0
- Ktistec v3.13.0
- XWiki ActivityPub Extension v1.7.12
- Misskey v2026.9.1
- NeoDB v0.19.3

Clients

- Fedilab v3.44.0
- Smither v3.6.7
- Pixelix v5.2.2
- RaccoonForFriendica v1.1.1
- Aria v1.5.14

Tools and Plugins

- FediFetcher v8.2.1

Protocol

- FEP-c0d0: Context Locking

Articles

- The Algorithm, Apparently Chronological

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: mitra.social/objects/01a0b604-…



Blocks on the fediverse have a consistency problem.

When a Block or Undo Block gets lost between servers, the two sides quietly disagree about who blocked whom. Sometimes that means a blocked account can still reach you.

Our fix, FEP-070c: Block synchronization across servers, is now accepted as a draft. Pixelfed is the first implementation, merged and shipping in our next release.

codeberg.org/fediverse/fep/src…

#pixelfed #pixeldev #activityPub #fediverse


Can someone explain to me why was Pixelfed, Loops, and Dansup being singled out for AI use?

There's no shortage of Fediverse software that are either built with AI assistance (including vibe coding), or welcomes AI contribution, but I'm not seeing the same level of outrage.

Did Pixelfed, Loops, and Dansup specifically promise to be AI-free?

#Fediverse #ActivityPub


Week in Fediverse 2026-09-25


Servers

- Pixelfed v0.14.0
- Ktistec v3.13.0
- XWiki ActivityPub Extension v1.7.12
- Misskey v2026.9.1
- NeoDB v0.19.3

Clients

- Fedilab v3.44.0
- Smither v3.6.7
- Pixelix v5.2.2
- RaccoonForFriendica v1.1.1
- Aria v1.5.14

Tools and Plugins

- FediFetcher v8.2.1

Protocol

- FEP-c0d0: Context Locking

Articles

- The Algorithm, Apparently Chronological

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: mitra.social/objects/01a0b604-…


#ibiswiki

嗨,各位关注 @board 的各位 Fedi 用户们大家好!好久不见呢

俺想简单谈谈关于 ibiswiki 该项目

大家或多或少都知道,在 #Fediverse 中、最著名的论坛社群就是 Lemmy 了,初始项目发起及其开发者是 Nutomic

Lemmy 一直以来也被称之为最好的 Reddit 替代品

最近俺了解到 Nutomic 很早推出了一个新项目,但似乎很少有讨论:Ibis - A federated online encyclopedia & 一个联邦在线百科全书

请注意:这不是介绍 #Fediverse 的 Wiki,Ibis 本质也是一个 #ActivityPub 实例

因此,Ibis Wiki 是可以让持有 #ActivityPub 账号的用户在当前的 Ibis Wiki 实例上编写或编辑当前 Wiki,也可以参与讨论

1/2


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: mitra.social/objects/01a091f1-…


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: mitra.social/objects/01a06eb0-…




Threads mit Lücken in Friendica


!Friendica Admins

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.


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: mitra.social/objects/01a06eb0-…


Nach mehreren Tagen Messung möchte ich unsere Untersuchung zum ungewöhnlich
anwachsenden PHP-FPM-Pool abschließen.

Der wichtigste Befund ist inzwischen recht eindeutig:
Von 196.466 ausgewerteten Slowlog-Ereignissen enthielten 195.069 einen
curl_exec()-Aufruf, also rund 99,3 Prozent.

Zusätzlich konnten wir einen betroffenen PHP-FPM-Prozess während eines realen
Ereignisses mit ss und strace beobachten. Dabei wartete der Prozess über viele Sekunden wiederholt in poll() auf Daten eines externen HTTPS-Sockets. Über ss ließsich derselbe File-Descriptor derselben PID eindeutig einer externen Verbindung zuordnen. Gleichzeitig bestanden mehrere weitere PHP-FPM-Verbindungen zu denselben wenigen Gegenstellen.

MariaDB und Redis antworteten im selben Zeitraum dagegen sehr schnell. Der Engpass
lag also nicht primär im lokalen System, sondern im Warten auf externe HTTP-
Kommunikation.

Nach der schrittweisen Anpassung der Wartezeiten und der FPM-Reserve hat sich das
Verhalten deutlich beruhigt. Auch der Load Average ist wieder auf ein normales Niveau
zurückgegangen. Die Zahl der Slowlog-Ereignisse fiel ab dem 4. September massiv ab.

Der Slowlog ist deshalb inzwischen wieder deaktiviert.

Mein persönliches Fazit aus der Untersuchung geht inzwischen über die konkrete
Friendica-Instanz hinaus:

Eine föderierte Instanz muss nicht nur selbst stabil laufen. Sie muss auch so mit
langsamen, fehlerhaften oder zeitweise unerreichbaren Gegenstellen umgehen können,
dass deren Zustand die eigene Funktionsfähigkeit möglichst wenig beeinflusst.

Ich habe die Ergebnisse deshalb noch einmal ausführlicher in einem Fachartikel
zusammengefasst:

Föderation braucht Fehlertoleranz an den Instanzgrenzen

Hier der vollständige Artikel

Dabei verzichte ich bewusst auf konkrete Grenzwerte oder eine allgemeine „Best-Practice-
Konfiguration“. Die Werte hängen zu stark von Instanzgröße, Nutzung, Federation-
Volumen und Systemumgebung ab. Entscheidend ist aus meiner Sicht nicht das Kopieren
einzelner Parameter, sondern das Verständnis der Zusammenhänge und die Messung auf
der eigenen Instanz.

#Friendica #Fediverse #Sysadmin #ActivityPub #Federation


Week in Fediverse 2026-09-04


Servers

- Ktistec v3.12.0
- Mastodon v4.7.1
- Vernissage v1.43.0
- snac v2.95
- ActivityPub for WordPress v9.3.0
- Owncast v0.3.0
- gathio v1.6.6
- NodeBB v4.15.2
- tootik v0.25.2
- NeoDB v0.18.0
- Bonfire v1.0.7

Clients

- PleromaFE v2.11.4
- Fedilab v3.43.3
- Tuba v0.11.1
- Pixelix v5.2.0
- Summit v1.85.0
- Shoot Web App v1.3.0

Tools and Plugins

- FediFetcher v8.2.0
- Poduptime v6.3.2
- Enable Mastodon Apps v1.6.3 (WordPress plugin)

For developers

- APx v0.27.0
- Library progress report - September 2026 (GoActivityPub)

Articles

- A reasonably practical guide to validating RFC 9421 HTTP Signatures for ActivityPub in PHP

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: mitra.social/objects/01a04a26-…


I've just published version 2.95 of #snac, the simple, minimalistic #ActivityPub instance server written in C. This is an important release, as it fixes an issue that can lead to denial of service attacks, so please update as soon as possible. It also includes the following changes:

Fixed a bug in the notification page that made snac hang forever while trying to read abnormally big files.

Improved support for text-only web browsers: it's now possible to configure a set of web browser user-agent strings that will receive simpler HTML in the private timeline web UI. Basically, it consists in avoiding details / summary HTML tags as much as possible.

Added some fixes to media proxy code.

Fixed EmojiReact code to allow any emoticon defined in emojis.json, not only those with colon-wrapped identifiers.

Fixed a bug in notification filtering (paging was sometimes incorrect).

Added a notification filter for Webmentions.

Mastodon API: Don't return reactions count as string (contributed by mkljczk), implemented GET /v1/media (contributed by clairemont).

Fixed bug in documentation examples (contributed by Sprite_tm).

Updated Ukrainian and Russian translations (contributed by wincentbalin and koru).

comam.es/what-is-snac

If you find #snac useful, please consider buying grunfink a coffee or contributing via LiberaPay.

#snacAnnounces #FrugalFediverse



#Fread 1.10.0 版本已经发布,以下是更新日志:

- 新增 AI 翻译
- Feeds 流支持加载缩略图
- 优化沉浸式浏览体验
- 优化 AI 设置
- 修复一些已知问题

#Mastodon #fediverse #Opensource
#RSS #FOSS #Freesoftware

github.com/0xZhangKe/Fread/rel…


The media in this post is not displayed to visitors. To view it, please go to the original post.

A video I tried to archive after the freedom of form foundation tried to erase some of the work from Atha (who was a compliance officer and was essentially given a unreasonable situation and was essentially kicked out) years ago got copyright striked by the fff recently

Any peer tube instances I can reupload this to
There's been more and more members leaving the fff recently as well as the fff leaves it's original purpose and enshitifies and becomes more corporate

Also boosting is appreciated

#fediverse #censorship #peertube #askfedi #vulpinelabs #freedomofform #transrights #science #preservation


9.3.0 — Modern Signatures and a Summer of Security Reports


The media in this post is not displayed to visitors. To view it, please go to the original post.

It has been almost three months since 9.0.0, and eight releases: 9.0.1, 9.0.2, 9.1.0, 9.2.0, 9.2.1, 9.2.2, 9.3.0, and now 9.3.1. Together they added seven new things, closed ten security issues, and fixed close to fifty bugs, which is a very different balance than usual.

This post covers the new things first, and then explains where the rest of the summer went.

Modern Signatures, On by Default


Every message your site sends to the Fediverse carries a signature, the digital equivalent of a wax seal on an envelope. In July 2025 we wrote about the move from the old draft format to RFC 9421, the official standard. Back then, sending with the new format was a setting for early adopters, and we promised to turn it on for everyone once the rest of the Fediverse was ready.

With 9.3.0 it is on by default. Your site now signs outgoing requests with RFC 9421, and falls back to the old format when the server on the other side does not understand it yet. For almost everyone this changes nothing you can see. Your posts keep arriving, your follows keep working.

A small number of servers advertise support for the new format but handle it differently in practice. If your posts suddenly stop arriving on one particular server after this update, you can switch back. Open the ActivityPub settings, click Screen Options in the top right, enable Advanced Settings, and turn off the modern signature format in the Advanced tab. Please let us know in the support forum which server it was, so we can look into it.

Your Podcast Travels With Its Audio


If you publish podcast episodes with Jetpack, your episodes now federate as episodes. The audio file and the cover art travel with the post, so your followers get a playable player in their Fediverse app instead of a link they have to click through.
A screenshot of a WordPress hosted Podcast Episode on Mastodon.
Version 9.1.0 did the same for Podlove Podcast Publisher, where the episode summary now goes out with the post rather than being dropped.

A Quieter Inbox


Likes, reposts, and quotes are lovely until there are two hundred of them and your email inbox has two hundred entries. Until now, switching those off meant switching off notifications for real comments and replies too.
Screenshot of the E-Mail Notification settings in WP-Admin.
9.3.0 separates them. There is a new notification setting that turns off emails about likes, reposts, and quotes, while comments and replies from the Fediverse keep reaching you. Reactions still show up on your post, you just stop hearing about each one individually.

Smaller Things You Might Notice


  • Fediverse and ActivityPub logos in the editor. On WordPress 7.1 and newer, both logos are part of the block editor’s icon library, so you can use them in a Social Icons block or anywhere else an icon fits.
  • The follow, reply, and reaction dialogs speak up. Screen readers now announce errors in those dialogs instead of leaving people guessing why nothing happened.
  • Scheduled posts show the right preview. Since 9.1.0, a scheduled post shows the Fediverse Preview, so you can see what your followers will get before it goes out.
  • Avatars that actually update. The scheduled refresh of remote profiles was not refreshing anything. Commenters kept the avatar and bio they had when they first showed up. Fixed in 9.1.0.
  • Two new FAQ guides, added in 9.0.1, for the two questions we get most often: follow requests stuck on “pending”, and comments from the Fediverse not appearing on your posts.


For People Building on the Plugin


9.1.0 added an actor autocomplete endpoint, so a Fediverse app connected to your site can offer typeahead search when you are mentioning someone. There is also a new filter for sites that need to federate inside a private or internal network, which mostly matters for intranets and staging setups.

In 9.3.0, apps connected through the ActivityPub API now use the standard permission names from the specification, and fetching remote content through your site counts as reading rather than posting. Apps also see the real error when a post is missing, instead of a generic failure that told them nothing.

Where the Summer Went


Seven new things in three months is not much. Here is the reason.

Since June we have had a steady stream of security reports. Ten of them became entries in the changelogs of 9.1.0 and 9.3.0, and a few more landed quietly as fixes. Every report has to be read, reproduced, judged, fixed, tested, and shipped, and the fix has to be written so it does not break the sites that already work. For a team our size that is most of a week each time, sometimes more.

This is not a complaint, and a real thank you to everyone who sent a report and then waited while we worked through the queue. Nearly all of the reports were real, and every one of them made the plugin safer for the people running it. This is responsible disclosure working the way it should. It just means the roadmap moves slower than it looks on paper, and features that were planned for July are still open.

We are not alone in this. WordPress core is seeing the same wave, and for the same reason: AI models have become good enough at reading code that finding a plausible vulnerability is now cheap. The security team wrote about it in The Core Security Initiative, and the project started Protect The Shire to review the code in the plugin and theme directories at a scale that was not possible before. The same tools that raise the number of reports also help everyone work through them. On balance, we think this is good for the ecosystem, even on the weeks where it does not feel like it.

In general terms, the security work in these releases covers four areas:

  • Content from other servers is cleaned before it is stored, and again before it is displayed, so what another server sends cannot influence how your site behaves.
  • Data that belongs to you stays yours. Your followers, the profiles your site has cached, and your reader posts are not readable by logged-out visitors, and the setting that hides your follower list is respected everywhere.
  • Activities are checked more strictly against the account they claim to come from, so a server cannot act on behalf of someone else.
  • Apps you connect can only do what you allowed them to do, and nothing wider.

We are keeping this vague on purpose. The details are in the reports, and we would rather not hand a recipe to anyone whose site has not updated yet. If you run the plugin, please update.

What the Fixes Cover


The fifty or so fixes across these releases are not one story, but they fall into a few groups:

  • Finding each other. Profiles and posts were not always found when an address contained unusual characters, or was written with different capitalisation, or when the other server answered in an unexpected shape. Several fixes make lookups work in all of those cases.
  • Reactions arriving once. Likes and boosts could be recorded as duplicate comments, or come back after you marked them as spam. A deletion on Mastodon did not always remove the matching comment on your site. Both are fixed.
  • Caching. ActivityPub responses were sometimes stored by page caches meant for regular web pages. Since 9.2.0, those responses are served only to clients that ask for ActivityPub data and nothing else, which keeps them out of caches like LiteSpeed and Surge. Support for the WP REST Cache plugin was removed as part of this.
  • Publishing edge cases. Posts scheduled for a future date were removed from the Fediverse when edited. Hidden page elements, like the text inside a closed dialog, ended up in the content sent to your followers. Backslashes vanished from imported titles. Small things, annoying every time.
  • Living with other plugins. Fixes for sites running Polylang, Jetpack, Surge, and the Mastodon importer, which was creating duplicate posts when an archive was imported twice.
  • Admin screens and the editor. Styles that failed to load on the Fediverse screens and in the Followers and Following blocks, an editor warning about unsaved changes that appeared right after saving, and a handful of errors that filled up log files without breaking anything visible.

The full, item-by-item changelog for every release is in the plugin’s changelog if you want to read it in detail.

Get It


Download from WordPress.org or grab it on GitHub. If your site updates automatically, you already have it.

Thanks to everyone who filed a bug report with steps we could follow. Those are the ones that get fixed fastest.

Now that signatures are modern by default: does anything still deliver differently for you? And what would you like to see us build once the queue is shorter?


Hello !Friendica Support

Does anyone know what exactly happens when changing an existing Friendica instance from "Single user instance" to "Multi user instance"?

Is this basically just enabling registration/additional local accounts, or are there any other behavioural changes or side effects I should be aware of?

The instance has been running as a single-user instance for quite some time, so I'm particularly interested in whether switching an existing installation is completely safe and reversible.

#Friendica #Fediverse #SelfHosting


Week in Fediverse 2026-08-28


Servers

- Hollo v0.9.13
- gush! v0.0.41
- tootik v0.25.0
- Mitra v5.10.0
- Pixelfed v0.12.9
- Hollo v0.9.15
- Funkwhale v2.0.10
- PieFed v1.7.13
- tootik v0.25.1
- NeoDB v0.17.8

Clients

- Pachli v3.8.1
- Fedilab v3.43.2
- RaccoonForFriendica v1.1.0

For developers

- Fedify v2.3.6

Protocol

- FEP-49eb: Batched Inbox Delivery

Articles

- A crawler wanted to know who talks to whom on our server
- The Problems and Successes of Fediverse Comments on my blog
- The Fediverse is Throwing a Music Festival

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: mitra.social/objects/01a0269e-…


#Mastodon is the powerful war rig in the #Fediverse army against the axis of biased social networks; #snac is the little buffoon back there in the rearguard, playing their old-fashioned lute and making silly jokes.

#CrazyFediverseAnalogies


Week in Fediverse 2026-08-21


Servers

- Funkwhale v2.0.8
- PieFed v1.7.11
- TinyAP v0.1.13
- Wafrn v2026.08.04
- Mastodon v4.7.0
- gathio v1.6.5
- NeoDB v0.17.7
- NodeBB v4.15.1
- Flox v2.7.0
- 5.0: Laying the foundation (Mastodon)

Clients

- PleromaFE v2.11.3
- chan-fe v0.3.0
- Tuba v0.11.0
- Mangane v1.24.3
- Mastodon for iOS v2026.07
- Miria v4.0.0+125
- Summit v1.84.0
- Voyager v2.48.5
- Pixelix v5.1.1

Tools and Plugins

- Pluraldawn: Decodes indicator emoji information from account avatars to provide a PluralKit-esque experience inside of various fediverse webapps

Protocol

- ActivityPub Miscellaneous Terms

Articles

- Implementing Pagination for ActivityPub Collections
- Owncast Newsletter August 2026

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: mitra.social/objects/01a001c8-…


!Friendica Admins
📢 Einladung zum 6. Friendica-Admin-Treffen

📅 Montag, 24.08.2026
🕢 19:30 Uhr (MESZ)

Hallo zusammen,

am kommenden Montag ist es wieder soweit: Wir laden herzlich zum 6. Friendica-Admin-Treffen ein.

Eingeladen sind alle Friendica-Admins, Instanzbetreiber, Entwickler:innen sowie alle, die sich für den Betrieb und die Weiterentwicklung von Friendica interessieren.

🔹 Ein mögliches Thema für den Abend:
Mit Friendica 2026.08-rc ist der Release Candidate der kommenden Version veröffentlicht worden. Eine gute Gelegenheit, gemeinsam einen Blick darauf zu werfen:

Was gibt es Neues? Gibt es bereits erste Erfahrungen mit dem RC? Welche Änderungen sind besonders für Administratoren interessant? Und vielleicht können wir auch einen vorsichtigen Blick darauf werfen, wie der weitere Weg bis zur nächsten stabilen Friendica-Version aussieht.

Dabei geht es natürlich nicht darum, einen Veröffentlichungstermin einzufordern – schließlich gilt auch bei Friendica: Es ist fertig, wenn es fertig ist. 😉

💬 Weitere Themen und Fragen sind ausdrücklich willkommen!

Bringt gerne eure Erfahrungen, Ideen, Fragen oder aktuelle Herausforderungen aus dem Alltag als Friendica-Admin mit. Oft entstehen gerade aus dem offenen Austausch die interessantesten Gespräche.

Wir freuen uns auf einen informativen und gemütlichen Abend mit euch und auf einen regen Austausch rund um Friendica. 🌐

💻 Online-Konferenzraum

Gerne weitersagen und auch andere Friendica-Admins und Entwickler:innen auf das Treffen aufmerksam machen.

#Friendica #Fediverse #FriendicaAdmin #AdminTreffen #OpenSource


The media in this post is not displayed to visitors. To view it, please go to the original post.

Frage | Friendica: Wie gut funktioniert das mit der Federation?


Guten Morgen Zusammen :-) Ich habe mal eine Frage betreffs Federation. Und zwar habe ich gesehen das ich in Sachen Beiträge vor allen via Lemmy Feedback bekomme, aber in den allermeisten Fällen kaum aus dem Rest des Fediverse. Dabei ist mir klar das ich wenn ich in eine Lemmy Community poste, ich recht viele Leute erreiche. Aber das erklärt eben nicht warum aus dem Rest des Fediverse wo ich sehr viel mehr Kontakte habe die mir folgen so wenig zurück bekomme.

Ist Euch ähnliches aufgefallen?

#Frage #Friendica #Federation #Feedback #Fediverse #Lemmy !Friendica Support


The media in this post is not displayed to visitors. To view it, please go to the original post.

I’ve updated the Dystronix Pixelfed icon.

The new gradient icon helps distinguish Dystronix on Pixelfed from dystronix.com. #fediverse #photography #streetphotography


Week in Fediverse 2026-08-14


Servers

- Akkoma v2026.08
- WriteFreely v0.17.2
- Wafrn v2026.08.03
- Mitra v5.9.0
- Ktistec v3.11.0
- Hollo v0.9.11
- Mastodon v4.6.6
- Forte v26.8.11
- gathio v1.6.4
- ActivityPub for WordPress v9.2.2
- NeoDB v0.17.6
- NodeBB v4.15.0
- Trunk & Tidbits, July 2026 (Mastodon)

Clients

- Aria v1.5.11
- Snowdrop: Multiplatform client for Mastodon API compatable Fediverse software

Tools and Plugins

- FediFetcher v9.1.1

For developers

- Fedipub v0.9.0
- Library progress report - August 2026 (GoActivityPub)

Protocol

- FEP-e4de: Closing Registration on Unattended Servers
- FEP-633c: Guardians

Articles

- Deploying your own Vernissage instance

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: mitra.social/objects/019fde3b-…


The media in this post is not displayed to visitors. To view it, please go to the original post.

For: Linux distro developers
Subject: Switched my Linux distro to XLibre

This is a copy of a post that I made just now in the Github issues section for XLibre. Link to the original post:
github.com/orgs/X11Libre/discu…

I've been developing a Linux distro, #Laclin, for 30 years. In the past 24 hours, I've switched, for now, from the old #Xorg framework to #XLibre. This includes, so far, xserver and some of the video drivers. I'll comment below on the rest.

This is my desktop running on XLibre:
260813-laclin-desktop

The desktop is original. The parts add up to only a few MB. I like light and stable. I'm not a fan of sumo-wrestler size layers that gobble up GB of RAM and drag performance down to Windows level.

I'm also the type that holds up a cross and recites "Get thee behind me, Satan" when I see systemd and Wayland. No offense to fans of systemd and Wayland is intended. But I don't plan to switch to either. So, XLibre is a positive development.

I've had no "build" or runtime issues with XLibre xserver so far. I needed to switch some of the video drivers to the XLibre forks in order to get them to build. I'd switch other components as well, but here's the thing:

Did I mention that I have 30 years of work invested in the distro? I don't want to break 2,000 packages.

The distro includes legacy packages, some of which no other distro has. The code goes back as far as the 1990s. [The 1970s to 1980s, in a few cases.] If XLibre drops ".pc" or ".la" files [as I gather it did in one case] the packages won't build. [Yes, I understand that that change was reverted.]

So, I have four requests:

  1. Keep up the good work. The fork needs to continue or the distros that are switching will be between a rock and a hard place.
  2. Prioritize backwards compatibility to the extent that old packages can be built in the new framework.
  3. Use of systemd should be optional.
  4. Set up a #Fediverse account and post there. LibreOffice, The GIMP, G'MIC, Project Gutenberg, Internet Archive, Dillo, LibreWolf, and many other projects do. It's a FOSS friendly environment.

The desktop in the screenshot is based on jwm with features added using lightweight scripts. It's got Start button, Boss button, taskbar, workspaces, systray, launch buttons, and dockapps. Plus Alt-Tab and single-instance support. I figure that that is most of what is needed.

It runs fine so far in XLibre. I'm not going to port 30 years of work to a new framework [Wayland] that intentionally breaks things and that isn't going to support old software or hardware.


I’ve been thinking about how the internet shapes polarization.After gathering on massive social platforms, many people now seem to be looking for smaller places that feel like their own.A huge public square where opposing views constantly collide can easily create conflict.Maybe the Fediverse is still underestimated—not just because it’s decentralized, but because it lets us stay connected while keeping some distance.We don’t all have to live in the same square to share the same world
#fediverse


⇧