#solidproject — Public Fediverse posts

Static #eportfolio sites for students would be nice, too (or #SolidProject pods or #ATProto PDS sites), at least for college students developing their professional identities. Combining that w/chat, social networking and #OpenBadges is a better foundation than building everything around an enterprise #LMS gradebook. Need better moderation and #E2EE privacy controls though. Have your students vibe code their own final exams in the meantime while Canvas is down ;)
#EdTech
https://hachyderm.io/@inthehands/116539289475889788

Static #eportfolio sites for students would be nice, too (or #SolidProject pods or #ATProto PDS sites), at least for college students developing their professional identities. Combining that w/chat, social networking and #OpenBadges is a better foundation than building everything around an enterprise #LMS gradebook. Need better moderation and #E2EE privacy controls though. Have your students vibe code their own final exams in the meantime while Canvas is down ;)
#EdTech
https://hachyderm.io/@inthehands/116539289475889788

@woozle the article was described as "fairly long thinkpiece" by @Profpatsch which with 53 min. read time is an understatement of "fairly long" where it comes to typical online content.

Thank you for taking the time and ponder things! I think that is the most important. We are all so pragmatic and want to have quick results. And our society is asking to be hurried. Everything is urgent. All is in peril. But giving in to that urge is a trap, that makes us weaker as mankind to face our wickedest problems.

Besides "Hammock driven development" mentioned in the article, #Emergence is key. And emergence is WEIRD and fascinating. I just tooted about it in..

https://social.coop/@smallcircles/116384803540561801

--

I used #SolidProject just to contrast a totally opposite approach to how fedi evolves: Fully formal #OpenStandards driven, but with risk to evolve into a 'standards maze' without ecosystem support.

#Mastodon Foundation is a new development. Hopefully they care beyond the app.

#SX #SocialCoding #SocialWeb

@woozle the article was described as "fairly long thinkpiece" by @Profpatsch which with 53 min. read time is an understatement of "fairly long" where it comes to typical online content.

Thank you for taking the time and ponder things! I think that is the most important. We are all so pragmatic and want to have quick results. And our society is asking to be hurried. Everything is urgent. All is in peril. But giving in to that urge is a trap, that makes us weaker as mankind to face our wickedest problems.

Besides "Hammock driven development" mentioned in the article, #Emergence is key. And emergence is WEIRD and fascinating. I just tooted about it in..

https://social.coop/@smallcircles/116384803540561801

--

I used #SolidProject just to contrast a totally opposite approach to how fedi evolves: Fully formal #OpenStandards driven, but with risk to evolve into a 'standards maze' without ecosystem support.

#Mastodon Foundation is a new development. Hopefully they care beyond the app.

#SX #SocialCoding #SocialWeb

I just noticed that #SolidProject website after many years still does not clearly communicate what Solid is, other than "something something advancing the web".

Luckily inventor of web and key driver of the technology effort, TBL, is quoted saying it has something to do with control of own data. Somewhere we lost "that human-first approach" that was so prevalent in the early days. And now we must go back to the roots again.

TBL even staked the whole company Inrupt he co-founded on it. Inrupt offers a *checks notes* ..

> #AI That Actually Knows Your Customers

> #ChatGPT knows a little about a lot of your customers' lives. The AI you build will know everything that really matters to your customer relationships.

Ah, I see now. We must go back to our roots. Well before the #DystopicWeb. Nom nom nom 🥕🥕 what a clear vision.

I just noticed that #SolidProject website after many years still does not clearly communicate what Solid is, other than "something something advancing the web".

Luckily inventor of web and key driver of the technology effort, TBL, is quoted saying it has something to do with control of own data. Somewhere we lost "that human-first approach" that was so prevalent in the early days. And now we must go back to the roots again.

TBL even staked the whole company Inrupt he co-founded on it. Inrupt offers a *checks notes* ..

> #AI That Actually Knows Your Customers

> #ChatGPT knows a little about a lot of your customers' lives. The AI you build will know everything that really matters to your customer relationships.

Ah, I see now. We must go back to our roots. Well before the #DystopicWeb. Nom nom nom 🥕🥕 what a clear vision.

@smallcircles @strypey @FinchHaven @naturzukunft2026

Hi, author of some things here. I can assure you that that is more of that big bad "semantic web" stuff baked into #ActivityPub than there is to #SolidProject but people spin things as they want to for a narrative. That said, totally agree with you that do x and y will come is not enough. Folks conflate various variables or attempt to boil things down to a single perspective. The reality is far more strange and unpredictable.

@smallcircles @strypey @FinchHaven @naturzukunft2026

Hi, author of some things here. I can assure you that that is more of that big bad "semantic web" stuff baked into #ActivityPub than there is to #SolidProject but people spin things as they want to for a narrative. That said, totally agree with you that do x and y will come is not enough. Folks conflate various variables or attempt to boil things down to a single perspective. The reality is far more strange and unpredictable.

@strypey @FinchHaven @naturzukunft2026

For the sake of further clarity I should point to your starting post and this text:

> we need domain-specific applications that leverage ActivityPub’s full semantic potential

And remark that in my opinion and by observation, tapping the sign "Reminder: #ActivityPub is #JSONLD, folks!" isn't enough. Much more is needed than pointing to the #OpenStandards to win back developers minds to adopt #LinkedData. There is a high reluctance and resistance to adoption that must be overcome.

Referring again to that adoption chart I drafted the other day - which is about #SolidProject, but this is where LD is strong(est?) today - "build open standards, and they will come" isn't going so well. I hope that changes, as I have always been a fan of the *notion* of the semantic web. Yet in role of a technology decision maker, not ready to bet on it for a social networking environment.

@strypey @FinchHaven @naturzukunft2026

For the sake of further clarity I should point to your starting post and this text:

> we need domain-specific applications that leverage ActivityPub’s full semantic potential

And remark that in my opinion and by observation, tapping the sign "Reminder: #ActivityPub is #JSONLD, folks!" isn't enough. Much more is needed than pointing to the #OpenStandards to win back developers minds to adopt #LinkedData. There is a high reluctance and resistance to adoption that must be overcome.

Referring again to that adoption chart I drafted the other day - which is about #SolidProject, but this is where LD is strong(est?) today - "build open standards, and they will come" isn't going so well. I hope that changes, as I have always been a fan of the *notion* of the semantic web. Yet in role of a technology decision maker, not ready to bet on it for a social networking environment.

RE: https://mastodon.xyz/@NGIZero/116160055128846646

Several #SolidProject initiatives funded!

RE: https://mastodon.xyz/@NGIZero/116160055128846646

Several #SolidProject initiatives funded!

@damon

Thank you. Yes, indeed. As it happens I was just in chat with Sébastien yesterday. They'll give a presentation at the #Solid Practitioners Meetings on the 5th of March.

#ActivityPods is positioned to bring "app development" to the intersection of the #ActivityPub and #SolidProject ecosystems, and that is very valuable. And also an #OpenStandards focused initiative.

I have revamped the #fediverse delightful lists to de-emphasize app domains and apps that have already established themselves, to highlight the innovative projects that can bring fedi to higher levels. @activitypods is on the developer list.. https://delightful.coding.social/delightful-fediverse-development/#application-development

They are well positioned to offer the 'Solution developer' stakeholders an attractive set of tools. And the opportunity is to marriage the best of 2 worlds. Which is at the same time the big challenge, coping with the worst of 2 worlds. The other day I tooted about this here: https://social.coop/@smallcircles/116113963712755122

@damon

Thank you. Yes, indeed. As it happens I was just in chat with Sébastien yesterday. They'll give a presentation at the #Solid Practitioners Meetings on the 5th of March.

#ActivityPods is positioned to bring "app development" to the intersection of the #ActivityPub and #SolidProject ecosystems, and that is very valuable. And also an #OpenStandards focused initiative.

I have revamped the #fediverse delightful lists to de-emphasize app domains and apps that have already established themselves, to highlight the innovative projects that can bring fedi to higher levels. @activitypods is on the developer list.. https://delightful.coding.social/delightful-fediverse-development/#application-development

They are well positioned to offer the 'Solution developer' stakeholders an attractive set of tools. And the opportunity is to marriage the best of 2 worlds. Which is at the same time the big challenge, coping with the worst of 2 worlds. The other day I tooted about this here: https://social.coop/@smallcircles/116113963712755122

@reiver @thisismissem @mfru

Here's the diagram btw: https://social.coop/@smallcircles/116113963712755122

The problem of #SolidProject knowing what it is, is more an inherited problem of #LinkedData / #SemanticWeb knowing what it is.

Semantic web always was "if only all information on the web were semantic and machine-readable, then...". And there it stopped. Presumably magic would happen.

And perhaps it would. But to make such a big leap, a paradigm shift of the entire web, along the way you have inspire a whole lot of people to set the (r)evolution in motion and keep it going.

If you look at what linked data is, it is a very low-level format. Nice if you have it, but now what are you going to build with it? There are some good application areas, but the case for linked data elsewhere is not a given.

Still today there are regular discussions on 'what would be the killer app for Solid' or linked data in general. Saw some interest for LLM's fed semantic data to make them more deterministic. I'm not interested.

@reiver @thisismissem @mfru

Here's the diagram btw: https://social.coop/@smallcircles/116113963712755122

The problem of #SolidProject knowing what it is, is more an inherited problem of #LinkedData / #SemanticWeb knowing what it is.

Semantic web always was "if only all information on the web were semantic and machine-readable, then...". And there it stopped. Presumably magic would happen.

And perhaps it would. But to make such a big leap, a paradigm shift of the entire web, along the way you have inspire a whole lot of people to set the (r)evolution in motion and keep it going.

If you look at what linked data is, it is a very low-level format. Nice if you have it, but now what are you going to build with it? There are some good application areas, but the case for linked data elsewhere is not a given.

Still today there are regular discussions on 'what would be the killer app for Solid' or linked data in general. Saw some interest for LLM's fed semantic data to make them more deterministic. I'm not interested.

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

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

I've been exploring opening #SolidProject files from desktop file manager/Android intents
There's a few tensions to resolve for RDF documents:

1) base uri is commonly inferred when documents are dereferenced, i.e. it's not in the document contents
2) the origin of a document may be ambiguous, particularly as Android makes it easy to share content and hard to access files
3) files with identical relative URL content can be different in absolute terms, so file deduplication needs to be RDF-aware

I've been exploring opening #SolidProject files from desktop file manager/Android intents
There's a few tensions to resolve for RDF documents:

1) base uri is commonly inferred when documents are dereferenced, i.e. it's not in the document contents
2) the origin of a document may be ambiguous, particularly as Android makes it easy to share content and hard to access files
3) files with identical relative URL content can be different in absolute terms, so file deduplication needs to be RDF-aware

@stuartyeates @mfru I think a critical mass of apps for a smaller number of users would also be ok - data sovereignty advantages can be obtained without network effects. There's still enough dev activity that the jury is out on whether this will be achieved.
#SolidProject

@stuartyeates @mfru I think a critical mass of apps for a smaller number of users would also be ok - data sovereignty advantages can be obtained without network effects. There's still enough dev activity that the jury is out on whether this will be achieved.
#SolidProject

@david_megginson @ben

Though with regards to progress, there's a difference in both approaches.

At the #SolidProject side you have inertia by the slow standardization process. But should they figure things out in a good way, eventually the ecosystem catches up and the inertia can quickly decrease.

While at #ActivityPub side, since AS/AP remains stagnant, the ever increasing protocol decay and tech debt non-linearly increases inertia and progress. And on top of that, you are never done once you implemented the 'ad-hoc specs' of the installed base, and you have to account for continuous whack-a-mole development and maintenance burdens to fix #interoperability breakages.

The AS/AP based fediverse devolves into effectively no interoperability, and a situation that is more comporative to NPM dependency hell.

@david_megginson @ben

Though with regards to progress, there's a difference in both approaches.

At the #SolidProject side you have inertia by the slow standardization process. But should they figure things out in a good way, eventually the ecosystem catches up and the inertia can quickly decrease.

While at #ActivityPub side, since AS/AP remains stagnant, the ever increasing protocol decay and tech debt non-linearly increases inertia and progress. And on top of that, you are never done once you implemented the 'ad-hoc specs' of the installed base, and you have to account for continuous whack-a-mole development and maintenance burdens to fix #interoperability breakages.

The AS/AP based fediverse devolves into effectively no interoperability, and a situation that is more comporative to NPM dependency hell.

@david_megginson @ben

Yes, I agree. Though the diagram is too simple to capture it well, it is important to identify the forces that are at play, and the mechanics that drive them, and to subsequently monitor where you are and where you want to be in the future. So timely action can be taken to make corrective actions.

For the #SolidProject ecosystem for instance they might have identified a minimum set of standards to adopt, with which reasonably powerful "MVP's of the Semantic web" could be approximated with. And focus on strong library and tool support for that in multiple programming environments. Instead you enter a jungle of open stardards in various stages of completion, and good luck go figure it out. Also they might've focused on actual movement building. Far-reaching innovative standards - a new paradigm for the web - aren't adopted by the boardroom of a company, but are introduced by devs who get excited by what see and how they are empowered. And persuade management.

@david_megginson @ben

Yes, I agree. Though the diagram is too simple to capture it well, it is important to identify the forces that are at play, and the mechanics that drive them, and to subsequently monitor where you are and where you want to be in the future. So timely action can be taken to make corrective actions.

For the #SolidProject ecosystem for instance they might have identified a minimum set of standards to adopt, with which reasonably powerful "MVP's of the Semantic web" could be approximated with. And focus on strong library and tool support for that in multiple programming environments. Instead you enter a jungle of open stardards in various stages of completion, and good luck go figure it out. Also they might've focused on actual movement building. Far-reaching innovative standards - a new paradigm for the web - aren't adopted by the boardroom of a company, but are introduced by devs who get excited by what see and how they are empowered. And persuade management.

I recreated an old diagram in Excalidraw that I spread about a couple years ago, and made it a bit more informative. Explanation can be found in the #AltText

See also and for discussion: https://discuss.coding.social/t/diagram-interoperability-in-practice/828

Or join the Social experience design chatroom at: https://matrix.to/#/#socialcoding-foundations:matrix.org

Also posted to #SocialHub at: https://socialhub.activitypub.rocks/t/activitypub-versus-fediverse-interoperability-in-practice/8498

@ben

#SX #SocialCoding #SocialWeb #ActivityPub #SolidProject #fediverse

I recreated an old diagram in Excalidraw that I spread about a couple years ago, and made it a bit more informative. Explanation can be found in the #AltText

See also and for discussion: https://discuss.coding.social/t/diagram-interoperability-in-practice/828

Or join the Social experience design chatroom at: https://matrix.to/#/#socialcoding-foundations:matrix.org

Also posted to #SocialHub at: https://socialhub.activitypub.rocks/t/activitypub-versus-fediverse-interoperability-in-practice/8498

@ben

#SX #SocialCoding #SocialWeb #ActivityPub #SolidProject #fediverse

@virtualpierogi @sri @jsalvador @ben @nlnet

It needs concerted effort, as argued in my blog post, to set all of this up. Things can start small and pragmatic, and then gradually evolve and mature, but we should take care it evolves in the proper direction.

There are trade-offs to consider every step of the way. If there'd more capabilities to introspect the functionality that an #ActivityPub actor offers, it would diminish the need for an upfront design-by-consensus process, but it would increase the complexity of the specifications.

I drew this in a diagram a couple years ago, and transferred it to our social coding forum at: https://discuss.coding.social/t/wiki-grassroots-standardization-processes/672?u=aschrijver

Here you see the fediverse devolve into non-interoperable app-by-app whack-a-mole development, keeping track of all the moving-target #FOSS projects one took a dependency on. Versus the #SolidProject that tries to hammer out full-blown specs upfront, which became a huge package to deal with, with high complexity to implement.

@virtualpierogi @sri @jsalvador @ben @nlnet

It needs concerted effort, as argued in my blog post, to set all of this up. Things can start small and pragmatic, and then gradually evolve and mature, but we should take care it evolves in the proper direction.

There are trade-offs to consider every step of the way. If there'd more capabilities to introspect the functionality that an #ActivityPub actor offers, it would diminish the need for an upfront design-by-consensus process, but it would increase the complexity of the specifications.

I drew this in a diagram a couple years ago, and transferred it to our social coding forum at: https://discuss.coding.social/t/wiki-grassroots-standardization-processes/672?u=aschrijver

Here you see the fediverse devolve into non-interoperable app-by-app whack-a-mole development, keeping track of all the moving-target #FOSS projects one took a dependency on. Versus the #SolidProject that tries to hammer out full-blown specs upfront, which became a huge package to deal with, with high complexity to implement.

I finally have a git setup I'm happy with when coding on mobile on a #SolidProject pod

PUTting .git/COMMIT_EDITMSG triggers add & commit via a Solid Notifications webhook

Using vitest for unit testing with ESM support.
Getting closer to TDD in the browser.

I finally have a git setup I'm happy with when coding on mobile on a #SolidProject pod

PUTting .git/COMMIT_EDITMSG triggers add & commit via a Solid Notifications webhook

Using vitest for unit testing with ESM support.
Getting closer to TDD in the browser.

@naton There's a fairly active community on several matrix channels including one for practitioners
https://github.com/solid-contrib/practitioners
#SolidProject

@naton There's a fairly active community on several matrix channels including one for practitioners
https://github.com/solid-contrib/practitioners
#SolidProject

@douginamug Yes, you can self-host a #SolidProject server, including directly from your device

e.g. You can Community Solid Server locally or with a production setup:

https://github.com/mrkvon/css-setup

There's also an experimental desktop app: https://github.com/SolidOS/data-kitchen

Some apps are local first or have caching, so the pod doesn't need to be always accessible

@douginamug Yes, you can self-host a #SolidProject server, including directly from your device

e.g. You can Community Solid Server locally or with a production setup:

https://github.com/mrkvon/css-setup

There's also an experimental desktop app: https://github.com/SolidOS/data-kitchen

Some apps are local first or have caching, so the pod doesn't need to be always accessible

Wohoo! Hello world Solid!
Just deployed my own pod ☺️🚀
#LDP #SolidProject #LinkedWebStorage

Wohoo! Hello world Solid!
Just deployed my own pod ☺️🚀
#LDP #SolidProject #LinkedWebStorage

I've been experimenting with #SolidProject agents and I like the elegance of https://github.com/solidcouch/solid-identity - the agent hosts its own webid and issuer - no login required, instead the user just grants access to the agent webid

I've been experimenting with #SolidProject agents and I like the elegance of https://github.com/solidcouch/solid-identity - the agent hosts its own webid and issuer - no login required, instead the user just grants access to the agent webid

Been playing with #solid apps again today. Love the way personal data is separated from the app. Has to be the way forward. Particularly good is the recipe cookbook from https://umai.noeldemartin.com/

Also managed to locally install the demo app linked to my pod. Just got to figure out how I can use this in the real world.

#solidproject

Been playing with #solid apps again today. Love the way personal data is separated from the app. Has to be the way forward. Particularly good is the recipe cookbook from https://umai.noeldemartin.com/

Also managed to locally install the demo app linked to my pod. Just got to figure out how I can use this in the real world.

#solidproject

The Solid Project

After creating a Solid Pod I found a great app created by @noeldemartin for saving, storing and viewing cooking recipes. The workflow is
1. Create a pod
2. Login to the app via pod credentials
3. Use the app to scrape recipe URLs, import via JsonLD or create from scratch
4. All recipes get synced to the pod

This is the 3rd app I have logged into, via my pod, where the data is stored on the pod. The data is mine and I can revoke access at any time. It's a different way of working to how big tech works but it feels like I have full control.

#solidproject

The Solid Project

After creating a Solid Pod I found a great app created by @noeldemartin for saving, storing and viewing cooking recipes. The workflow is
1. Create a pod
2. Login to the app via pod credentials
3. Use the app to scrape recipe URLs, import via JsonLD or create from scratch
4. All recipes get synced to the pod

This is the 3rd app I have logged into, via my pod, where the data is stored on the pod. The data is mine and I can revoke access at any time. It's a different way of working to how big tech works but it feels like I have full control.

#solidproject

I've always kept tabs on what the Solid Project has been doing, partly because of the involvement of Sir Tim Berners-Lee. In theory it is an exciting project BUT I opened a pod today for the first time in a couple of years and it seems not much has changed.

https://solidproject.org/

#solidproject

I've always kept tabs on what the Solid Project has been doing, partly because of the involvement of Sir Tim Berners-Lee. In theory it is an exciting project BUT I opened a pod today for the first time in a couple of years and it seems not much has changed.

https://solidproject.org/

#solidproject

My experimental #SolidProject webhook config now also has an indexer that adds new schema:Action tasks compatible with https://focus.noeldemartin.com to an ItemList

Works well with additions to a container, but listening to edits would require subscribing to updates from individual documents.

I'm still regenerating the index daily as well and currently thinking of it as an index that provides eventual consistency. The consumer should assume updates and deletions/tombstones may be missing.

My experimental #SolidProject webhook config now also has an indexer that adds new schema:Action tasks compatible with https://focus.noeldemartin.com to an ItemList

Works well with additions to a container, but listening to edits would require subscribing to updates from individual documents.

I'm still regenerating the index daily as well and currently thinking of it as an index that provides eventual consistency. The consumer should assume updates and deletions/tombstones may be missing.

TIM BERNERS-LEE ÍN HÊN ĐÊN CÙA SỐ OÀN SOLID NÊUÊN TIÊN VÊN DÊN HÀNH LÍCH. THỰC VƯƠNG KÊTN TINH NGỌI SOLID XUÂY DỰNG MÁY LÁY CỘN CÙA VÀ LỊNH SỒNG MỘI. ĐÃY LÀ CỐI PHÚ CÔNG NHẬT CÙA MỘI! #SelfHosting #SolidProject #ThôngTin

https://www.reddit.com/r/selfhosted/comments/1pg84yg/just_found_out_about_solid/

Have you booked for the final Solid World of the year? It will include updates from the Solid Practitioners Group (PG), the Solid Community Group (CG) and the Linked Web Storage Group (LWS). We're also delighted to welcome Frederik Byl (Vito), who will present on two innovative projects leveraging Solid for sharing health data.
https://www.eventbrite.co.uk/e/solid-world-december-2025-tickets-1702624067419?aff=oddtdtcreator

#SolidWorld #SolidProject #PersonalData #ODI #HealthTech

Have you booked for the final Solid World of the year? It will include updates from the Solid Practitioners Group (PG), the Solid Community Group (CG) and the Linked Web Storage Group (LWS). We're also delighted to welcome Frederik Byl (Vito), who will present on two innovative projects leveraging Solid for sharing health data.
https://www.eventbrite.co.uk/e/solid-world-december-2025-tickets-1702624067419?aff=oddtdtcreator

#SolidWorld #SolidProject #PersonalData #ODI #HealthTech

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

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

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

#Solid Symposium will take place in #London in Spring 2026

The Symposium brings together individuals from science, business, the public sector and academia to discuss and learn about the latest developments in Solid and related technologies in the Linked Web.

https://theodi.org/news-and-events/news/announcing-the-solid-symposium-2026/

#SolidProject #LinkedData #Web

#Solid Symposium will take place in #London in Spring 2026

The Symposium brings together individuals from science, business, the public sector and academia to discuss and learn about the latest developments in Solid and related technologies in the Linked Web.

https://theodi.org/news-and-events/news/announcing-the-solid-symposium-2026/

#SolidProject #LinkedData #Web

RE: https://mastodon.social/@jg10/112911946823132168

I'm increasingly convinced there's value in a #SolidProject server cooperative built on trust and aimed at providing a high quality service one would feel comfortable recommending to family and friends.

Value comes when data flows - accumulating it in a pod is not enough. A medium sized cooperative would provide the end users, resources and stability to develop high value data flows that would demonstrate why data sovereignty is worthwhile.

Still a lot of work to be done to scope a MVP though.

RE: https://mastodon.social/@jg10/112911946823132168

I'm increasingly convinced there's value in a #SolidProject server cooperative built on trust and aimed at providing a high quality service one would feel comfortable recommending to family and friends.

Value comes when data flows - accumulating it in a pod is not enough. A medium sized cooperative would provide the end users, resources and stability to develop high value data flows that would demonstrate why data sovereignty is worthwhile.

Still a lot of work to be done to scope a MVP though.