Wohoo! Hello world Solid!
Just deployed my own pod 鈽猴笍馃殌
#LDP #SolidProject #LinkedWebStorage
fedicat
and 1 other
boosted
My experimental #ActivityPub #SolidProject agent now listens to POSTs to a list of inboxes and outboxes and processes activities asynchronously as they arrive.
Next I plan to dynamically define the inboxes and outboxes.
The agent would be given access to a config, subscribe to the listed topics and connect them to the appropriate handler.
It would also set the public key on the named actor. e.g.
:myactor_inbox a :WebHookRegistration;
:topic </inbox/>;
:handler :InboxModified;
:actor </actor>.
馃 socialcoding..
boosted
I've proposed two possible outlines for a document about #SolidProject #Activitypub integration
https://github.com/solid-contrib/activitypub-interop/issues/2#issuecomment-3590595603
The first is more note/tutorial/primer like, because a large part of the content is just redescribing ActivityPub for a Solid audience.
The second assumes prior knowledge of ActivityPub and primarily describes what is needed to integrate ActivityPub with Solid, based on three architectures:
- Server support
- External processing
- External endpoints
My experimental #ActivityPub #SolidProject agent now listens to POSTs to a list of inboxes and outboxes and processes activities asynchronously as they arrive.
Next I plan to dynamically define the inboxes and outboxes.
The agent would be given access to a config, subscribe to the listed topics and connect them to the appropriate handler.
It would also set the public key on the named actor. e.g.
:myactor_inbox a :WebHookRegistration;
:topic </inbox/>;
:handler :InboxModified;
:actor </actor>.
I've proposed two possible outlines for a document about #SolidProject #Activitypub integration
https://github.com/solid-contrib/activitypub-interop/issues/2#issuecomment-3590595603
The first is more note/tutorial/primer like, because a large part of the content is just redescribing ActivityPub for a Solid audience.
The second assumes prior knowledge of ActivityPub and primarily describes what is needed to integrate ActivityPub with Solid, based on three architectures:
- Server support
- External processing
- External endpoints
The web we know is efficient鈥攂ut fragile. Power and innovation have drifted away from users and into platforms. A new generation of open architectures鈥擜ctivityPub, Solid, and beyond鈥攐ffers a way to take control back.
https://techtonicshift.vivaldi.net/2025/10/16/roads-to-the-user-owned-web/
How big is the open social web, the #fediverse, #bluesky etc compared to the big commercial platforms? It's a bit sobering.
From my recent talk "From millions to billions -- a plausible narrative for how to grow the open social web."
@j12t what exposed seems something similar to #solidproject by @timbl that has #webIdentity and data flow