Pull conflict into shared space (#openprocess #4opens #trustflows)

Poison thrives in private channels, so you gently but consistently move things:

from DMs → into group threads
from whispers → into meetings
from vague → into specific

This doesn’t eliminate conflict, it grounds it. Sunlight doesn’t solve everything, but it stops the worst rot.

With the #Trustflows community, we’re launching #TrustTriggers:

A new event series combining a cross-domain Trustflows topic, a long networking break, and 3 concrete use cases.

First edition: 20 April at De Krook in Ghent. With curator @besteves4 hosting a discussion on the EUDI with invited keynote speaker Jan Lindquist.

We’ll also discuss use cases such as DPP, local council decisions, and trigger in the water domain.

Program and registration: https://trustflows.eu/events/2026/04/trust-triggers-1/

Today we’re welcoming Flanders’ top researchers in Data and AI in Ghent for the closing event of #SolidLab. Where we’re continuing the community under a new name, #Trustflows.

We’re still working on #interoperability, but we’re now adding #legalcompliance and #trust as major drivers. Trustflows continues the mission we started with Solid.

Want to know more? Take a look at the website: https://trustflows.eu

Next Monday we’re organizing the closing event of the SolidLab research project in De Krook - Ghent, where we’ll launch our next steps with the #Trustflows community.

Registration and program: https://solidcommunity.be/events/solidlab-closing-event/

The charter of the new community:
https://trustflows.eu/charter

Then @julianrojas will be presenting our poster on #Trustflows, a new operational model for the read–write Web of Data. By combining CQRS and Event Sourcing with Linked Data, it decouples reads and writes, supports evolving data models, and adds explicit trust contexts. Validated in the PACSOI health data use case.

Paper: https://ceur-ws.org/Vol-4085/paper37.pdf

#iswc2025

Compost lies using #4opens horizontal networks

Pull conflict into shared space (#openprocess #4opens #trustflows). Poison thrives in private channels, so you gently but consistently move things: from DMs → into group threadsfrom whispers → into meetingsfrom vague → into specific This doesn’t eliminate conflict, it grounds it. Sunlight doesn’t solve everything, but it stops the worst rot. From “how do we stop bad behaviour?” To “how do we stop bad behaviour from breaking the commons?”. The #4opens makes many people […]

https://hamishcampbell.com/we-compost-lies-to-build-4opens-rooted-local-horizontal-networks-of-resistance-and-renewal/

I then presented a new method to take on data exchange projects called “Trustflows”. With #Trustflows, one creates specifications that start from a description of the write process, and which then explains how each write gets translated into multiple read interfaces.

Ben De Meester then applied this idea of Trustflows to a very specific case in personal health management within the PACSOI project (in collaboration with Byteflies and FAQIR Foundation).