Discussion
Loading...

Post

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
witchescauldron
@witchescauldron@kolektiva.social  ·  activity timestamp last week

What do we really need:

A user-controlled blob of data that syncs across devices.

A conflict resolution flow (because yes, sync is hard, but solvable if you design for it).

A protocol path that is not “just another cloud,” but part of a commons.

This is what the #OMN path is sketching out:

Bridging client/server with #p2p flows.

Giving people the power to hold their own history (rather than leasing it back from Google/Meta).

Doing this inside a trust-based #4opens framework (#OpenData, #OpenSource, #OpenStandards, #OpenProcess).

Keeping it #KISS so a normal-ish human can understand what’s happening.

It’s not “a new app.” It’s plumbing — the pipes and tanks that allow history, content, and flows to move while staying in your hands.

Not the same as a sync library, but the same path: moving from stranded silos → cloud capture → trust-based decentralisation.

#KISS

  • Copy link
  • Flag this post
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.0-rc.2.21 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login