[Proposed Work Item]: ActivityPub for Solid

[thhck]

Enabling Activity Pub for Solid

see also:

• ActivityPod
• SoAP opera

potential deliverable:

• an Acitivity Pub component for CSS

[elf-pavlik]

An interesting overlap would be with

• [Proposed Work Item]: Social profiles - public and protected #61

I may use AS vocab for basic social profile info in my implementation.

I think we should ping @jg10-mastodon-social and @mrkvon

[jg10-mastodon-social]

Adapting from #54 (comment)

It seems like it might be possible to continue:

• [New Work Item] ActivityPub/Fediverse interoperability solid/specification#708

It never made it into the TR list and was moved to solid-contrib but there's now at least 5 partial implementations and 3 people recently working on it in some form.

Personally I can't commit to a "task force" but did offer to do some draft writing.

I'm not personally that interested in an ActivityPub component for CSS - I currently prefer an agent-based approach, but I think there is a lot of common ground between different approaches to implementing ActivityPub with Solid, and I think some kind of spec or primer document would be useful.

Here's two suggestions for what the document could look like, depending on interest solid-contrib/activitypub-interop#2 (comment)

[renyuneyun]

Potentially there can be a side-effect (or synergy between other work items): defining a standard (or de facto standard) for extending Solid with additional protocols.

(See also #68.)

In particular, ActivityPub requires a "bot" residing next to the Pod. Can there be a standard/common way to allow multiple such "bots" exist (and advertize / be explicit about their existence), for different goals (e.g., an ActivityPub bot, a CalDAV bot, a CRDT bot)?