Rented platforms, real patients: why our support spaces need network sovereignty
Most of the systems we lean on aren't collapsing in flames. They're dissolving into dependencies. We built our communities on platforms we don't control, APIs we don't own, algorithms we can't see and identities we rent. Patients became "users", conversations became "engagement", and the infrastructure became someone else's problem.
I didn't think much about any of this until a patient support group I helped moderate on a big social platform lost most of its reach overnight after a feed change. People who had relied on that group between appointments simply stopped seeing it. Nobody had done anything wrong. The rules had just moved under us.
A feed is not a network
A feed is a broadcast stream tuned for attention. A real network, the kind a caregiver or a newly diagnosed patient needs, has things most platforms only simulate:
- Identity with context: who someone is in this group, not just a username
- Permissions with nuance: who can see a post about a diagnosis, and who can't
- Communication with memory: last year's thread on side effects is still there when someone needs it
- Governance with rules the community sets and can change itself
When those pieces are missing, communities fall apart the moment friction appears, and every new group starts again from zero.
Why it matters more in health communities
The stakes are higher when the people in the room are vulnerable. If the data lives somewhere that doesn't answer to the community that created it, privacy is a promise someone else can revise. And as AI tools start acting on top of these platforms, they inherit the same weakness: no durable memory, no structured permissions, and access that can be revoked overnight.
Building on something we own
That's why the Patient Support Network and Caregivers Connect live here, on UNA, rather than on a rented page. UNA treats accounts, profiles, roles, permissions, groups, messaging and events as building blocks rather than features bolted onto a feed. As a moderator, I can decide exactly who sees what, and know the answer won't change because a company changed its mind.
Every generation chooses its infrastructure. We can keep renting engagement machines, or we can build networks that communities own and govern. For the people I see in clinic, who need each other between appointments, I know which one I'd rather offer.
Info
html
asdasdasd
-
-
·
Tim Adebayo
- ·
-
·
Tim Adebayo
-
-
·
Tim Adebayo
- ·
-
·
Tim Adebayo
-
- · Jackson Reyes
- ·
Reading this from the dev side, the bit about rented identities hits hardest. Half my client work is sync jobs that copy members out of some SaaS tool they never really owned. With headless UNA the profiles, roles and permissions live in one place, and the Next.js front end just asks for them. Fewer 2am pages for me, too.
