Hi, I wanted to chime in from over on https://forum.solidproject.org/
Adding knowledge aggregation in principle comes fairly cheaply from a linked data platform / Solid perspective. The intention is that multiple apps even with different purposes can be backed by the same data, so knowledge aggregation is mostly about ensuring that it appears in the right index.
I’m new to fedeproxy, and keen to see how it could integrate/provide a bridge with the issue management system being developed in the Solid context, and therefore feed into this knowledge aggregation process.
The “Issue-pane” is a (still immature) UI component that provides card and table views of issues: https://github.com/solid/issue-pane/blob/main/Documentation/Configuration.md
It uses the workflow ontology to model issues, including a message store.
In principle messages could include further linked data, which lends itself to further manipulation of issue discussion content.
In a knowledge aggregation or federation context, new issues or messages could either be added directly by a dev-ops bot (mentioned over on Lemmy), or could be staged for review by being labelled with an initial state or category.
I’ll try to get my head around how fedeproxy would fit in here, but any suggestions are welcome…