taquiones.net 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.
Week in Fediverse 2026-01-09
Servers
- Wafrn v2026.01.02
- snac v2.86
- Ktistec v3.2.7
- Mitra v4.16.1
- Mastodon v4.5.4
- Bookwyrm v0.8.3
- PieFed v1.4.5
- shops v0.2.0
- Cross-posting is coming to NodeBB!
- Lemmy Development Update December 2025
Clients
- IceCubesApp v2.12.2
- tooi v0.17.0
- Thunder v0.8.4
- NeoDB You v1.0.6
- Phanpy changelog
Tools and Plugins
Articles
- Mandy: ActivityPub on Goblins
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019b800a-060c-a6fc-6a7a-4c9bef0d6ea9
ChatGPT mostly reflects what's already out there, the internet, Reddit, different communities.
Which means chatting with it is a bit like chatting with what the world currently thinks, bias and vice, trolls included, but also real discussions.
So, I asked it about the Fediverse. I would say that it sounds not too "wrong".
What's your take?
This is the convo:
The beauty of #ActivityPub
Yes, Loops federates, and admins can enable any remote instance video posts to appear in local follower feeds AND you can even include them in the For You page ✨
just came across the Protocols for Publishers event happening in London on February 4th & 5th directly after FOSDEM featuring @laurenshof, @ben, @saskia, and @aendra.com (as announced speakers so far)
https://protocolsforpublishers.com/london-2026 #ActivityPub #ATProto
Hide EmojiReacts from muted actors and blocked instances.
Sorry for the inconvenience. Bad people creativity always gets me off-guard. Upgrade your snac to this version ASAP, or revert to 2.85.
There will be another release pretty soon with a better solution to delete offending EmojiReacts.
Fediverse account backups via 3rd party FOSS service
Personal Archive Node (PAN) is quite brilliant, its compatible with most fediverse software already, and uses a dual strategy for data backup, with one being adaptable to most fediverse software via adapters.
While not exactly ideal, PAN solves the issue of unforseen instance shutdowns in a short term fashion, while paving the way for a long term, more efficient solution ✨
More details soon.
tl;dr — cross-posting is coming to NodeBB in v4.9.0. It will be internal-only for now, as we work through social issues with federated cross-posting. Existing category sync and auto-categorization logic in NodeBB now utilises cross-posts instead of moving or ignoring categorized topics, respectively.
Some history
For the past couple months, I've been mulling over the idea of cross-posting, and how this would work in a federated forum context. Specifically, I had begun to think more critically about how NodeBB presented itself in the threadiverse (threaded fediverse), and whether what we were doing currently was the right approach.
Somewhere in the v4.1.x releases, NodeBB began supporting a new feature called "category synchronization". It allowed categories to follow other categories, and would move topics from those other categories into a local category. If done in reverse, the both categories could be considered "synchronized", meaning that users on both instances could see, like, and comment on the same topics.
As of v4.3.x, NodeBB gained the ability to actually "see" remote categories. You'd be able to browse to a local representation of something like @fediverse@piefed.social or @comicstrips@lemmy.world and see the posts in those categories as though you were on that site itself. It was a huge jump in how NodeBB treated threadiverse content.
After that point, it became a little weird that category sychronization would move topics from one category to another, because the topic really didn't lose its existing categorization, we simply stole it! When I introduced auto-categorization rules in v4.5.0, I was cognizant of this discrepancy, and avoided complication by ignoring already-categorized topics.
What is cross-posting?
In a nutshell, cross-posting is the ability for a single topic/reply-tree to exist in multiple places simultaneously. Comment trees are shared and accessible from both of those places, and this avoids unnecessary duplication of content across multiple communities.
We see manual cross-posting happening often on the fediverse already, and collapsing these identical items into a single entity would be a boost to discussion as it eliminates the artificial fracturing of comments across multiple disparate posts.
Importantly, v4.9.0 will introduce cross-posting locally only. It means that topics from outside the forum can be cross-posted to an local category, but local topics cannot be cross-posted to remote categories. This is the eventual plan, but we are not there yet! See below ("Why don't cross-posts federate?") for more details.
Cross-posting essentials
Topics will have a new button in the sidebar (or top bar, in the Persona theme) that allows you to cross-post topics to another category. In this dialog, you will be able to choose one or more categories to cross-post the topic to.

Admittedly, there's not a whole lot of utility in cross-posting local topics to another local category, but it really shines when you crosspost remote topics to a local category.
When a cross-post appears in a local category, a link back to the original category is shown.

Anyone can cross-post a topic to a local category, but only mods and administrators can remove others' cross-posts.
What of category synchronization and auto-categorization?
The existing features will be updated as follows:
Why don't cross-posts federate?
I want to roll out a first-pass at cross-posting as there are immediate benefits for forums and their local categories. Being able to pull in content from other remote categories while respecting their categorization will allow for more increased cross-community engagement and expose remote communities to people who would have otherwise not discovered them.
At the same time, we want to move slowly because there are wide-ranging effects that federated cross-posting could bring about. Namely, if anybody is able to cross-post anything anywhere, then it would enable brigading because different communities with (sometimes very) different values would suddenly co-exist in the same space, leading to some very negative interactions.
Additional questions exist, such as:
I certainly don't have all the answers as to how to best approach it, but it is something we at the @forum-wg would love to tackle at some point.
What's next?
Other threadiverse software (Lemmy, Piefed, mbin) don't handle cross-posting, and there are no immediate plans to support it. Piefed does have something similar (called "Topics", akin to Reddit multi-reddits) which can contain posts from multiple communities. Both Lemmy and Piefed attempt to automatically collapse comment trees when identical links are discovered. Moving forward we may want to coalesce toward a single desired behaviour, but whether cross-posting is it, is to be determined.
Additionally, NodeBB doesn't have the concept of "boosting" (also known as resharing, reblogging, etc.) It does do something similar when topics are moved between categories, and so it would make sense that a cross-post would be the forum equivalent of a reshare.
Cross-posting is currently being tested on activitypub.space, and should be generally available as of NodeBB v4.9.0.
Truncate RSS titles at UTF-8 character boundaries (contributed by lxo).
Link contacts to single-user people pages. Also, user's posts are shown (contributed by lxo).
Added emoji reactions (contributed by violette).
Mastodon API: Fix for some client notifications (contributed by violette), fix for a status visibility error (contributed by fruye).
If the query variable terse of a public post page is set to anything, no header is shown.
Fixed search failures when the query string has any leading blank.
If you find #snac useful, please consider buying grunfink a coffee or contributing via LiberaPay.
Week in Fediverse 2026-01-02
Servers
- Vernissage Server v1.27.0
- Ktistec v3.2.6
- Pleroma v2.10.0
- Wafrn v2026.01.01
- NeoDB v0.12.7
- PieFed v1.4.1
- shops v0.1.9
- Loops v1.0.0-beta.7
- Mitra v4.16.0
- Agora: A distributed knowledge graph
- December 2025: hooo boy! (Bandwagon)
Clients
- Pachli v3.3.0
- IceCubesApp v2.1.1
- Loops Mobile App v1.0.1.19
- Voyager v2.43.1
- P2Play v0.10.0
- tooi: A text-based user interface for Mastodon, Pleroma and friends
Tools and Plugins
- Mastodon to Bluesky v1.5.0
- Altbot v2.5
For developers
- funfedi.dev schemas v0.1.0
- apsig v0.6.0
- apkit v0.3.7
Articles
- A case for organisations running their own ActivityPub servers
- Fediverse predictions
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019b5b98-13e5-ff26-3605-f31d929bf9bf
RE: https://badges.vocalcat.com/grant/badgesvocalcatcom_133_5_2f1bbe7477c80c1ff0100c86c31c0289
You can now quote badges from @badgefed !
Preparing for #fosdem demo.
Thanks to @Mastodon for the FEP-044f! It was easy to implement.
#activitypub #fediverse #mastodon
https://codeberg.org/fediverse/fep/src/branch/main/fep/044f/fep-044f.md
(duplicated)
I've been experimenting with lightweight activitypub tools like gotosocial and snac2.
So far snac2 works, but seems incompatible with basically every frontend I've tried.
gotosocial is more compatible, but crashes randomly and won't stay online for 24hrs at a time.
What am I doing wrong here?
Anyone have any tips?
Quoted posts are now shown.
Added metadata to remote users in the people page (contributed by dandelions).
Fixed memory leak (contributed by dandelions).
Fixed user matching (contributed by rakoo).
Rendering visibility conditionally, with lesser reach if needed (contributed by byte).
Added a button next to a follow notification to follow back.
Fixed typo in man page (contributed by spky).
Updated Czech and German translations (contributed by pmjv and zen).
If you find #snac useful, please consider buying grunfink a coffee or contributing via LiberaPay.
RE: https://colours.bots.edent.tel/posts/68d87379-8e35-18be-b901-2730376a090d.json
Ok, I need some #ActivityPub help, please.
The reply to this will have links to the QuoteRequest the bot received, the QuoteAuthorization which it saves, and the Accept message it returns.
Can anyone figure out why the Quote permissions aren't showing on external servers?
Added support for scheduled posts (for this to work correctly, users will have to set their time zone, see below).
The user can now select a working time zone. This will be used to correctly parse the local date and time of a scheduled post.
Fixed incorrect poll vote format, which was causing problems in platforms like GotoSocial.
Mastodon API: added support for /api/v1/instance/peers.
Added a new snac-admin helper script (contributed by shtrophic).
In the web UI, posts are separated by the <hr hidden> tag; it's invisible in graphical browsers, but it separates post clearly in text-based browsers.
Some Finnish, Spanish, Czech and Russian translation updates and fixes.
If you find #snac useful, please consider buying grunfink a coffee or contributing via LiberaPay.
This release has been inspired by the song Pictures on the Wall by #MichelleGurevich.
You, people, are GREAT. Thank you very much.
De la mano del muchache creador de #snac, y su inagotable optimismo con el amor y la vida, nos llega ahora una instancia #activitypub para saber si llega o no llega el meteorito de las narices.
Week in Fediverse 2025-01-31
Servers
- Manyfold v0.99.0
- Misskey v2025.1.0
- snac v2.70
- Hollo v0.4.5
- Gancio v1.23.0
- NeoDB v0.11.4.3
- forgejo-contrib/federation: The place to organize development around federation for Forgejo
Clients
- Elk v0.16.0
- Pachli v2.9.2
- Dhaaga v0.14.1
- Alexandrite v0.8.18
- Pixelix v3.3.0
- PeerTube Mobile v0.6.0
Tools and Plugins
Protocol
- FEP-2277: ActivityPub core types
Articles
- Improving Snac Performance With Nginx Proxy Cache
- Fediverse Report #101
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019499d8-2a50-b1df-6908-393384df7e2d
Added support for subscribing to LitePub (Pleroma-style) Fediverse Relays like e.g. https://fedi-relay.gyptazy.com to improve federation. See snac(8) (the Administrator Manual) for more information on how to use this feature.
Added support for following hashtags. This is only useful if your instance is subscribed to relays (see above).
Added support for a Mastodon-like /authorize_interaction webpoint entry, that allows following, liking and boosting from another account's Mastodon public web interface. To be able to use it, you must reconfigure your https proxy to redirect /authorize_interaction to snac (see snac(8)).
Some fixes to accept Event objects properly (like those coming from implementations like https://gancio.org/ or https://mobilizon.fr).
Added some caching for local Actor objects.
Hashtags that are not explicitly linked in a post's content are shown below it.
Fixed broken NetBSD build (missing dependency in Makefile.NetBSD).
The user profile can now include longitude and latitude data for your current location.
Mastodon API: implemented limit= on notification fetches (contributed by nowster), implemented faster min_id handling (contributed by nowster), obey the quiet public visibility set for posts, other timeline improvements (contributed by nowster).
Reduced RSA key size for new users from 4096 to 2048. This will be friendlier to smaller machines, and everybody else out there is using 2048.
If the SNAC_BASEDIR environment variable is defined and set to the base directory of your installation, you don't have to include the base directory in the command line.
Fixed a bug in the generation of the top page (contributed by an-im-dugud).
Added support for Markdown headers and underlining (contributed by an-im-dugud).
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
This release has been inspired by the song Nine Hundred Miles by #BarbaraDane.
Fixed regression in link verification code (contributed by nowster).
Added ipv6 support for the https frontend connection (contributed by hb9hnt).
New "Like by URL" operation (contributed by dheadshot).
Added support for a Mastodon-like /share link sharing URL, like the one provided by sites like https://mastodonshare.com/ and such. To be able to use it, you must reconfigure your https proxy to redirect /share to snac (see snac(8)).
New linux landlock (sandboxing) support for enhanced security (contributed by shtrophic). It's still a bit experimental, so you have to enable it explicitly by recompiling with the WITH_LINUX_SANDBOX directive (e.g. make CFLAGS=-DWITH_LINUX_SANDBOX).
Some search fixes regarding repeated matches.
The export_csv cmdline operation now exports the CSV files inside a user's export/ subdirectory instead of the current directory.
All CSV files to be imported must now be stored inside a user's import/ subdirectory instead of the current directory.
Mastodon API: more timeline paging tunings (contributed by nowster), post language selected in apps is properly set.
The command-line operation note new reads the LANG environment variable to set the post's language.
A new command-line operation, note_unlisted, allows posting "unlisted" or "quiet public" posts.
The maximum number of entries in users' RSS feeds and in outboxes can now be set via the max_public_entries variable in the server.json file.
Fixed broken support for Audio objects.
Made xmpp and mailto URLs clickable.
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
This release has been inspired by the painting Judith Slaying Holofernes by #ArtemisiaGentileschi.
Added a new user option to disable automatic follow confirmations (follow requests must be manually approved from the people page).
The search box also searches for accounts (via webfinger).
New command-line action import_list, to import a Mastodon list in CSV format (so that Mastodon Follow Packs can be directly used).
New command-line action import_block_list, to import a Mastodon list of accounts to be blocked in CSV format.
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
The server can now act as a proxy for all image, audio or video media coming from other account's posts (both from the Web UI and the Mastodon API). This way, other servers will see media requests coming from the server IP, not the user's, improving privacy. This is controlled by setting the proxy_media boolean field to server.json to true.
The strict_public_timelines option introduced in the previous release now works correctly.
Fixed a crash when posting from the links browser.
Fixed some repeated images from Lemmy posts.
Fixed a crash when posting an image from the tooot mobile app.
Updated FreeBSD rc script: the server process is now managed by the daemon(8) utility (contributed by @stefano@bsd.cafe).
RSS feeds are now in 2.0 version instead of 0.91.
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/donate
This release has been inspired by the song New Moon (Dark Phase) by #DuranDuran.
Migration from a Mastodon account to a snac one has been implemented. Please see snac(8) (the administrator manual) for more information.
Mastodon API: fixed timelines/public (it was showing less posts that it should).
Fixed over-zealous caching to the public timeline.
Some HTML tweaks and fixes to the web interface.
If you find #snac useful, please consider buying grunfink a coffee: https://ko-fi.com/grunfink
This release has been inspired by the painting The Hands Resist Him by #BillStoneham.
Support for custom Emojis has been added; they are no longer hardcoded, but read from the emojis.json file at the server base directory. Also, they are no longer limited to string substitutions, but images as external URLs are also supported (see snac(8) for more information).
Fixed a bug that caused some notifications to be lost when coming from a user in the same instance.
Added an additional check for blocked instances (sometimes, posts from blocked sites that were ancestors of legit posts were 'leaking' into the timeline).
On OpenBSD, if the disable_email_notifications server flag is set to true, unveil() is not called for the execution of the /usr/sbin/sendmail binary and pledge() doesn't set the exec promise.
If you find #snac useful, please consider buying grunfink a coffee: https://ko-fi.com/grunfink
This release has been inspired by the album Eternal Embers by #Meltt.
Part 3 of "A Guide to Implementing ActivityPub in a Static Site (or Any Website)" is just out the oven!
In this blog post, I explain how to make your blog discoverable in the Fediverse as an account, and also address some of the annoying pitfalls I encountered.
Full article here: https://maho.dev/2024/02/a-guide-to-implementing-activitypub-in-a-static-site-or-any-website-part-3/
If you like it don't forget to follow the @blog !
#fediverse #activitypub #static-sites #hugo #azure #mastodon #web-development #social-web #webfinger #http