What if your GitHub identity wasn’t just a developer profile?
What if it became the foundation of a persistent digital character — an identity that can build, contribute, own a history, interact with AI agents, and move through a digital ecosystem?
That is one of the ideas behind MyZubster.
We are experimenting with a different interpretation of the metaverse.
Not a giant 3D world owned by one company.
Not an account trapped inside a game.
Instead:
GitHub becomes part of the infrastructure of the world.
And MyZubster becomes the identity layer on top of it.
- Start with an identity you already own
The onboarding flow begins with GitHub.
A user connects their GitHub account through OAuth.
GitHub
↓
OAuth
↓
MyZubster Identity
↓
Digital Character
GitHub gives us a useful starting point because an identity there can already have a public, verifiable history:
repositories
commits
contributions
projects
collaborations
open-source activity
Instead of asking somebody to create an empty metaverse profile, MyZubster can connect a new digital identity to an existing technical identity.
- Your account becomes a character
After authentication, the interesting part begins.
A MyZubster identity can be represented as a digital character.
Think of it as the visual and interactive representation of your identity.
For example:
{
"identity": "myzubster-user",
"github_verified": true,
"character": {
"mission": "Build technology for humans and nature",
"traits": [
"builder",
"open-source",
"explorer"
]
}
}
The avatar is therefore not supposed to be just a profile picture.
It becomes a human-readable representation of an identity.
GitHub provides one source of verifiable information.
MyZubster provides the character and interaction layer.
- GitHub becomes part of the world state
This is where our definition of “metaverse” starts becoming different.
Traditionally, a metaverse platform stores almost everything in proprietary infrastructure.
We can invert that idea.
Parts of the MyZubster ecosystem can exist as normal software artifacts:
Git repositories
├── identities
├── characters
├── assets
├── protocols
├── agents
├── environments
└── world rules
Changes can therefore become commits.
Experiments can become branches.
Features can become pull requests.
Community discussion can happen through issues.
Parts of the history of the world can be inspectable.
The metaverse starts looking less like a closed game server and more like an open-source digital civilization.
- A Pull Request can change the metaverse
This is one of my favorite implications.
Imagine a community proposing a new digital object, species, environment or protocol.
Instead of silently modifying a proprietary database, the proposal could follow an open-source workflow:
Idea
↓
Issue
↓
Branch
↓
Implementation
↓
Pull Request
↓
Review
↓
Merge
↓
New part of the ecosystem
The development process itself becomes part of the world-building process.
That gives us something many virtual worlds lack:
provenance.
We can know who proposed something, who built it, what changed and when it entered the ecosystem.
- Humans aren't the only inhabitants
MyZubster is also exploring AI agents as participants in this ecosystem.
That creates another interesting model:
Humans
↕
Digital Characters
↕
AI Agents
↕
Open Protocols
↕
GitHub
An agent doesn't necessarily need to exist only inside a chat window.
It could have an identity, capabilities, history and relationships with other entities.
Humans could create characters.
Developers could create agents.
Agents could interact with services.
Repositories could describe parts of their behavior.
The boundary between software project and digital entity starts becoming less obvious.
- The character can evolve
A static avatar isn't very interesting.
A persistent identity is.
Over time a MyZubster character could accumulate verifiable attributes:
MYZUBSTER IDENTITY
GitHub VERIFIED
Contributions ↑
Projects ↑
Reputation ↑
Digital assets ↑
Interactions ↑
The important distinction is between verified data and narrative data.
For example, GitHub activity can be verified against GitHub.
A character's mission or personality can be user-defined.
Those should not be presented as the same kind of information.
That distinction matters if we want digital identities people can actually trust.
- Why call this a metaverse?
Because I think the word became too closely associated with graphics.
A metaverse doesn't necessarily need to start with VR.
It needs persistent entities, identity, interaction, shared rules and a world that can evolve.
Graphics can be one interface to that world.
The underlying system matters more.
Our current experiment can be summarized roughly as:
MYZUBSTER
DIGITAL IDENTITY
│
┌───────┴───────┐
│ │
CHARACTER AI AGENT
│ │
└───────┬───────┘
│
OPEN ECOSYSTEM
│
┌────────┼────────┐
│ │ │
GitHub APIs Protocols
GitHub is especially interesting here because developers already understand its primitives.
Fork.
Commit.
Merge.
Issue.
Release.
History.
Those same concepts can become surprisingly powerful primitives for collaborative world building.
- We just created the first identity visual
As part of this experiment, we created a MyZubster digital identity visual and committed it directly to the project repository.
The asset now lives inside the project itself:
docs/assets/myzubster-digital-identity.png
That sounds like a small detail.
Conceptually, however, it demonstrates something important.
The character isn't only sitting inside a centralized profile database.
It can become an artifact of the open-source ecosystem itself.
And from there we can go much further.
What comes next?
The next challenge is making this model available to everyone.
Imagine visiting MyZubster and doing this:
Connect GitHub
↓
Create Identity
↓
Generate Character
↓
Verify Contributions
↓
Enter Ecosystem
↓
Build / Explore / Collaborate
Your character would not begin from zero.
It could begin with the history you've already created.
And as the ecosystem evolves, the identity evolves with it.
That is the experiment.
Not building another virtual world.
Building an open protocol where humans, characters, software and AI agents can share one evolving digital ecosystem.
And using the tools developers already use to build it.
The metaverse might not need another platform.
Maybe it needs a repository.
Top comments (0)