The current FASP work does seem to focused on addressing ...

2026-08-20T01:13:32Z

In reply to nevent1q…uf9y
_________________________

The current FASP work does seem to focused on addressing discovery, which has a large overlap with relays.

But my understanding is that is in theory the scope of services/capabilities can be much broader (e.g, Mastodon is working on one for content detection of spam/illegal material, and another for shared remote media storage).

So the way I was thinking about it (unclear if this is the way they intended) was considering what services or functionality I might want for my ActivityPub server that either:

benefit from not being siloed to my server (e.g, 3p integration, more data, or reduced cost)
or benefit from not being reliant on my ActivityPub software (e.g, more choice, or not as constrained by one teams bandwidth and roadmap priorities)

I've recently been learning about FASPs, and started playing ...

2026-08-19T21:57:26Z

I've recently been learning about FASPs, and started playing around with making some prototypes. As it's still a relatively new concept, and I've not been able to find much discussion on it, I thought I'd kick one off here. Obviously the amount of code for FASPs at the moment is small in both scope and deployment. So it's probably more useful to focus on the potential of the concept, rather than its current state.

So for those who have looked into it:

What FASPs might you want one day to be available to your server to use?
Or what FASP features might you want to one day provide to other servers?

Or even just generally, I would love to hear people's thoughts about the FASP concept overall.

Nostr notes by Roche

The current FASP work does seem to focused on addressing ...

I've recently been learning about FASPs, and started playing ...