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.
PRs must not incorporate any material generated by or with the assistance of any so-called "generative AI" tool or LLM.
Hey #ActivityPub friends. Are there any new ActivityPub / Mastodon features I should add to #ActivityBot?
It's a small bot-only ActivityPub server in a single PHP file.
https://gitlab.com/edent/activity-bot/
It can be followed, post images, allow quote posts, etc.
Is there anything else you would like a bot-server to be able to do?
Correction: I can't tell 5 from 6. FOSSY 2026 in same venue as FediCon 2025.
😲…I realized #FediCon is in *same* venue as #FOSSY!
I hope #Fediverse folks going to event will be able stay in Vancouver for FOSSY!
Also, I suspect #SFC would welcome a Fediverse track at FOSSY…
https://sfconservancy.org/fossy/community-tracks/
…maybe as a B-sides event for overflow talks?
¿Sabían que Lemmy, la plataforma de agregación de noticias y foros del Fediverso, fue lanzada originalmente en febrero de 2019 como una alternativa descentralizada y de código abierto a Reddit?
Desarrollada por Dessalines y Nutmic, esta herramienta utiliza el protocolo ActivityPub, lo que permite que diferentes instancias de Lemmy interactúen entre sí y con otros servicios como Mastodon o Friendica. A diferencia de las plataformas centralizadas, Lemmy permite que cualquier usuario con los conocimientos técnicos necesarios aloje su propio servidor, manteniendo el control total sobre los datos, las políticas de moderación y la administración de la comunidad sin depender de una estructura corporativa única.
El crecimiento exponencial de la red ocurrió a mediados de 2023, tras los cambios en la política de precios de la API de Reddit, lo que provocó una migración masiva de usuarios hacia el Fediverso. Técnicamente, Lemmy está escrito en el lenguaje de programación Rust para el servidor y utiliza el framework Actix, mientras que el front-end está desarrollado en Typescript con Inferno. Esta arquitectura permite un manejo eficiente de recursos y una alta velocidad de respuesta en comparación con otras plataformas de microblogueo. Actualmente, la red cuenta con miles de comunidades activas organizadas por temáticas que van desde el software libre hasta la fotografía, consolidándose como el principal nodo de foros federados a nivel global.
#Lemmy #Fediverso #ActivityPub #SoftwareLibre #Tecnología #Descentralización
I've written a fully complete #ActivityPub server in 64KB. What's the smallest *entirely self-hosted* PDS for #ATProto? gitlab.com/edent/activi...
With ActivityPub / ActivityStreams...
To me, it feels like there should have been something that is a common parent of both 'Object' and 'Link'.
That just had the "name", "nameMap", and "preview" fields (along with "id" and "type, of course) — since that is what 'Object' and 'Link' share in common.
I'll just call this common parent: 'Entity'.
...
It could have even been an opportunity to talk about how to handle unknown types.
Week in Fediverse 2026-03-06
Servers
- Hollo v0.7.5
- Lemmy v0.19.16
- Ktistec v3.3.2
- Stegodon v1.8.1
- GoToSocial v0.21.1
- ActivityPub for WordPress v8.0.0
- gathio v1.6.2
- Misskey v2026.3.0
- Castopod v1.15.5
- flohmarkt v0.16.1
- NodeBB v4.9.1
- PieFed v1.6.9
- Lemmy Development Update February 2026
- FediProfile: A linktree for the fediverse - ActivityPub enabled profiles
Clients
- Sengi v1.9.0
- Summit v1.79.1
- Blorp v1.10.8
Tools and Plugins
- Poduptime v6.3.0
- share.joinmastodon.org: Share widget for Mastodon
Protocol
- FEP-82f6: Actor statuses (Final comments)
Articles
- Gotosocial Reverse Proxy With Wireguard
- FR#156 – Share Where?
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019ca0a0-4fce-c180-89e4-071244c530a4
Para hacerlo entendible #activityPub es un protocolo que usa peticiones HTTP basada en un formato concreto que luego en tu aplicativo adaptas a tu conveniencia (teniendo en cuenta si recibes o mandas, inbox u outbox).
Por si queréis hacer aplicativos compatibles con el protocolo ActivityPub y os molara hacer algo federado. Hay como unas acciones sociales concretitas que se le puede dar uso para la interoperabilidad.
Acabo de enterarme de que en @nextcloud están implementando una red social compatible con #ActivityPub, por lo que si tienes un servidor Nextcloud, todos tus datos quedarían allí. Y si es autoalojado, tienes de hecho una instancia autoalojada del fediverso.
RE: https://social.growyourown.services/@homegrown/116155421471110983
Existe un nuevo proyecto llamado #Holos que brinda la facilidad de tener tu propio servidor del #Fediverso en tu dispositivo móvil. Puedes seguir el proyecto en:
➡️ @HolosSocial
La web oficial explica cómo funciona:
➡️ https://holos.social/how-it-works
Para calmar expectativas, aún está en sus etapas iniciales y orientado a personas con conocimientos técnicos por ahora. Sin embargo, será interesante seguir su evolución 🙂
Holos es creado por los desarrolladores de la aplicación móvil para Mastodon/Fediverso #Fedilab.
Complete this sentence:
"I experience #fediverse as a .."
#Poll #AskFedi #Microblogging #Mastodon #ActivityPub
| Bustling city: | 32 |
| Cozy village: | 130 |
| Ghost town: | 7 |
| Other (please comment): | 15 |
@silverpill @raphael @julian @mariusor
I sometimes picture fediverse as one of these old horseracing toys from the 50s, where the horses represent all the various perspectives and expectations people have of the fediverse. There is no horse to bet on, positions change all the time, horses change tracks randomly. And furthermore there no finish line, the race is an endless slog. The prize of a robust #ActivityPub protocol forever out of reach, getting more elusive as time progresses.
@fox @silverpill @raphael @julian @mariusor
Yes. I tooted about the need for Grassroots open standards and Grassroots standardization this morning..
https://social.coop/@smallcircles/116147786851664068
In a decentralized grassroots movement, somewhere there needs to an aggregation of the solution artifact. In this case a robust, comprehensible #ActivityPub standard that can be readily implemented in libraries, frameworks and SDK's upon which then subsequently #SocialNetworking solution design can take place.
This is not centralization, this artifact can be federated. But there must be a place of convergence where consensus on protocol design comes together.
There might be a crowdsourced ActivityPub 2.0 specs + documentation site, plus a process around it to make it work.
Week in Fediverse 2026-02-27
Servers
- Bookwyrm v0.8.5
- Gush! v0.0.31
- Hollo v0.7.4
- flohmarkt v0.16.0
- Mastodon v4.5.7
- Wafrn v2026.02.02
- GoToSocial v0.21.0
- Loops v1.0.0-beta.10
- Ktistec v3.3.1
- Mitra v4.19.0
- Stegodon v1.8.0
- Hometown v1.2.0
- gathio v1.6.1
- Castopod v1.15.5
- NodeBB v4.9.0
- PieFed v1.6.7
Clients
- Pachli v3.4.0
- tooi v0.22.0
- Summit v1.78.1
- Photon v2.3.0
- Blorp v1.10.3
- Phanpy changelog
Tools and Plugins
- Poduptime v6.2.1
- Fediverse invitation
For developers
Protocol
- FEP-a427: Server Domain Migration
- FEP-fc48: Generic ActivityPub server
Articles
- Self-Hosting Pixelfed: Federated Instagram Without the Algorithm
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019c7c6f-742a-7930-2413-73b1d9611c99
I’m building a new tool and looking for volunteers to test it! A #fediverse linktree. (UPDATE: https://hub.vocalcat.com )
It’s designed for two types of people:
Normies / newcomers – Think of it like a free, privacy-respecting Linktree. No trackers, no ads. But here's the cool part: it's a Trojan horse for the fediverse. Your profile link is itself an ActivityPub actor. That means people can interact with it directly in the fediverse, and it encourages exploration of open platforms.
Fediverse users, If you have multiple accounts (#Mastodon, #Pixelfed, Loops, a federated blog…), you know the struggle: sometimes you just want one persona to follow. This tool gives you that. It doesn’t post on its own (read-only), but it boosts all your other accounts and even has its own #ActivityPub inbox. PLUS it can receive and show your badges issued by @badgefed !
Interested in testing? Right now it only supports mastodon authentication, so if you have a mastodon account reach out in private mention for the invitation code.
¿Sabían que Write.as no es solo una plataforma de blogs minimalista, sino uno de los pilares de la publicación larga dentro del Fediverso gracias a su integración nativa con el protocolo ActivityPub?
Lanzada originalmente a finales de 2014 como una herramienta enfocada estrictamente en la privacidad y el anonimato —donde ni siquiera era necesario crear una cuenta para publicar—, la plataforma evolucionó para permitir que cada blog funcione como una cuenta de red social federada. Esto significa que un blog en Write.as posee una dirección de usuario con el formato @usuario@write.as, la cual puede ser buscada y seguida desde instancias de Mastodon, Pleroma o Friendica como si se tratara de cualquier otro perfil, pongo como ejemplo mi propio blog https://text.tchncs.de/mdtblogmx/ que como verán esta en la instancia wtite.as de text.tchncs.de el cual puede seguirse desde cualquier cuenta del fediverso dándole follow a @mdtblogmx
La arquitectura de Write.as se basa en el software de código abierto WriteFreely, lo que garantiza que los artículos publicados se distribuyan automáticamente a los "muros" o líneas de tiempo de los seguidores en el Fediverso, permitiendo que las interacciones como "me gusta" o "impulsos" (boosts) se sincronicen entre servidores distintos. A diferencia de las plataformas de blogs tradicionales que dependen de lectores RSS o boletines de correo, Write.as utiliza la infraestructura descentralizada para convertir un texto estático en un objeto social dinámico que puede ser comentado y compartido a través de diferentes plataformas compatibles. Esta integración permite que el contenido extenso y analítico recupere visibilidad en un entorno dominado por mensajes cortos, manteniendo la interoperabilidad sin rastreadores ni publicidad.
#WriteAs #Fediverso #ActivityPub #Blog #Tecnologia #Mastodon
Learning some of the secret backend sauce of NodeBB. It uses a relay - FediBuzz - to pull content from specific hashtags into its federated forums.
I knew that when I tagged #ActivityPub it ended up showing in activitypub.space, now I know how!
I made a diagram yesterday that contrasts #ActivityPub and #SolidProject that is I think interesting to consider.
In the past I've been very active on the Solid forum, and tried to get a collab going with #SocialHub community. A number of points that existed then, are still issues today I think.
Like, though anyone could participate in the standards process via chat, the Solid team and Inrupt were not really interested in their community, hardly giving attention while people were building interesting stuff there.
Also at the time basically all available code was Javascript, making Solid uninteresting or hard to access for other language devs.
But I think biggest issue was that Solid didn't know what it was. It was positioned as 'personal data vault' on the landing page then (but not using this term), but was 'secretly' TBL's desire to reboot the #SemanticWeb. The new web would be all 'Solid apps'. But the adoption strategy for that didn't exist.
RE: https://mastodon.social/@reiver/112133984854710390
"A guide to implement ActivityPub in a static site (or any website)" by @mapache
https://maho.dev/2024/02/a-guide-to-implement-activitypub-in-a-static-site-or-any-website/
I suspect that there is an error in the Turtle specification, in the section shown in the screen-shot.
(It relates to JSON-LD, which ActivityPub / ActivityStreams is built on.)
I suspect that "PN_CHARS_BASE" is an error.
Because other parts of other specifications seem to not make sense if it is.
I suspect that maybe it should have been "PN_PREFIX" instead.
It is a lightweight, privacy-first Fediverse client for iOS, built around a simple idea: fast, small, predictable behavior, and first-class support for snac.
What makes it different:
• snac-first by design, not "compatible by accident"
• Works with all Mastodon API compatible software, including Mastodon, snac, GoToSocial, Akkoma, and others
• EXIF stripping on upload (HDR and orientation preserved)
• Optional on-device alt text generation via Apple Intelligence for your uploads and for images in your timeline
• Markdown posting for snac
• Granular notifications, grouping, multi-account
• Blocking and moderation tools
• Very small footprint, very low RAM usage
Alt text generation happens entirely on device via Apple APIs on supported hardware. Nothing is sent to external services.
It is built around my own workflow and priorities. It may not be for everyone, and that is perfectly fine.
Important note:
MastoBlaster will always be free for BSD Cafe users, illumos Cafe users, and for anyone connecting to a snac instance, including self-hosted ones.
The app is already usable, but this is still a test phase. I am looking for feedback, bug reports, and real-world usage insights.
TestFlight link:
https://testflight.apple.com/join/Pkxa5R1k
Stay tuned.
#MastoBlaster #iOS #Apple #Fediverse #Mastodon #snac #GoToSocial #Akkoma #ActivityPub
#MastoBlaster has its own #Fediverse account - powered by #snac
Follow @mastoblaster to receive all the updates, insights, etc.
There is a larger discussion about fixed-point numbers versus floating-point numbers.
And that, ALL programming-languages should have fixed-point numbers built into them.
And that, programmers should be warned against using floating-point numbers in all but a set of very specialized situations — where inexact math is OK.
For most programmers in most situations inexact math is NOT OK. And, they should NOT use floating-point numbers.
This is likely (directly or indirectly) the fault of a single paragraph in IETF RFC-7159 / RFC-8259 (shown in the attached screen-shot).
(And note that, there is a difference between JSON and IETF JSON. JSON did not have this. IETF JSON does.)
That paragraph (in the IETF RFC) was NOT a requirement. But, others made it a requirement — including JSON-LD.
This is from the JSON-LD spec.
ActivityPub / ActivityStream are based on JSON-LD.
I think it was a very bad idea for JSON-LD to define "number" this way!
It makes it so numbers with fractional values are inexact & lossy.
This include values that are common for money.
For example, neither 0.10 and 0.20 can be represented exactly. So, 0.10 + 0.20 does NOT equal 0.30!
It should have used FIXED-point numbers rather than FLOATING-point.
This is how #Holos currently handles #E2EE DMs over #ActivityPub. Holos is a project we develop alongside #Fedilab.
@sk@utsukta.org mentioned in another thread that the way Hubzilla and threadiverse software handle group discussions is incompatible.
It got me thinking about whether that is true. At its core both FEPs (171b and 1b12, respectively) rely on a central "distributor" node to send activities to recipients.
@silverpill@mitra.social did further comparisons in thr text of 171b itself:
Announceactivity is used instead ofAdd. Conversation and related activities are synchronized between participants, but conversation backfilling mechanism is not specified.
The questions here are:
Add in addition to Announce, would that satisfy basic synchronization (not backfill) requirements laid out by 171b?Announce could not be used to facilitate private federated group discussions as well? Assuming visibility maintains scoped to addresses, I don't see any immediate reason why not...With #HolosDiscover we checked multiple criteria before indexing: "indexable" enabled, account not locked, no #nobot or #noindex in bio, not in opted-out list, only public posts. Every deletion, edit or block was processed instantly via #ActivityPub.
Google uses that same "indexable" flag but ignores everything else, keeps deleted content cached for weeks.
We shut it down after pushback. Was that the right call? Don't hesitate to share, this concerns the whole Fediverse.
| It should have stayed up: | 150 |
| Right call to shut it down: | 71 |
| No opinion: | 65 |
Closed
In the old blogging software I created back in the 1990s, I had a handful of posts types
There was a type of rich-text oriented post that had a title. (Article)
And, there way another type of rich-text oriented post that did not have a title. (Note)
(There were also other types of posts, but they aren't relevant here)
These 2 types of posts were rendered / displayed differently
I.e., my 1990s software already had this distinction
I've seen an ongoing debate between "Note" versus "Article" in ActivityPub / ActivityStreams.
When is something a "Note"‽
When is something an "Article"‽
Personally — I would probably have made the distinction this way.
An "Article" has a title.
A "Note" doesn't have a title.
(In ActivityPub / ActivityStreams, a 'title' seems to tend to get represented in the "name" field.)
boostedThe current fediverse is an evolutionary dead-end for 2 reasons:
1. It has painted itself in a small niche of decentralizing typical social media use cases, by means of post-facto interop and the introduction of protocol decay.
2. Lacking a proper grassroots standardization process, and with the primary mechanism for fediverse extension being only post-facto interoperability, there is no way out.
Congratulations to the early adopters, who managed to "cross the chasm" with their own app platforms. It took true grit to become deep #ActivityPub experts, and plug holes needed for your app, but you have made it. Post-facto interop works in your favor now. You are unrestrained to productively add more features in your app, and put them on the fedi wire for others to deal with.
To avoid fedi to become less and less attractive to newcomers, we must now consider:
“Why do we want to grow the open social web, and for whom?” -- @ben
number of files generated by snac is huge, but i don't care that much anymore.
$ du -hd0 /var/snaci like snac a lot: i run my own server and client, i can modify css (and i do tweak it often, i can modify the source code---didn't get to that yet ;)
133M /var/snac
$ find /var/snac | wc -l
35603
sometimes i use snac command line, but mostly snac web ui and nothing else.
someday maybe i'll try to build some minimalist #activitypub server, but looks like a lot of work :)
see also
activitypub-single-php-file by @Edent@mastodon.social
Week in Fediverse 2026-02-20
Servers
- snac v2.90
- Castopod v1.15.0
- Ktistec v3.3.0
- tootik v0.21.1
- Badgefed v0.1.1
- Gush! v0.0.30
- Wanderer v0.18.5
- PieFed v1.6.6
- Our technical direction (Mastodon)
Clients
- Sengi v1.8.0
- tooi v0.21.2
- Summit v1.77.0
- Aria v1.4.3
- Pixelix v4.3.2
Tools and Plugins
- feed2fedi v3.5.0
- PeerTube Browser: A video discovery project for the federated PeerTube network
Protocol
- FEP-34c1: Collection Filtering using TREE Hypermedia Vocabulary
Articles
- Where Does Community Live?
- Why MAEPs? What should they look like?
- how to not regret c2s
- Reimagining Fediverse Advocacy
- FR#154 – Search and Community
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019c5906-05c0-87bf-8302-8226a8513c00
In *theory* you should be able to follow this test user:
@你好@i18n.viii.fi
But I can't find any Fediverse software which actually supports non-ASCII usernames.
If you are able to see the user, its description, and its avatar - please send me a screenshot 🙂
Hey, this is great. It is so nice to see the uptick of interest in the #C2S part of #ActivityPub. Very uplifting and gives me hope for the future of #fediverse.
I really liked your #FOSDEM presentation, and thank you for mentioning my humble list. They are just notes atm, but I will try to keep them up-to-date. I just made a bunch of updates..
https://codeberg.org/fediverse/delightful-fediverse-experience/issues/130
Would love to hear more on what are the particular plans and goals for your project in the near future?
@ocdtrekkie @badgefed and hey, if we can help to do that backpack badgefed compatible (which is really #activitypub + #openbadges) lmk
EDIT: Build 68 should also run on iOS 18.x but it currently crashes. I'll see if I can fix it.
After quite some time, I’m finally ready to share this.
MastoBlaster is now available in public testing on TestFlight.
It is a lightweight, privacy-first Fediverse client for iOS, built around a simple idea: fast, small, predictable behavior, and first-class support for snac.
What makes it different:
• snac-first by design, not "compatible by accident"
• Works with all Mastodon API compatible software, including Mastodon, snac, GoToSocial, Akkoma, and others
• EXIF stripping on upload (HDR and orientation preserved)
• Optional on-device alt text generation via Apple Intelligence for your uploads and for images in your timeline
• Markdown posting for snac
• Granular notifications, grouping, multi-account
• Blocking and moderation tools
• Very small footprint, very low RAM usage
Alt text generation happens entirely on device via Apple APIs on supported hardware. Nothing is sent to external services.
It is built around my own workflow and priorities. It may not be for everyone, and that is perfectly fine.
Important note:
MastoBlaster will always be free for BSD Cafe users, illumos Cafe users, and for anyone connecting to a snac instance, including self-hosted ones.
The app is already usable, but this is still a test phase. I am looking for feedback, bug reports, and real-world usage insights.
TestFlight link:
https://testflight.apple.com/join/Pkxa5R1k
Stay tuned.
#MastoBlaster #iOS #Fediverse #Mastodon #snac #snac2 #Akkoma #GoToSocial #ActivityPub #OwnYourData
After shutting down #HolosDiscover, we're rethinking the approach with #HolosIndex: users explicitly opt in by adding #HolosIndex to their bio with interest tags, then submit their profile. No assumptions, no default settings.
This will power interest-based discovery across the #Fediverse, helping people find each other through shared interests. Still all through #ActivityPub of course, with real-time deletions and updates.
Maybe something to clarify with #HolosSocial. There is a full moderation system like on any Fediverse instance. Moderators can ban accounts. But relays are dumb by design: your identity and data belong to you, not to the relay. A ban is like a relay going down, you don't lose everything. You can move to another relay and keep all your followers, following, and data. With a custom domain the transition is seamless, otherwise it works through standard #ActivityPub migration.
Why do we want to grow the open social web, and for whom? @ben says the value is in protocols that allow people — all people around the world — to build and own communities that address their needs. "The only way to achieve that is to not just co-design with them but distribute equity. They must be full co-owners of the open social web," he writes.
Minor tweak to improve signature key retrieving for some Wordpress configurations.
Fixed web UI incorrect links to actor public pages for some configurations.
Fixed mismatch in the accounts being followed number in the public and people pages.
Notifications can be filtered by category (contributed by byte).
Dates are shown adjusted to the account's time zone (contributed by dandelions).
Configurable limit for poll items (contributed by dandelions).
Fixed incorrect scope when editing a post (contributed by dandelions).
Change the strip_exif logic to work with the already existing OpenBSD sandbox (contributed by oxzi).
Mastodon API: Add poll creation (contributed by davidrv00), fixed a voting bug (contributed by davidrv00), added a fix to verify_credentials (contributed by ag-eitilt).
Updated Czech, German, Brazilian Portuguese, Spanish translations (contributed by pmjv, zen, daltux).
If you find #snac useful, please consider buying grunfink a coffee or contributing via LiberaPay.
Heh, heh. Tonight I stumbled upon a hidden little feature in Fedify's CLI.
If you run `fedify nodeinfo mastodon.social -b` you get a cute little ascii art representation of the instance's logo.
Happy to see a bit of fun mixed into these fedi tools!
Recently, there was a question by @taylorlorenz about how you explain the Fediverse to someone who doesn't use it.
And usually, what we tend to do is we talk about servers and decentralisation and federation and ActivityPub and all these highly technical concepts.
I've been thinking about it, and all that technical stuff is really impressive work by people far more clever than I'll ever be.
But for me, that technology is a facilitating thing. It's like trying to describe how a bicycle works, rather than why you ride it.
Instead, what the Fediverse is, is a place to have conversations online without algorithms, AI, and ads getting in the way.
Which is increasingly a rare thing online.
Almost the entirety of the internet, from SEO on the web to YouTube to TikTok to Spotify to Instagram and X and Facebook, has been turned into a race to game an algorithm designed to sell ads.
What makes the Fedi unique is that it's not that.
And I suspect if you're trying to persuade someone to try Mastodon (or Lemmy, or Pixelfed, or GtS, etc), you'll get a lot further explaining it as algorithm-free, ad-free, AI-free conversations, rather than trying to describe a decentralised protocol.
There's a lot of energy on the #Fediverse right now to discuss/find a #Federated alternative to #Discord using #ActivityPub.
@strypey suggested that I put this out there to anyone who's thinking about it. We could probably rebuild most of Discord's features as an #Emissary inbox without doing a lot of back end code.
I'm too swamped to start on this right now. But if you're a great HTML+CSS designer, I'm able to give some time to a team who wants to take this on.
#Roomy currently based on AT Proto but looking to add #ActivityPub soon
https://itsfoss.com/roomy-discord-alternative/
https://fedi-relay.gyptazy.com is a tech related relay instance that connects over 100 instances, focussing on things like #FreeBSD, #BGP, #IPv6, #Proxmox, #Homelab, #Linux and many other things! You can easily add a really when using #snac / #snac2, #mastodon, #pleroma and many other ones!
#community #activitypub #socialmedia #fedi #fediwall #relay #opensource #tech #federated #social
This morning I promoted nolto.social, a platform that was made - at least I thought so, to be a Fediverse based alternative to LinkedIn. As I'm getting more and more annoyed by LinkedIn and all the useless posts over there, I was happy to find an independent alternative.
nolto.social still worked this morning, but when I came back later; i found the project deleted and at least when you are viewing the website from your smartphone, you see a message from the developer of nolto.social where he states that this project was never meant to grow. Obviously this was just a one person project who became overwhelmed by the success of the platform and by the fact, that companies started creating profiles and nearly 1000 people joined within a short time period. But now it seems that this project ran out of control and the maintainer decided to pull the emergency break. He is also talking about negative feedback he received for the platform and even personal harrassment.
It is sad that a promising project like this had been terminated, but I can understand what made the maintainer doing so. Managing a business platform can become a fulltime job quite fast and it also requires technical ressources and money to run these resources.
I firmly believe that we need an alternative to LinkedIn. I believe that people don't want all this bullshit posts just created to please the algorithm and to generate likes and feedback. And I believe that people would like a business network which is nothing else than a business network - no space for bursting egos and self promotion, but a space for connection and serious discussion.
Fediverse would be the ideal space for this. But as we know, if business networks are successful, they require more and more attention, more ressources, more money. And at this is the problem. When you need money to run your social network, it's tempting to ask yourself how you could generate money by using the ressources you already have, which are user data...
I don't see a solution for this now, just sharing some thoughts.
I would even host it at home, but it seems like huge parts of the Fediverse are IPv4-only, and #ActivityPub behind Dual-Stack Lite doesn't sound like fun.
With https://discover.holos.social we may have highlighted that many Fediverse users don't pay attention to their default settings. We built a fully respectful search engine that only relies on #ActivityPub, with instant deletion, updates, and indexing only consenting users. We will likely shut down the service, but the source code will remain available as we believe the approach is ethical. That same indexable setting already lets Google index your posts and keep them cached long after deletion.
The walled gardens of the big tech-platforms will be their demise. So much innovation is lost because of the need for control.
Really, the U.S. platforms are not forward looking. The have hit reverse a long time ago, going full speed towards history.
In the previous century I could pick up a phone and call anyone. Try that with the big platforms. NoT wiTHout a DeAl!
Open protocols are the way ahead.
Your Home Feed is the inbox of an ActivityPub actor — in particular YOUR ActivityPub actor.
There could be an actor for each hash-tag, too.
You could even do Del.icio.us like things — and have actors for intersections of hash-tags, too.
These hash-tag actors' inboxes would need to be readable by anyone.
...
This could be a more ActivityPub like API alternative to Mastodon's "GET /API/v1/tags/{name}" API.
#ActivityPub #FediDev #FediDevs #Fediverse #HashTag #HashTags
@lps
That would be interesting indeed. We have an open feature request for this (https://github.com/AntennaPod/AntennaPod/issues/7698) but there are some technical and legal challenges. No decision has been made yet on whether this might be implemented (if a PR would be accepted).
But did you know you can already open ActivityPub comments (in the browser) for episodes that support it? In the player screen you can tap on the three dots and then 'Show comments'!
@dasgrueneblatt
#ActivityPub #podcasts
@thenewoil
> Tinder looks to AI
The enshittification continues. I remember @evan shared some thoughts about using ActivityPub to develop a federated #dating app. In some ways, it's the ultimate test for UX, onboarding, etc, in federated networks. Some challenges;
* it requires helping people meet within a geographical range
* it requires a critical mass of attractive people using it to attract others (the bootstrap problem dialed up to maximum)
* Trust & Safety are *essential*
Anyone in my followers list on a server that has secure fetch enabled? I want to use it to test my proxyUrl implementation for client to server #ActivityPub. :D
RE: https://badgefed.org/grant/badgefedorg_135_8_81bd973ba9611087987c50769193a675
@fajfer has helped #badgefed by deploying it to its first Kubernetes environment, smoothing out the rough edges to make it work properly, and now I’m proudly quoting his badge to test quotes!
Comment if you can see this quote in #mastodon!
It’s out!
The video of my FOSDEM 2026 talk on decentralised badges + ActivityPub (BadgeFed) is now online 👀
Check it out here:
https://video.fosdem.org/2026/h2215/JEMNBZ-decentralised-badges-activitypub-badgefed.av1.webm
Part of the Social Web track:
https://fosdem.org/2026/schedule/track/social-web/
Having some silly fun with @stegodon a new fediverse platform with an SSH TUI interface. The first screenshot is the web profile, the second is the TUI interface.
This is the first command line UI for ActivityPub client I've seen that has an actual backend server platform tied to it.
| yes, for myself and other people: | 9 |
| yes, just for myself: | 22 |
| no, but maybe in the future: | 33 |
| no: | 32 |
2/
RE: https://mastodon.social/@reiver/115945290105913697
The resolving of a Fediverse ID to one or more cryptographic public-keys could happen via the activity-file for the user.
A JSON-LD namespace (separate from ActivityPub) could put the cryptographic public-keys into the activity-file.
But, I think we would need more information than what the 2 current methods for including cryptographic public-keys currently support.
#ActivityPub #Cryptography #FediDev #FediDevs #Fediverse #JSONLD
1/
RE: https://mastodon.social/@reiver/115945290105913697
Right now, Fediverse IDs resolve to HTTPS URLs.
For example, the Fediverse ID:
@reiver@mastodon.social
Resolves to HTTPS URL:
https;//mastodon·social/users/reiver
...
If we wanted cryptographic public-keys to serve as a basis of Identity on the Fediverse, then —
We would (similarly) also need a Fediverse ID to resolve to one or more cryptographic public-keys
...
#ActivityPub #Cryptography #FediDev #FediDevs #Fediverse #JSONLD
I dream of being able to store my online social presence, identity, and history just as — an (organized) set of static files.
A set that I control.
And, I can (if I want to) host myself. (I.e., I am the "source of truth" / "origin" for my files.)
RE: https://mastodon.social/@reiver/116018261922778583
#ActivityPub #FediDev #FediDevs #FediUX #Fediverse #FediverseUX
3/
If you cannot get (most) regular people to write JSON-LD, JSON, or even HTML —
But, you might be able to get them (regular people) to write something similar to Markdown and INI —
Then, are there ways you could (explicitly or implicitly) encode JSON-LD type information, such as ActivityPub, into a Markdown-like or INI-like file — in a way where they (regular people) would likely include it?
I suspect — probably yes.
#ActivityPub #FediDev #FediDevs #FediUX #Fediverse #FediverseUX
https://romanzolotarev.com/pub/hi
becomes
https://romanzolotarev.com/pub/hi.rss
how cool is that? 😎
$ du -hd0 /var/snac && find /var/snac | wc -lmeanwhile #rss feed is just 9999 bytes
61.8M /var/snac
9532
$
$ curl -s https://romanzolotarev.com/pub/hi.rss | wc -cthanks #snac2 for great defaults and working perfectly out of the box ❤️
9999
@mapache Same problem :-(
Piefed is seeing a surge. 📈
El tipo de aplicaciones/servicios que todavía consigue emocionarme con la tecnología 😍
@HolosSocial es una red completamente descentralizada basada en #ActivityPub que crea un servidor en el móvil que comunica con el resto de servidores a través de un relay.
Podría entenderse como un servidor de Mastodon, p. ej., con un único usuario ejecutándose en el dispositivo móvil donde se almacenarían todos sus datos.
Buenas gentes del #fediverso , necesito vuestro #fediconsejo
¿Me recomendaríais una instancia de blog compatible con #activitypub tipo #writefreely ? A ser posible, una que sea gratuita y cuya interface esté en castellano o catalán.. Sólo es para trastear un poco.
¡Gracias!
damn "How We Lost Communication to Entertainment" by @ploum hits hard — can't decide between setting up my own snac2 instance or just getting rid of this account for good
https://ploum.net/2025-12-15-communication-entertainment.html
There is a BOF session today on Fediverse events. I think it would make a lot of sense to have a Task Force of the Social Web Community Group focused on the Event schema in #ActivityPub.
This is what they took from us #activitypub #c2s
I think @badgefed (OpenBadges + #ActivityPub) is a great idea 👏🏻 @mapache #FOSDEM #SocialWeb
Emissary along with @Bonfire and @swf are working on #MLS based e2ee messaging over #ActivityPub supported by Sovereign Tech Fund
I got a t-shirt from @mediaformat ♥️
#owncast is FOSS and awesome. so why did #ATproto people build smoke signals? same reason #bluesky didn't just build off #ActivityPub I assume. something something don't mention VC etc.
On stage now, @django — arguing for widespread adoption of ActivityPub client-server (C2S) protocol.
I agree with him.
At the very least, to make extension of ActivityPub through JSON-LD namespaces possible.
But also to decouple Fediverse client development from Fediverse server development.
And more.
#ActivityPub #FediDev #FediDevs #Fediverse #FOSDEM #FOSDEM2026 #SocialWeb #SocialWebFOSDEM #SocialWebFOSDEM2026
First talk today at the Social Web Devroom we have @pfefferle talking about the state of WordPress's fediverse integration
#FOSDEM #ActivityPub #fedidev
Week in Fediverse 2026-01-30
Servers
- Betula v1.6.0
- stegodon v1.6.2
- flohmarkt v0.14.3
- Friendica v2026.01
- PeerTube v8.0.2
- Manyfold v0.132.0
- Hubzilla v11.0
- Ktistec v3.2.8
- Castopod v1.14.0
- NodeBB v4.8.1
- shops v0.2.1
- PieFed v1.5.4
- Loops v1.0.0-beta.9
Clients
- Pachli v3.3.1
- tooi v0.20.0
- PeerTube-GTK: Native desktop PeerTube client
Tools and Plugins
- Poduptime v6.2.0
- FediBoost: Automatically boost WordPress posts on connected Mastodon accounts
For developers
Articles
- A Crowdsourced Photo Gallery from the Fediverse – the Open Social Web in action
- Community, Fedi-style
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019bebbb-adee-b1ae-ab85-c1825103684b
Escribí una cosa sobre cómo librarse de X desde Europa, intentando ser muy pedagógica, en especial para personas que pensada tengan alguna relación con instituciones públicas. Por si os resulta útil para moverlo: https://redesnuestras.net/2026/01/28/que-pueden-hacer-las-instituciones-democraticas-europeas-para-defenderse-de-x/
The Quiet app provides high-level technical details of how their app works:
https://github.com/TryQuiet/quiet/#technical-overview
This is actually very similar to one way I imagined a more server-less peer-based usage of ActivitiyPub working.
Edit: Done! https://madeincanada.social/#servers
Instead of manually adding servers to https://MadeInCanada.social, I'll leverage my FediDB.com service with a new API 🔥
On February 3rd (very soon!) I am hosting another [BERLIN FEDERATED NETWORK EXPLORATION CIRCLE] at @offline. It's a chance to meet and talk with people who are interested in the #fediverse & networking & exploration & circ---you get the idea.
We have the pleasure of having @hongminhee who will give a presentation about @fedify "an opinionated #ActivityPub framework for TypeScript that handles the protocol plumbing"
It is an open free event and everyone is welcome!
5/
So, not just Decentralized Social (DeSo), but instead —
Decentralized Social (DeSo), Federated Social (FeSo), Localized Social (LoSo)
The goal is 'social' that is simultaneously — 'Decentralized', 'Federated', and 'Localized', all at the same time.
RE: https://mastodon.social/@reiver/114551725757671167
#ActivityPub #ActivityStreams #Decentralization #DeSo #Federation #FeSo #Fediverse #governance #Localization #LoSo
4/
Federation is the word we use to describe that act of bringing together and connecting these separate Decentralized, Localized communities.
This is where protocols such as ActivityPub, ActivityStreams, etc come into play.
Federation is a voluntary choice.
But, so too is Defederation, if desired.
#ActivityPub #ActivityStreams #Decentralization #DeSo #Federation #FeSo #Fediverse #governance #Localization #LoSo