#ThoughtProvoker 🤔

#SX #SocialCoding #SocialWeb #ActivityPub #ReimagineSocial #fediverse #peopleverse

Alt...

Peopleverse ? How do you #ReimagineSocial ? Do you dare to dream? Then Dream. Do you dare to play? Then Play. Can you imagine a peopleverse ? Then let The journey begin.

As precursor to my blog post announcement later today, here's my #SocialHub response to the topic on how to treat the #LinkedData based #ActivityPub open standard where messages can be expressed both as plain #JSON as well as in #JSONLD, leading to the most costly misconception that has dragged the #fediverse sideways from its original promise and power..

https://socialhub.activitypub.rocks/t/practices-around-json-formatting-of-json-ld-messages/8628/24

#ThoughtProvoker 🤔

#fediverse is at an inflection point.

Either revival and course correction to the original #ActivityPub protocol power and promise. With the potential to #ReimagineSocial.

Or keep current track with fedi-we-have. Be content with a few great and reasonably popular app platforms. Surely some more to come. But with a messy wire protocol that stifles #innovation and isn't future-proof.

#AskFedi do you dare to dream?

This special thought provoker is based on personal reflection and 8 years of #commoning. Deliberately exposed to the inherent unsustainability of the #FOSS movement. Burning privilege by spending my savings.

Goal: 1st-hand experience to learn the #social dynamics that make a #commons tick.

I invite you to a #brainstorm & #ideation ride. To ponder how #fedi can organically evolve. Become unbeatable by #hypercapitalism.

https://coding.social/blog/grassroots-evolution

But in an age of #AI who still reads long handcrafted #blogs? Fill in the #poll.

#SX #SocialCoding #SocialWeb

In the interests of starting a more productive dialogue than yesterday's main character was interested in, let's make a #brainstorm thread about design changes to ActivityPub and/or client UI that could actually help address drive-by (often racist) harassment on the fediverse.

Feel free to discuss pros/cons but don't feel an idea needs to be perfect to suggest it. Also since this is a brainstorm don't worry about complexity/implementation cost. If you have a great-but-hard-to-implement idea someone else may think of a way to simplify it.

Note that the underlying problem *is* a social one, do there won't be a technological fix! But tech changes can make social remedies easier/harder.

I've got some to start:

1. Have a "protected mode" that users can voluntarily turn on. Some servers might turn it on by default. In protected mode, users whose accounts are less than D days old and/or who have fewer than F followers can't reply to or DM you. F and D could have different values for same-sever vs. different-server accounts, and could be customized by each user. Obviously a dedicated harasser can get around this, but it ups the activation energy for block evasion and pile-ons a bit. Would be interesting to review moderation records to estimate how helpful this might or might not be. Could also have a setting to require "follows-from-my-server" although that might be too limiting on private servers. Restriction would be turned off for people you mention within that thread and could be set to unlimit anyone you've ever mentioned. Would this lock new users out of engagement entirely? If everyone had it on via a default, you'd have you post your own stuff until someone followed you (assuming F=1). One could add "R non-moderated replies" and/or "F favorites" options to soften things; those experiencing more harassment could set higher limits. When muting/blocking/reporting someone who replied to your post, protected mode could be suggested with settings that would have filtered the post you're reporting.

2. Enable some form of public moderation info to be displayed when both moderator and local server opt-in. Obviously each server would be able to ignore federated public tags. I'm imagining "banned from X server for R reason (optional link to evidence)" appearing on someone's profile & an icon on their PFP in each post viewed by someone on server Y *if* the mods of server X decide it's appropriate *and* server Y opts in to displaying such tags from server X specifically. Alliances of servers with similar moderation preferences could then have moderation action on one server result in clear warning propagation to others without the other mods needing to decide whether to also take action immediately. In some cases different moderation preferences would mean you wouldn't take action yourself but would keep the notice up for your users to consider. Obviously the "Scarlet Letter" vibe ain't great, but in some cases it's deserved, and when there's disagreement between servers about that, mods on server Y could either disable a specific tag or disable federation of mod tags from that server in general. Even better shared moderation tools are of course possible.

3. Different people/groups have different norms around boosting. Currently we only have a locked/public binary. Without any big protocol changes, adding a "prefers boosts/doesn't" setting which would warn in the UI before a viewer chooses to boost if the preference is "doesn't" could help. This could be set per-post, but could also have defaults and could have different values for same-server or not, or for particular servers. For example, I could say "default to prefer boosts from users on my server but not from users on other servers" or "default to prefer boosting on all servers except mastodon.social." Last option might be harder to implement I guess.

#ActivityPub #Meta #Harassment

ActivityPub outboxes are the new RSS / Atom / WebFeed.

You can just read from them to get a JSON feed of someone's posts.

I.e., you do NOT have to implement the full suite of Fediverse protocols, or Follow, or run your own server, or anything else to get someone's posts on the Fediverse — just read from their outbox.

#ActivityPub #ActivityStreams #AtomFeed #AtomFormat #DeSe #FediDev #FediDevs #Fediverse #JSON #OpenSocial #RSS #SocialWeb

Week in Fediverse 2026-04-03

Servers

- TinyAP v0.1.7
- Iceshrimp v2026.4.1
- Gush! v0.0.34
- Ktistec v3.3.5
- Socialhome v0.23.0
- PeerTube v8.1.4
- Misskey v2026.3.2
- NeoDB v0.13.0
- PieFed v1.6.14
- Wafrn v2026.03.03

Clients

- nicolium v0.1.2
- Voyager v2.45.1
- Blorp v1.12.0
- Mitra Mini: A headless ActivityPub client that implements FEP-ae97 specification

Tools and Plugins

- Friends v4.0 (WordPress plugin)

For developers

- BotKit v0.4.0

Protocol

- FEP-1a11: Send Announces Containing Many Activities

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: https://mitra.social/objects/019d30f2-2656-7043-04d6-328ad9750e23

RE: https://mas.to/@Aubreader/116330793703168577

This article is a must read.

An excerpt: “Why would anyone fund an Atmosphere project if #Bluesky, with $100 million in the bank, might ship a competing feature at any moment? Why would a founder bet their career on this ecosystem? The presentation didn't just hurt Graze. It made the entire ecosystem look unfundable.”

Why do I keep bringing up this topic?

Because #ATproto is often put in the same category as #ActivityPub (“open protocols yay”) but I strongly disagree with that stance

Activitypub micropayments idea:
what if instead of some digital token like Taler or Monero, I send a digital “cheque” instead, which is a signed payment intent, signed with the other actor’s e.g. Liberapay pubkey.

At the end of the month, the other person can take all these micropayment cheques and prove to liberapay that other people owe them money, and everything is settled in one transaction.

#Activitypub #micropayments #taler #liberapay

Announcing Mitra Mini v0.1.0

Mitra Mini is an ActivityPub client that implements nomadic identity. It has become stable enough that I decided to cut the first release.

The basic features have been implemented: posts, reposts, likes. For more information, check the project's readme:

https://codeberg.org/silverpill/minimitra

It all started nearly four years ago with a vague idea that linking cryptographic keys to #ActivityPub actors could unlock decentralized identity in Fediverse. Eventually, the solution was discovered, and implemented by several projects, but these implementations were servers, not clients. Now there is finally a client, and the design has been proven to work well.

#NomadicIdentity

@reiver

Today "ActivityStreams: Where do you want to go to today?" might be a slogan we borrowed from Microsoft.

The question is whether #ActivityStreams should be used - besides all the things it is already being used for - to also map to file systems.

The #LinkedData nature of #ActivityPub is generally shunned in favor of plain #JSON. That in itself is fine, as long as:

a) information still represents valid #JSONLD.

b) information models still follow data modeling best practices.

c) information models are designed with #interoperability in mind.

Not saying your approach is good or bad, just observing that everyone mapping and overloading their own app-specific semantics to the poor AS vocab looks to me a worst-practice. We can get away with it, as we made post-facto interop the poor man's accepted practice, lacking more rigorous extension process and guidance.

There are likely existing standardized ontologies.

I am outputting ActivityPub/ActivityStreams content for the listing of what is in a directory.

Think of it as the AP/AS version of output from the `ls` command.

AP/AS has a whole bunch of stuff that can be used to represents files. Even sub-types of files

https://www.w3.org/TR/activitystreams-vocabulary/#object-types

And, while AP/AS has 'Collection' (and 'CollectionPage') —

https://www.w3.org/TR/activitystreams-vocabulary/#dfn-collection

AP/AS doesn't have a 'Directory' type (as a sub-type of 'Collection')

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse

Friends, if you haven't already, it would be a big favour to me if you could enable tags.pub to boost your public tagged posts.

Just search for @_followback in your Mastodon UI. Click the follow button there. (Don't try to follow from the profile page; it doesn't work yet.)

It will follow you back, and when you make a post with a hashtag in it, the server will boost your post from the appropriate hashtag.

#tagspub #hashtags #activitypub

RE: https://mastodon.social/@HolosSocial/116302845964923188

With #Holos, you can have your identity on your own domain. No server? A simple CNAME record is enough. Already have a server? Point a subdomain to handle #ActivityPub traffic and serve a static JSON file on your root domain.

This is a step toward the same sovereignty #Nostr offers with cryptographic identities, but staying in the #ActivityPub ecosystem you already know.

#Holos started at the end of 2025. A full #ActivityPub server now runs on your phone, with the ability to use your own domain as your identity, #E2EE DMs via Signal Protocol, zero-knowledge encrypted backup, #ActivityPub media served from your own cloud, a tailored timeline based on your interests thanks to #HolosDiscover, and the ability to switch views depending on your mood or the content you want to browse. Thank you for your feedback and support that helped to go through these steps.

New post: Can we have a more “social” media?

https://profpatsch.de/essays/a-more-social-media

On advertising, the Fediverse, and what a more human social web could look like.

Special mentions: @smallcircles, @phnt, @happy-programming

#fediverse #activitypub #socialmedia #writing #essay

@silverpill

@delta might like to have a word with you. 😅

I did not try to make the literal comparison between a person who emails or creates email-related software with #fediverse AP solution development.

What I did want to point out was how blurred the lines are in the #ActivityPub fediverse between stuff that is the protocol, and stuff that is solution development i.e. app-specific / domain-specific.

The anti-patterns I listed are encountered by any newcomer dev who takes an interest in creating fedi apps & services, and is faced with much more than they bargained for when reading the AS/AP specs.

It forms a barrier to entry, decrease in attractiveness to create fedi apps, and devs leaving the space for greener pastures (e.g. to #ATProto or various still-less-mature-than-fedi #P2P protocols)

@silverpill

There are a couple of #ActivityPub projects that focus on providing the good tools that abstract away the complexities of wire-level network comms, and help free the hands of a solution developer to focus more directly on what people need, instead of on plumbing and Babylonian speech confusion of how things fit together. I try to emphasize these projects, e.g. @fedify by listing them higher in the https://delightful.coding.social curated lists.

But their challenge is to offer a kind of reverse to browser quirks mode. Web browsers can handle about any malformed HTML a person throws at it, and still manage to turn that into machine processable form, and make the most of it.

As a fedi toolkit builder you almost need to do the opposite. Focus on offering comprehensive and intuitive API's and functionality to solution developers, and translate it into wire chaos that constitutes the fediverse-protocol-of-the-day.

Thanks

RE: https://mastodon.social/@HolosSocial/116286098619535273

The next step with #HolosSocial will be to let you use your root domain as your identity while still using a subdomain for the relay.
Yes, #Holos is kind of like #nostr but with #ActivityPub. The main difference: your data lives on your device, not on a server, and relays remain completely dumb.

Say, how are edits to posts managed? Is there any indication an edit happened, a way to see the original\previous versions or to add an explanation for the changes that's not just a "Edit: x-y-z" line?

I suppose this might more a question for the #ActivityPub tag tho'.

(Although remember that nothing is private on Mastodon. Your private mentions/direct messages are not end-to-end encrypted so your instance admins – and anyone hosting a hammer to their knees – could be reading them all. If you want to talk privately, use Signal or Delta Chat. Never share sensitive information on “private” messages on Mastodon. That goes double for our friends in Gaza.)

#mastodon #fediverse #activityPub #privacy #encryption

With the news of the secret $100 million investment in Bluesky by Bain, I keep thinking about protocols.

Maybe the perceived "drawbacks" of #ActivityPub are ultimately strengths?

#ATproto handles identity in a way that allows a single sign-in across apps. But wouldn't this make it easier to profile you? Is this why crypto VCs are so attracted to it?

And ATproto has funding in the 100s of millions by VCs but at some point they'll want to turn a profit. There is ZERO pressure here to ensh*tt*fy

Fixed some local posts not being shown if the replied post is deleted.

Fixed web UI incorrect links to public posts for some configurations.

Fixed encoding bug in Mastodon-style share links.

Fixed an error that made imposible to leave empty the following hashtags or blocked hashtags from the web UI.

Include post attachments in the RSS feed entries.

Added some OpenBSD-specific documentation (contributed by oxzi).

Fixed some timezones (contributed by matoken).

Fixed some crashes (special thanks to Louis Merlin for helping me with this).

Updated Docker scripts to avoid generating a useless log file.

Fixed several memory leaks, key generation errors and HTML inconsistencies (contributed by dandelions).

Added ostatus.org and FEP-3b86 data to Webfinger objects.

Added a new CONTRIBUTING.md file. Among other guidelines, I explicitly say there that AI contributions are NOT accepted.

snac is now available as a Yunohost app. Thank you very much to Bruno Cesar Rocha for this.

https://comam.es/what-is-snac

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

#snacAnnounces #FrugalFediverse

Abbiamo appena aggiunto 37 nuove destinazioni turistiche italiane alla nostra rete di bot meteo.

Dalle coste siciliane alle Dolomiti, dalla Costiera Amalfitana ai laghi del Nord, i tuoi posti del cuore sono ora nel Fediverso! 🇮🇹

🏖️ Mare & Isole:
@taormina@it.fedimeteo.com - Taormina
@tropea@it.fedimeteo.com - Tropea
@gallipoli@it.fedimeteo.com - Gallipoli
@otranto@it.fedimeteo.com - Otranto
@vieste@it.fedimeteo.com - Vieste
@riccione@it.fedimeteo.com - Riccione
@jesolo@it.fedimeteo.com - Jesolo
@lignano_sabbiadoro@it.fedimeteo.com - Lignano Sabbiadoro
@alghero@it.fedimeteo.com - Alghero
@olbia@it.fedimeteo.com - Olbia
@amalfi@it.fedimeteo.com - Amalfi
@positano@it.fedimeteo.com - Positano
@ischia@it.fedimeteo.com - Ischia
@capri@it.fedimeteo.com - Capri
@portoferraio@it.fedimeteo.com - Portoferraio (Elba)
@lampedusa@it.fedimeteo.com - Lampedusa

🌊 Riviera Ligure:
@sanremo@it.fedimeteo.com - Sanremo
@sestri_levante@it.fedimeteo.com - Sestri Levante
@lerici@it.fedimeteo.com - Lerici
@camogli@it.fedimeteo.com - Camogli
@portofino@it.fedimeteo.com - Portofino
@rapallo@it.fedimeteo.com - Rapallo

🌸 Toscana & Cilento:
@viareggio@it.fedimeteo.com - Viareggio
@forte_dei_marmi@it.fedimeteo.com - Forte dei Marmi
@castiglione_della_pescaia@it.fedimeteo.com - Castiglione della Pescaia
@palinuro@it.fedimeteo.com - Palinuro
@agropoli@it.fedimeteo.com - Agropoli

🏔️ Montagna:
@cortina_d_ampezzo@it.fedimeteo.com - Cortina d'Ampezzo
@courmayeur@it.fedimeteo.com - Courmayeur

🏞️ Laghi:
@riva_del_garda@it.fedimeteo.com - Riva del Garda
@sirmione@it.fedimeteo.com - Sirmione
@bellagio@it.fedimeteo.com - Bellagio
@stresa@it.fedimeteo.com - Stresa

🏛️ Borghi & Gemme:
@assisi@it.fedimeteo.com - Assisi
@noto@it.fedimeteo.com - Noto
@alberobello@it.fedimeteo.com - Alberobello
@ostuni@it.fedimeteo.com - Ostuni

Segui la tua destinazione e preparala la valigia!
https://it.fedimeteo.com

#Italia #Meteo #Fediverso #ActivityPub #Viaggi #Estate #FediMeteoUpdates #FediMeteoAnnouncements #FediMeteoCoverage #Italy

We just added 37 new Italian tourist destinations to our weather bot network.
From the Sicilian coast to the Dolomites, from the Amalfi Coast to the Italian Lakes, your favourite holiday spots are now on the Fediverse! 🇮🇹

🏖️ Coast & Islands:
@taormina@it.fedimeteo.com - Taormina
@tropea@it.fedimeteo.com - Tropea
@gallipoli@it.fedimeteo.com - Gallipoli
@otranto@it.fedimeteo.com - Otranto
@vieste@it.fedimeteo.com - Vieste
@riccione@it.fedimeteo.com - Riccione
@jesolo@it.fedimeteo.com - Jesolo
@lignano_sabbiadoro@it.fedimeteo.com - Lignano Sabbiadoro
@alghero@it.fedimeteo.com - Alghero
@olbia@it.fedimeteo.com - Olbia
@amalfi@it.fedimeteo.com - Amalfi
@positano@it.fedimeteo.com - Positano
@ischia@it.fedimeteo.com - Ischia
@capri@it.fedimeteo.com - Capri
@portoferraio@it.fedimeteo.com - Portoferraio (Elba)
@lampedusa@it.fedimeteo.com - Lampedusa

🌊 Ligurian Riviera:
@sanremo@it.fedimeteo.com - Sanremo
@sestri_levante@it.fedimeteo.com - Sestri Levante
@lerici@it.fedimeteo.com - Lerici
@camogli@it.fedimeteo.com - Camogli
@portofino@it.fedimeteo.com - Portofino
@rapallo@it.fedimeteo.com - Rapallo

🌸 Tuscany & Cilento:
@viareggio@it.fedimeteo.com - Viareggio
@forte_dei_marmi@it.fedimeteo.com - Forte dei Marmi
@castiglione_della_pescaia@it.fedimeteo.com - Castiglione della Pescaia
@palinuro@it.fedimeteo.com - Palinuro
@agropoli@it.fedimeteo.com - Agropoli

🏔️ Mountains:
@cortina_d_ampezzo@it.fedimeteo.com - Cortina d'Ampezzo
@courmayeur@it.fedimeteo.com - Courmayeur

🏞️ Lakes:
@riva_del_garda@it.fedimeteo.com - Riva del Garda
@sirmione@it.fedimeteo.com - Sirmione
@bellagio@it.fedimeteo.com - Bellagio
@stresa@it.fedimeteo.com - Stresa

🏛️ Gems:
@assisi@it.fedimeteo.com - Assisi
@noto@it.fedimeteo.com - Noto
@alberobello@it.fedimeteo.com - Alberobello
@ostuni@it.fedimeteo.com - Ostuni

Follow your destination and pack accordingly!

https://it.fedimeteo.com

#Italy #Weather #Fediverse #ActivityPub #Travel #Summer #FediMeteoUpdates #FediMeteoAnnouncements #FediMeteoCoverage

Introducing Starter Kits

https://blog.joinloops.org/introducing-starter-kits/

#Loops #StarterKits #ActivityPub #Fediverse

#ActivityPub developers only: do you implement rate limit support in your HTTP client implementation?

#EvanPoll #poll

F*** big techs

Les institucions culturals públiques segueixen donant els seus recursos a Meta i companyia.
A l'#HackejaLaTerra proposem canviar-ho: #ActivityPub, desmoneitzar discursos d'odi, protocols oberts i pressió ciutadana.
#Fedivers #ActivityPub #CulturaLliure @sobtec @proyectouna

Week in Fediverse 2026-03-20

Servers

- Akkoma v2026.03
- Bonfire v1.0.2
- PeerTube v8.1.3
- Mitra v4.20.0
- NodeBB v4.10.0
- GoToSocial v0.21.2
- Funkwhale v2.0.0
- Ktistec v3.3.4
- ActivityPub for WordPress v8.0.2
- PeerTube v8.1.3
- ties v0.2.0
- Wafrn v2026.03.02
- PieFed v1.6.13
- Some updates to ActivityBot
- tags.pub: Global hashtag server

Clients

- Fedilab v3.37.1
- tinmop v0.9.9.141421356237309504
- tooi v0.23.0
- Holos v1.0.0
- Voyager v2.44.0
- Aria v1.4.6

Tools and Plugins

- mastodon-bookmark-rss: A small app to let you connect your mastodon bookmarks to your RSS reader
- smol overlays: Chat overlay and emoji wall for Owncast streamers

For developers

- activitypub-federation-rust v0.5.11

Protocol

- FEP-3ab2: ActivityPub Event Streaming API
- FEP-34ec: Notification Collection Endpoint
- FEP-db70: RemoveAll Collection Activity
- FEP-c07e: add product type to object
- FEP-c195: JSONPath Filtering for ActivityPub Collection Retrieval
- FEP-f011: Full-Text Search Query Syntax for ActivityPub
- FEP-a1d1: ActivityPub Patch
- FEP-c81b: Agent Social Attribution for ActivityPub

Articles

- Openness, transparency and reach: three reasons why public institutions should embrace the Fediverse
- The Purpose of Protocols

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: https://mitra.social/objects/019ce933-238d-11fb-304d-c3557c940c30

The source code of #PawFed is now available on #Codeberg. PawFed is a federated map for animal welfare: reports come from the #Fediverse via #ActivityPub mentions, and permanent places like shelters and vets are pulled from OpenStreetMap.

A location is not always required: if you have supplies or food to give away and can ship, just say so.

Found an abandoned animal? Just report it.

How to build a message: https://pawfed.org/tags

Source code: https://codeberg.org/tom79/PawFed

As you might have seen over on @FediTips , Wanderer is a trail-sharing platform for the Fediverse somewhat similar to Strava.

Wanderer is free open source software so you can host your own server if you want, and federated so you can communicate with other servers too.

At the moment Wanderer does require some technical knowledge to create your own server, you can find installation instructions at https://wanderer.to/run/installation/quick and source at https://github.com/open-wanderer/wanderer

#Wanderer #SelfHosting #ActivityPub

7/

Continuing to look for an alternative to "attachment" (for properly supporting an Actor specifying a list of CALL Service actors associated with it) —

Maybe a call specific custom top-level attribute would be useful.

Maybe something like:

"call": [
{
"rel":"callpub",
"href":"https://videocalls.example/users/joeblow"
}
]

Or even:

"call": [
"href":"https://videocalls.example/users/joeblow"
]

.

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall

6/

Continuing to look for an alternative to "attachment" (for properly supporting an Actor specifying a list of Service actors associated with it) —

Maybe a custom top-level attribute would be useful.

Maybe something like:

"service": [
{
"rel":"callpub",
"href":"https://videocalls.example/users/joeblow"
}
]

Although perhaps that is not much better than "attachment", if you just care about calls

So —

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall

5/

Continuing to look for an alternative to "attachment" (for properly supporting an Actor specifying a list of Service actors associated with it) —

I think "endpoints" would also be a poor choice, too. Again, the semantics are wrong, or at least lacking.

So —

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall

4/

Looking for an alternative to "attachment" (for properly supporting an Actor specifying a list of Service actors associated with it) —

I think using "alsoKnownAs" or "sameAs" would be a poor choice. The semantics are wrong.

For example: a Service actor might represent my mobile phone (or software on it). My phone is not me. It is something I have.

So —

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall

3/

But, what about the non- fall-back situation where software could properly support this (when an Actor specifies a list of Service actors associated with it)‽

I think some might say, put the associated Service actors in "attachment". And, semantically I think that would work with ActivityPub, but — I have a very strong dislike with putting everything in "attachment" (and "tag"). It makes parsing difficult.

So —

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall

2/

Because most people wouldn't be able to add custom attributes or custom values to most Fediverse software (including Mastodon) —

Most supporting software would probably want to support a "PropertyValue" link in "attachment" field as a fall-back

For example:

"attachment": [
{
"type": "PropertyValue",
"name": "Video Calls (callpub)",
"value": "https://videocalls.example/users/joeblow"
}

But —

...

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall

1/

AFAIK, there isn't a way for an ActivityPub Actor (such as a Person actor) to specify a list of Service actors associated with it.

...

For example, imagine that there is a Service actor that represents a way to make a video call to me.

And, for example, I have my Mastodon Person actor.

And, I want to let people know about it (and other Service actors associated with me).

How do I do that using AP, etc‽

...

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall

I used to not like JSON-LD. And then I got exposed to CBOR. And, since then, I ended up liking JSON-LD more than I did before.

https://j12t.social/@j12t/114581086678041245

...

I was looking for performant ways of storing JSON-LD data, so that it can be looked up, queried, etc.

CBOR might actually be a way of doing that.

...

For me that is an odd realization given me liking JSON-LD is a reaction to CBOR.

#ActivityPub #ActivityStreams #CBOR #CBORLD #FediDev #JSONLD

🆕 blog! “Some updates to ActivityBot”

I couple of years ago, I developed ActivityBot - the simplest way to build Mastodon Bots. It is a single PHP file which can run an entire ActivityPub server and it is less than 80KB.

It works! You can follow @openbenches to see the latest entries on OpenBenches.org, and @colours for a …

👀 Read more: https://shkspr.mobi/blog/2026/03/some-updates-to-activitybot/
⸻
#ActivityBot #ActivityPub #mastodon #php

"If you want to be in the Fediverse without relying on big intances, or if you just want to own your #data & #identity on the network, running your own instance is the way to go.
That is where Mastodon alternatives such as GoToSocial & #snac comes in.
snac (Social Networks Are Crap) is a minimalistic, lightweight #ActivityPub instance…perfect for single user instances or small communities, and it's so light that even a #RaspberryPi can handle it without breaking a sweat."
https://rochacbruno.com/deploy-your-own-fediverse-instance-with-snac.html

Gualaaaaa, ya empieza a tomar forma #FediPhoto

una fedi aplicación super ligera para publicar una foto (y sólo una) cada día, apta para correr en una raspberry, un vps mínimo o donde quieras

Admite Follow, UnFollow y notifica cuando hay una foto nueva

Publicar una foto es tan fácil como copiarla en la carpeta "inbox" donde esté desplegada la aplicación y chimpón, la envía a tus followers

Le quedan algunas cositas y subo el código

p.d.
NO sirve para nada más que para que yo practique con el #ActivityPub

I’m also exploring ideas like:

• leaderboards
• activity points
• community challenges

Possibly as a component integrated with BadgeFed + Fediprofile, or maybe as a separate project.

Still experimenting.

--

In short:

BadgeFed issues decentralized recognitions.
Fediprofile helps people collect and display them.

Both use #ActivityPub as the backbone.

(You can create your own badge wallet. You can create your own badge issuer. Just use activitypub and openbadges and they should connect).

Badges become portable, social, and decentralized.

And communities can build on top of that.

--

P.S. I decided to NEVER add a wallet into BadgeFed, keeping it simple and extensible by default. So Fediprofile is the default wallet. But anyone can build and use their own. No new specs, no new protocols.

Badges themselves are very simple files.

Often the badge information is encoded inside an image, usually a PNG.

So the image contains both:
• the visual badge
• the structured metadata describing the credential

One file, both human-friendly and machine-readable.

Other times these are simple json files.

--

Where things get interesting is with #ActivityPub.

@badgefed uses ActivityPub as a transport layer for decentralization, and also as a way to add social features.

BadgeFed issues credentials, but it wraps the OpenBadge inside an ActivityPub Note.

The actor creating that note is the badge issuer. <-- important!

--

This is actually very similar to how a Mastodon post works when you post a image.

Imagine:

• the image = the badge
• the post = the description of the recognition

Once published, anyone in the #Fediverse can interact with it:
reply, comment, like, boost, quote, or follow (and block) the issuer.

Badges become social objects.

I think it's a good time to explain how we see @badgefed and @fediprofile, how they work together, and how #badges can use #ActivityPub and the #Fediverse.

Also how this can help communities outside the fediverse!

This is a quick overview of the architecture and ideas behind it. 🧵 1/

(thanks @johannab for the ask ...)

Qué maravilla !!!

Me estoy haciendo una implementacion de #Activitypub en #Java #Micronaut desde cero

acepta Follow/UnFollow y encima te saluda!!

I see the #fedi announcement by a commercial marketing agency of a venture capital based app store joining the fediverse.

Is the #fediverse we have capable of avoiding #enshittification as it grows and attracts an increasing number of corporations, who make it their market?

Is our #ActivityPub landscape resistant to corporate capture and eventual takeover and domination? Just like the Corporate Web, also decentralized.

There are nice niches on the web, like a bloggosphere, bulletin boards, and news readers, that all still exist. But web as a whole is predominantly corporate, arguably not commons based, for the people by the people.

Social experience design defines "commons based" as "where people are in control of their future on a path of healthy evolution and natural growth". A core principle is being sustainable at all times, and timely acknowledge and mitigate risks.

Is fediverse commons based? Did we cocreate the Future of Social networking?

#SX #SocialCoding #poll #AskFedi

Week in Fediverse 2026-03-13

Servers

- Sharkey v2025.4.6
- Gush! v0.0.32
- Wafrn v2026.03.01
- PeerTube v8.1.0
- Ktistec v3.3.3
- Stegodon v1.8.2
- Hollo v0.7.6
- ActivityPub for WordPress v8.0.1
- Misskey v2026.3.1
- tootik v0.21.2
- Vernissage Server v1.31.0
- NodeBB v4.9.2
- PieFed v1.6.12
- Trunk & Tidbits, February 2026 (Mastodon)
- Madblog: A Markdown Folder That Federates Everywhere

Clients

- Sengi v1.9.1
- Fedilab v3.37.0
- Aria v1.4.5
- ap, the ActivityPub API command-line client

Tools and Plugins

- slurp v1.1.0
- Owlbot: An Owncast chat bot with a modular event-driven architecture

For developers

- Pubby: A general-purpose Python library to add ActivityPub federation support to your website

Protocol

- FEP-0151: NodeInfo in Fediverse Software (2025 edition) (Finalized)

Articles

- Link Preview Manifest: A Proposal for the Fediverse
- FR#157 – Social Software Distribution

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: https://mitra.social/objects/019cc4d0-1232-6c08-970c-83c7f49e1a73

Once again, I humbly come to you to ask: do you know of any bloggers that write regularly about the #Fediverse, #ActivityPub, #ATproto, or anything of that nature?

As the network grows, it feels like it’s harder and harder to find individual voices and perspectives. If you’re writing stuff about the network, its evolution, the culture, and the people on it, I’m interested in following you.

Three different #ActivityPub spec guides - three different answers!

FEP-7628 says a Move has an ID, To, & CC.
https://codeberg.org/fediverse/fep/src/branch/main/fep/7628/fep-7628.md

SocialDocs says just an ID, no To nor CC.
https://socialdocs.org/docs/guides/account-migration/#the-move-activity

SWICG says no ID, nor To, nor CC.
https://swicg.github.io/activitypub-data-portability/#process-0

RE: https://w3c.social/@w3c/116216070362563670

FWIW, I have been storing Linked Data (including ActivityPub) in an INI like format — because I find INI-like formats more human-friendly (to both read and write) than JSON.

YAML is probably better than JSON, too, in that respects. But I think INI-like formats are better than YAML.

#ActivityPub #ActivityStreams #JSONLD #LinkedData #RDF #YAML #YAMLLD

A question about #ActivityPub account migration.

Is it possible to use it to combine multiple accounts into one?

That is, can I `movedTo` all my old accounts to one new account, and set *several* `alsoKnownAs` on my new account's actor?

#ActivityPub support in #Madblog

https://blog.fabiomanganiello.com/article/Madblog-federated-blogging-from-markdown

I am glad to announce that Madblog has now officially joined the #Fediverse family.

If you want to test it out, search for this URL on your Fediverse client.

Madblog has already supported #Webmentions for the past couple of weeks, allowing your blog posts to be mentioned by other sites with Webmentions support (WordPress, Lemmy, HackerNews…) and get those mentions directly rendered on your page.

It now adds ActivityPub support too, using #Pubby, another little Python library that I’ve put together myself (just like Webmentions) as a mean to quickly plug ActivityPub support to any Python Web app.

Webmentions and Pubby follow similar principles and implement a similar API, and you can easily use them to add federation support to your existing Web applications - a single bind_webmentions or bind_activitypub call to your existing Flask/FastAPI/Tornado application should suffice for most of the cases.

Madblog may have now become the easiest way to publish a federated blog - and perhaps the only way that doesn’t require a database, everything is based on plain Markdown files.

If you have a registered domain and a certificate, then hosting your federated blog is now just a matter of:

mkdir -p ~/madblog/markdown
cat <<EOF > ~/madblog/markdown/hello-world.md
# My first post

This is my first post on [Madblog](https://git.fabiomanganiello.com/madblog)!
EOF

docker run -it \
  -p 8000:8000 \
  -v "$HOME/madblog:/data" \
  quay.io/blacklight/madblog

And Markdown files can be hosted wherever you like - a Git folder, an Obsidian Vault, a Nextcloud Notes installation, a folder on your phone synchronized over SyncThing…

Federation support is also at a quite advanced state compared to e.g. #WriteFreely. It currently supports:

• Interactions rendered on the articles: if you like, boost, quote or reply to an article, all interactions are rendered directly at the bottom of the article (interactions with WriteFreely through federated accounts were kind of lost in the void instead)

• Guestbook support (optional): mentions to the federated Madblog handle that are not in response to articles are now rendered on a separate /guestbook route

• Email notifications: all interactions can have email notifications

• Support for quotes, also on Mastodon

• Support for mentions, just drop a @joe@example.com in your Markdown file and Joe will get a notification

• Support for hashtag federation

• Support for split-domain configurations, you can host your blog on blog.example.com but have a Fediverse handle like @blog@example.com. Search by direct post URL on Mastodon will work with both cases

• Support for custom profile fields, all rendered on Mastodon, with verification support

• Support for moderation, either through blocklist or allowlist, with support for rules on handles/usernames, URLs, domains or regular expressions

• A partial (but comprehensive for the provided features) implementation of the Mastodon API

If you want you can follow both the profiles of my blogs - they are now both federated:

• My personal blog: @fabio (it used to run WriteFreely before, so if you followed it you may need to unfollow it and re-follow it)

• The #Platypush blog: @blog

RE: https://example.viii.fi/posts/69b029a4-2ee5-0f49-b23b-333d1e8ee38b.json

OK! Editing posts now works.

A fully complete #ActivityPub server in under 80KB of code.

https://gitlab.com/edent/activity-bot/

I think supporting polls will be too hard, so I'm declaring this feature complete (although not bug free) for now.

If you have any suggestions for how to improve it - let me know 🙂
#ActivityBot

Imagine being able to curate lists of accounts by topics, allowing others to easily follow them after they consented to be included.

Meet Starter Kits.

Consent driven discovery that federates across servers and software.

With a rich browsing experience so you can explore kits without an account.

Shipping Soon 🚀

#Loops #StarterKits #ActivityPub #FeaturedCollections

Alt...

Loops Starter Kits Browse

Alt...

Loops Starter Kits Kit page

Alt...

Loops Starter Kits Kit page federation modal

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?

Cc: @reiver @evan @ossguy @karen

#ActivityPub #FOSS #OpenSource #Mastodon

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.

#ActivityPub #ActivityStreams #FediDev #Fediverse

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

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.

https://github.com/nextcloud/social

#snac #activitypub #mastodon

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.

#SelfHosting #Fediverso #ActivityPub

Complete this sentence:

"I experience #fediverse as a .."

#Poll #AskFedi #Microblogging #Mastodon #ActivityPub

In the #Fediverse, most software is built around a specific platform model. One for microblogging, one for video, one for photos... and new ones will keep coming.
With #Holos, your phone runs your own #ActivityPub server. You control your data and can use your own domain as your identity.
Built on the protocol, not a platform model, Holos is not limited to a single use case. One account that adapts to your needs.
That's where we're heading, and we hope for your support.

#HolosSocial

@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.

Alt...

Antique horseracing game from the fiftees, small horse figures on a plastic track, that can be slid forward.

@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.

#SX #SocialCoding

Recently, there was a discussion about generic #ActivityPub servers. Several people claimed that they were working on one, but it turned out that their "generic" servers only support activities defined in the ActivityPub specification. Such a server shouldn't be called generic. It is not difficult to build, neither it is an interesting concept because competing protocols (e.g. Nostr) already offer much more.

I've been writing a #FEP that describes how to build a real generic server. It is not finished yet, but I feel like now is a good time to publish it:

FEP-fc48: Generic ActivityPub server

This kind of server:

- Can process any object type, and can process non-standard activities like EmojiReact.
- Compatible with FEP-ae97 clients.
- Does not require JSON-LD.

I attempted to implement it when I was researching security properties of FEP-ae97 API: https://codeberg.org/silverpill/fep-ae97-server. Back then I didn't know what to do with side effects, but now I think that we can simply force clients to specify them.

Special thanks to @mariusor and @trwnh for their input.

#C2S

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

- Fedify v2.0

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

UPDATE: https://hub.vocalcat.com is open for public registration.

--

I’m building a new tool and looking for volunteers to test it! A #fediverse linktree.

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/gotosocial authentication, so if you have a mastodon or gotosocial account register a new account.

--

UPDATE: I am doing load testing at this point, if many people sign-up expect some unavailability moments. Thanks for your patience, I want to discover the limits of the stack.

Alt...

One webpage screenshot in white background and big letters saying Your links, Your Identity our Network

Alt...

A screenshot of links in rows, showing a profile with Pixelfed, Blog, Mastodon, LinkedIn links among others.

@reiver @thisismissem @mfru

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/

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse

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.

#ActivityPub #ActivityStreams #RDF #JSONLD

Alt...

2.6 RDF Blank Nodes RDF blank nodes in Turtle are expressed as _: followed by a blank node label which is a series of name characters. The characters in the label are built upon PN_CHARS_BASE, liberalized as follows: • The characters _ and digits may appear anywhere in a blank node label. • The character . may appear anywhere except the first or last character. • The characters -, U+00B7, U+0300 to U+036F and U+203F to U+2040 are permitted anywhere except the first character.

#MastoBlaster has its own #Fediverse account - powered by #snac

Follow @mastoblaster to receive all the updates, insights, etc.

#iOS #Fediverse #Mastodon #snac #GoToSocial #ActivityPub

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.

#ActivityPub #ActivityStreams #JSONLD #RFC7159 #RFC8259

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.

RE: https://mastodon.social/@reiver/115956356584464586

#ActivityPub #ActivityStreams #JSONLD #RFC7159 #RFC8259

Alt...

This specification allows implementations to set limits on the range and precision of numbers accepted. Since software that implements IEEE 754 binary64 (double precision) numbers [IEEE754] is generally available and widely used, good interoperability can be achieved by implementations that expect no more precision or range than these provide, in the sense that implementations will approximate JSON numbers within the expected precision. A JSON number such as 1E400 or 3.141592653589793238462643383279 may indicate potential interoperability problems, since it suggests that the software that created it expects receiving software to have greater capabilities for numeric magnitude and precision than is widely available.

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.

#ActivityPub #ActivityStreams #JSONLD #RFC7159 #RFC8259

Alt...

number In the JSON serialization, a number is similar to that used in most programming languages, except that the octal and hexadecimal formats are not used and that leading zeros are not allowed. In the internal representation, a number is equivalent to either a long or double, depending on if the number has a non-zero fractional part (see [WEBIDL]).

This is how #Holos currently handles #E2EE DMs over #ActivityPub. Holos is a project we develop alongside #Fedilab.

https://holos.social/e2ee

#HolosSocial

@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:

Announce activity is used instead of Add. Conversation and related activities are synchronized between participants, but conversation backfilling mechanism is not specified.

The questions here are:

1. If threadiverse software federated out an Add in addition to Announce, would that satisfy basic synchronization (not backfill) requirements laid out by 171b?
2. Is there any reason why 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.

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

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse

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.)

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse

#ThoughtProvoker

The 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

http://coding.social/blog/shared-ownership/

number of files generated by snac is huge, but i don't care that much anymore.

$ du -hd0 /var/snac
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 🙂

#Fediverse #ActivityPub #Unicode

@django @evan @liaizon

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.

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).

https://comam.es/what-is-snac

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

#snacAnnounces #FrugalFediverse