Enter the BobaFujoVerse™

Behold, an ecosystem!

Published on January 9, 2024

Table of Contents

What is the BobaFujoVerse™

The FujoVerse™1–previously known as The BobaVerse™2–is “an eclectic collection of projects related to coding, community and fandom3 on the web”. In this series, I want to give an eagle-eye-view of this ecosystem, and how it works to accomplish its goal: turn the web back into a place of fun, joy, and connection, where people build and nurture their own communities and software.

Slide 7:

Where Are We At: BobaVerse™ Edition

in case you lost track of all we’ve been working on until now

(you’d be extremely excused)

let’s just say it’s been an intense… 3 years or so

BEHOLD, the BobaVerse™!

A Venn diagram of sorts, with overlapping circles in the center ("Long-term
projects" and "April 1st jokes") as well as a rectangle on the left ("Test boba
galaxy") that partially overlaps with Long-term projects, and another square off
to the right ("side projects") that does not overlap with anything else. 

Long-term projects contains the logos for BobaBoard and Fandom Coders (a pair of
lime green braces that enclose the statement "if fandom then coding"), and in
pink text the comment "ms boba getting paid for her time, aka "Patron income"
(again, thank you)". 

The Fujoshi Guide to Web Development spans across the intersection of Long-term
projects and April 1st jokes. 

April 1st jokes also includes the logo for FujoBoard (Boba-tan licking her lips)
and purple text for RobinBoob by BobaBoard.

Fandom Coders is located where the "Test boba galaxy" rectangle overlaps with
Long-term projects. Also within the rectangle are "the Boobies" (BobaBoard
enthusiasts, represented by a real-life photo of the marine birds blue-footed

In the "side projects" square are AO3.js (in the red and white scheme of Archive
of Our Own) and Tim the Enchanter from Monty Python and the Holy Grail [**VALE

“The BobaVerse™ is an eclectic collection of projects related to coding,
community and fandom on the web that may or may not create a sustainable
ecosystem one day” — definition ms boba just made up on the fly but that
actually kinda works

Slide introducing the FujoVerse™, from the first edition of my quarterly(ish) newsletter

Want to read (or share) on socials?

The Pillars: Community, Software Ownership, and Technical Education

The FujoVerse™ projects evolved over time, based on what I learned building each piece, making friends and allies, and reading anything I could find on related topics. While ambituous goals that tackle complex systems cannot have too-tight roadmaps, these efforts have hovered around a few fundamental pillars:


There’s many issues that come together to make the modern web feel like a “joyless landscape”, but a core and often-underestimated problem is the abscence of true communities. Indeed, while the hyper-connectedness of contemporary social online spaces may trick us into seeing these as such, their shape makes it hard (if not impossible) to build the necessary group identity, shared norms, and mutual concern between their members4.

Research shows that the lack of true community heavily contributes to loneliness and social isolation we feel in the modern days, even in the online world. This adds to the disenfranchisement felt by many users, and keeps them disempowered and stuck in a loop of helplessness and often-misdirected anger at one another. (Re)building communities is required to change how we feel and interact on the web.

Software Ownership and Collaboration

The needs of niche online communities are, well, niche. While software built by big tech companies is increasingly at odds even with mainstream users, the current dynamics disproportionately impact marginalized groups and communities. To build software that responds to their own needs, members of niche communities must be able to shape this software themselves.

As we know, however, this challenge is not only technical5: solving it means building structures and processes for constructive collaboration, both within each community and accross different ones. Unfortunately, effective collaboration requires both trust and psychological safety. As communities erode, and the web and social systems break down, building safe, stable spaces for collaborative work (an already-difficult problem) becomes more and more complex.

Education (Technical and Beyond)

To shape their own spaces, members of niche online communities need to know how to build and maintain their own software. Unfortunately, most educational material for web developers targets people who seek a professional career, or hardly moves past simple HTML and CSS pages (with maybe a sprinke of basic JavaScript)6. To change the web, we need highly-technical education that speaks the language of hobbyists, supports and encourages their desire for mastery, and carries them across the gap from beginner to intermediate builders.

Once again, the need for education goes beyond the technical realm: from community building to conflict resolution, from negotiation to effective (and kind) communication, from marketing to business to project management, niche communities need many different skills to build a better future for themselves and the web. In a world that doesn’t equip many of us with these skills, we must build approachable and trusted resources to learn them from.

Note: In more than one way, these pillars also intersect with open source software and decentralized protocols.

The Future: Help Build the FujoVerse™

Despite all that we’ve already built, The FujoVerse™ is still in its inception. We have a long road ahead of us to support the collaborators that make our project possible, and to continue making an impact in 2024 and beyond. To this end, this year I’m focused on building a larger public to find new supporters and sponsors. If you believe that a better web is worth fighting for, you can support our work on Patreon or by subscribing through my own alternative. If you wish to donate more, you can reach out to set up a custom sponsorship.

In the long term, given the opportunity and finances to do so, we believe we can build profitable projects that will be able to independently sustain our mission. After all, the people who contribute to The FujoVerse™ have a unique perspective that speaks to the needs of the web and its netizens in a way that no mainstream company can replicate. While the road to manifesting and harnessing their power will be difficult, nothing ambitious has ever looked easy from the starting line.

Slide 10:

what we’re trying instead (extreme WIP edition)

i call it “take it slow and pray” ("and pray" is struck out)

1. Kickstart a series of aspirationally-independent software, educational,
and/or community initiatives that are of interest to niche online communities

2. Use these initiatives to train the niche user base in the skill needed to
continue maintaining and improving them (starting with transformative fandom!
incredibly strategical reason: it’s the niche I’m personally in)

2a. Enable motivated members of the userbase to have direct impact on the
direction of each project (and to go start their own)

2b. Lower costs and nurture the community by offering skill-training from
experts in exchange for help (intrinsic motivation, baby)

2c. Get to play that “diversity initiative” card when asking for grants
(education grants = take focus away from BobaBoard itself, making it less likely
that we’ll have to justify the proliferation of a/b/o on it)

3. Reinvest income resulting from donations + for-profit projects that might
(one day) hit it big, and continue nurturing that ecosystem 

3a. With the support of a small, core team of skilled, full-time, paid personnel
(which we aren’t even close to affording right now, money is the bit that keeps
me up at night tbh, my bank account has been falling for so long that (insert
Loki joke this slide is too overdue to finish) ANYWAY, more later

3b. Source core team and contract talent from the community grown at step #2 to
reduce risk and ensure cultural alignment, repeat, profit

…aka, “The BobaVerse™”

Slide explaining the masterplan, from the first edition of my quarterly(ish) newsletter

Like what you read? Help by sharing it on socials!


  1. Not a real trademark

  2. Also not a real trademark

  3. “Fandom” should be considered a stand-in for ”niche online community”. While my work centers around “transformational/shipping fandom” (because that’s my own online niche), the projects, principles and lessons are applicable beyond it.

  4. This will be an article at some point. For now I suggest reading The Art of Community, or (if you can stomach business speak) the excellent Building Brand Communities, from the same author.

  5. The challenge is not only technical, but it is (alas) also technical. A baseline of technical skills and understanding empowers people in other roles to become more active and informed partecipants. It’s important that we nurture these skills, just like we must nurture non-technical skills in tech-oriented folks.

  6. Sometimes people push against this point by listing various existing resources. However, after spending three years and counting mentoring hobbyist coders and nurturing a community dedicated to their growth, I continue being confident in this assessment.