Making Community Governance Legible: A Semester with Bonfire

By Sohyeon Hwang

Authors: Sohyeon Hwang (Princeton University), Andrés Monroy-Hernández (Princeton University)

Most of us have spent the last two decades living inside platforms we have little control over. A handful of companies tune algorithms, moderate content, and set policies. Operating at “unfathomable” scales, this comes at a cost: it constrains diverse communities to a single set of rules, leaves little room for local values or context, and gives people almost no visibility — or voice — into decision-making.

An exciting new wave of networks and systems have sought to create alternative spaces for digital life. But alternatives that are not only viable but also sustainable demands moving beyond software. It means rethinking how we organize within these spaces, govern them, and make decisions about them collectively; it also means building tools that support iteration, deliberation, and experimentation along those lines, rather than presuming what should come next. In the Spring 2026 semester course “Designing Protocols” (EGR 373), students had the chance to dig into exactly that problem in collaboration with community partners, including Bonfire. Bonfire is an open-source, modular framework that provides a platform for building online spaces and social networks owned and governed by communities, giving users greater autonomy and control over their digital lives. 

Creating an interface for “Governance Cards”

One of the EGR 373 projects, “Community Governance Cards,” was led by ECE major Prishaa Kapasi (‘29), with support from MSE student Michelle Le (‘27). As part of our broader project CROW (“Community Rules for an Open Web,”) this project was based on research findings from design workshops with fediverse folks that the Princeton HCI lab ran last year, published at CHI’26. A key idea in the workshops was inspired by tools like CC licenses or Model Cards: give communities a concise, structured way to document how they govern themselves, across core dimensions like infrastructure, membership, rules, and so on. Whereas this information is typically informal, scattered, or entirely undocumented, Governance Cards become a simple and consistent way of sharing norms and context.

We were lucky enough to team up with Bonfire to translate Governance Cards from an abstract idea into a prototype that can be used in actual communities. The student team met with the Bonfire team periodically throughout the semester, with our conversations circling back to two central questions.

What do people actually need to set up and articulate? Intuitively, we know that governance isn’t one-size-fits-all! Neither is the language communities use to describe what they do. A big part of this work was simply figuring out which dimensions of governance actually matter to communities and finding vocabulary flexible enough to fit diverse communities that might be wildly different, specific, or distinct. Regular discussions to iterate on the schema pushed us to sync up social and organizational dimensions with the actual affordances the software provides, as well as raised new ideas of what the software might support. 

rules interface

The rule-selection interface was a good example of this in practice. We started with the fuzzy question of “what does a community allow or disallow?”. After analyzing 200 or so rule sets from a random sample of Fediverse communities, we developed a structured, comparable set of choices, adding options that still made it possible for communities to express nuance about their own specific norms. In a test version, Bonfire was able to implement this interface into the platform software, making it much easier for Bonfire communities to draft an initial set of rules.

crow rules screenshot

How should the data actually be shared? Once people fill out a Governance Card, a question that remained was how that information should be stored. Governance Cards are a kind of documentation, and documentation is only useful if it’s usable (for example, by the administrators filling it out, by prospective members trying to evaluate a community, and eventually by other tools and platforms assessing compatibility). That meant thinking hard about data formats (Bonfire suggested JSON-LD as a way to make Governance Cards both machine-readable and interoperable across systems) and about privacy (governance information can be sensitive). In future extensions of this project, we’ll experiment with how to support multiple levels of visibility rather than treating all governance data as equally public.

What’s next

Working with Bonfire gave us a testbed for this work, grounded in the real constraints of software and their experience with communities using their platform. We’re excited to continue working with them to finalize a data schema and define privacy settings for card-sharing, as well as to design a visual representation of a Governance Card that people can display on their communities.

Stay tuned for:

  • The release of the prototype, which will live at crowcards.org
  • Our announcement for community workshops that you can sign up for!

Further Reading: 

Sohyeon Hwang studies how users shape the governance of digital technologies. Her work focuses on online communities as a valuable point of collective decision-making and organizing to anticipate and respond to potential platform harms. In her projects, she leverages mixed methods to understand how community governance can be better supported so that everyday people have greater autonomy in addressing pressing issues such as those around online safety, information integrity, and algorithmic bias.


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *