https://c3d2.social/users/astro posted on Mar 20, 2026 14:33
In reply to: https://activitypub.space/post/1615
In reply to: https://activitypub.space/post/1615
Instance software is constantly evolving and adding new features. Wouldn’t it be good if there was a way for other instances to discover what features yours can handle, to determine how they will communicate?
One way to do this could be to add the FEPs, etc that an instance supports to the nodeinfo response that it serves. Possibly as a protocol, a service or just in the metadata part.
Where would make the most sense? Or is there another mechanism apart from nodeinfo entirely?
@julian dunno, I'm a bit taken aback by the greeting
So I got this bot that allows multiple people to curate a list of toots that are boosted by it, to create a nice topical account to follow.
Now I only need ideas what to boost haha :)
Congrats, you just reinvented FEP 1b12, the foundation for Lemmy, PieFed and Mbin.
@rimu not really no, but thanks for the snarky comment
📢 The @w3c Breakouts Day 2026 agenda is available!
➡️ https://www.w3.org/calendar/breakouts-day-2026/
Two dates: 🗓️ 25 March from 13:00-15:00 UTC and 🗓️ 26 March from 21:00-23:00 UTC
We invite the web community to take part in these one-hour sessions and give input on diverse topics such as #ActivityPub, #AI, cognitive #a11y, #privacy, policy engagement, #sustainability and more!
Anyone with a W3C account (including non-Members) can participate. No fee or registration is required.
I sat down with @snarfed.org to talk about his work around the #fediverse, the #indieweb and the #atmosphere including (fed.)brid.gy and @anewsocial
https://openchannels.fm/connecting-decentralized-social-networks-and-rethinking-interoperability/
@quillmatiq you should post about this on the @anewsocial account!
@liaizon Tysm for the heads up!
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
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
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" and "sameAs" would be a poor choice. And, 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
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
@brettm@swarm.coiloptic.org Could I see the problematic JSON-LD document?
@julian@activitypub.space
