Avatar
notjb55
fd3fdb0d0d8d6f9a7667b53211de8ae3c5246b79bdaf64ebac849d5148b5615f
KEY COMPROMISED, THIS IS NOT MY ACCOUNT

At Starbucks posting from Damus to an uncensorable information relay protocol. No big deal.

shouldn't be too hard to fork branle and add a dark theme... someone should do that

because your browser is trying to force http -> https

what do you mean by repost? like retweet?

yeah there will be a public testflight once I have threads, replies, profiles, following, etc working

Replying to Avatar notjb55

Testing a large post, sorry if this is obnoxious

# protoverse, a metaverse protocol experiment

Ever since I read the book Ready Player One I've been fascinated by the idea of the metaverse. Imagine instead of joining an IRC chatroom, you joined a virtual room with objects: chairs, tables, robots, other people? A virtual shared space where you could meet up with your friends and hang out. This is typically envisioned as some sort of virtual reality where you meet with people face to face, but the metaverse could be much more general than that.

I started thinking about, what could a metaverse protocol look like? Is such an ambitious project even possible? How do we avoid the mess that is the web? Could we keep it simple and extensible? I believe I have a pretty good plan on how to achieve this: I'm calling it the protoverse.

## Goals

Before we start thinking about the ingredients needed to build a metaverse protocol, first let's look at some high level goals:

* Accessible. The metaverse shouldn't exclude those who are blind. This was one of the goals of the original web and we should strive to have an accessibility plan.

* Simple. We should learn from the web and not force client vendors to implement a large number of ad-hoc specifications.

* Flexible. It should support many different use cases and environments. You should be able to connect to a server and be served a multiplayer game, a room, or whatever experience the server operator wishes.

* Interconnected. Like the web with hyperlinks, there should be some way to jump from server to server in a standard way.

apparently you can write blog posts in here

Testing a large post, sorry if this is obnoxious

# protoverse, a metaverse protocol experiment

Ever since I read the book Ready Player One I've been fascinated by the idea of the metaverse. Imagine instead of joining an IRC chatroom, you joined a virtual room with objects: chairs, tables, robots, other people? A virtual shared space where you could meet up with your friends and hang out. This is typically envisioned as some sort of virtual reality where you meet with people face to face, but the metaverse could be much more general than that.

I started thinking about, what could a metaverse protocol look like? Is such an ambitious project even possible? How do we avoid the mess that is the web? Could we keep it simple and extensible? I believe I have a pretty good plan on how to achieve this: I'm calling it the protoverse.

## Goals

Before we start thinking about the ingredients needed to build a metaverse protocol, first let's look at some high level goals:

* Accessible. The metaverse shouldn't exclude those who are blind. This was one of the goals of the original web and we should strive to have an accessibility plan.

* Simple. We should learn from the web and not force client vendors to implement a large number of ad-hoc specifications.

* Flexible. It should support many different use cases and environments. You should be able to connect to a server and be served a multiplayer game, a room, or whatever experience the server operator wishes.

* Interconnected. Like the web with hyperlinks, there should be some way to jump from server to server in a standard way.

nostr doesn't have to be as laggy as branle (no offense to branle devs, but I think the web stack that is being used is inefficient or something). on iOS it's super snappy and I haven't even optimized it yet.

who knows but it's fun regardless!

Test line break

Encoding issue. Should be fixed?

Friends and global timeline working! 😎 all with a single connection per relay! I just filter all events locally for now, but I might need to switch to filtering on contact list ids to go further back for friends. Posted this from iOS of course! There is no content length limit yet, should there be?

Weird, got a signature verification error ... testing 🧐