Should We Build It or Bridge It? The MATO Problem and What Germ Network Changes

Token: I’m Leaving Soon Tour at Green Room in Minneapolis

Boston rapper Token brings the I’m Leaving Soon Tour to Green Room. Known for technical lyricism and tracks like "Household Name," "Flamingo," and…

I found MATO while doing promotion for Token's I'm Leaving Soon Tour at Green Room Minneapolis. If you don't know MATO — it's an underground event discovery platform. "Unpolished. Unfiltered. Unapologetic." Their pitch is surfacing the city's rawest cultural moments. Their infrastructure is built on Instagram handles and ActivityPub.

That last part is the problem.

What I Actually Need

I.B. Loud is a social network DJ. That's her cover. What she actually does is move through cities, find where culture is alive, connect communities, and try to stop a planet from hitting the same breaking point that killed Saturn — while a competing corporation waits to absorb the solar system.

For that story to work in the real world, I need event discovery infrastructure that lives in the same ecosystem as everything else I'm building. I need it to be AT Protocol-native. I need it to respect the privacy model we've built into Veiled Dominion — your data lives on your server, not ours.

MATO is beautiful. But it's built on Instagram's API and ActivityPub's fragmented discovery model. Every venue they list is dependent on Instagram continuing to allow access. Every event they surface is a piece of data owned by a platform that has every incentive to eventually charge for it, restrict it, or make it disappear behind an algorithm.

That's exactly the kind of infrastructure I.B. Loud is supposed to be working against.

The Question I Was About to Ask

I was drafting an email to MATO's support team asking whether they'd considered AT Protocol as a foundation — whether they'd looked at building event discovery on a model where venues own their data, where a DID is the venue's identity, where an event record lives on a Personal Data Server instead of an Instagram post.

The email was going to include dev documentation:

• Protocol overview: atproto.com/guides/overview
• How to define custom record schemas (lexicons): atproto.com/guides/lexicon
• Jetstream for real-time event discovery: github.com/bluesky-social/jetstream

It was a peer builder pitch. One protocol believer to a team that clearly cares about authentic culture but hasn't made the infrastructure choice yet.

Then Germ Network Showed Up

While I was drafting that email, Germ Network liked two of my posts on Bluesky and said: "Hmmmm I wonder how we can incorporate our apps together? Wanna play?"

Germ is different from MATO in one critical way: they're already building on AT Protocol. Their Bluesky integration is in public beta. They're building quantum-secure end-to-end encrypted DMs linked to your AT Protocol handle. Multiple profiles, no phone numbers, mutual opt-in connections, no recommendations or introductions without consent. Their tagline is "Free your DMs." Their roadmap includes full-featured DMs from your AT Proto handle and eventually Android.

They're not the competition. They're a potential infrastructure layer for exactly what I.B. Loud needs — a way for communities to find each other and communicate without the data living somewhere it doesn't belong.

The Actual Decision

So now the question isn't "should I email MATO" — it's three questions:

Option 1: Email MATO's support team and ask whether they're open to an AT Protocol integration path. The risk: they're fundamentally built for Instagram's ecosystem. A pivot to ATProto isn't a feature add, it's an architectural shift. They may not be interested. They may not be able to.

Option 2: Build the event discovery feature ourselves using AT Protocol's native tools — a custom lexicon for events, Jetstream for real-time discovery, a feed generator as the discovery layer. This is technically achievable. It's also significant scope on top of an already active build list. But it means the infrastructure belongs to us and to the community, not to any platform.

Option 3: Build with Germ Network — respond to their invitation, explore what "incorporating our apps together" could mean. Germ has E2EE DMs on AT Protocol. We have a game ecosystem, a lore world, a matchmaking layer, and a community organizing around physical events in cities. A Germ-powered communication layer underneath a Veiled Dominion event network is a coherent stack. And they reached out first.

Where I'm Landing

Option 3 is the conversation worth having right now. Not because it's the easiest — but because Germ is already doing the hard AT Protocol infrastructure work on the messaging side, which is the part we'd be slowest to build well. They need a community and a use case. We need a communication layer that respects our privacy model.

Option 2 is still on the table for event discovery specifically — a custom events.loptr.define lexicon isn't out of scope for a later build sprint, and it would make the Veiled Dominion physical hackathon events discoverable across the AT Protocol ecosystem the same way Veiled Dominion: Duet is discoverable on atmosphere.games.

Option 1 — the MATO email — becomes less urgent but not irrelevant. MATO is good at what they do and they're in the cities where culture is actually happening. If they ever want to talk AT Protocol, the documentation is ready.

What This Has to Do with the Story

Urban Alien Adventures is the travel agency for the corporation gentrifying Gaia. I.B. Loud's cover is a social network DJ. Her real job is triage — finding the raw cultural moments before they get extracted, commodified, and used to destabilize a planet.

The infrastructure question isn't separate from the lore. It's the same question the story is asking: who owns the network the culture runs on?

MATO built something beautiful on infrastructure they don't control. That's the story of every artist, venue, and community that built on Instagram and then watched the algorithm decide whether anyone saw their work.

We're building on AT Protocol because the answer to that question matters. And apparently Germ Network is building there for the same reason.

Next step: reply to Germ Network's Bluesky message and find out what "incorporating our apps together" actually means to them.

— PIXIE devlog, Loptr Lab