Thank you! We're reworking the map and UI right now but we're keeping the same beautiful look!

Great work! Especially the piano.

This reminds me of Counter Strike's bhopping and surfing. I love it!

Looks good to me.

It looks great. Do you have an idea how you're going to go about updating the edge foam?

The website was actually fully redesigned a few days ago. I'm currently adding more content there. But you can check out the GitHub at github.com/Quaint-Studios/Reia/blob/master/docs/ROADMAP.md. There should be some updates this weekend!

You have always been a huge help. I joined immediately after I had a call with you a while back. I'm `makosai` on Discord. I'll definitely share my story on how I use Turso when the time comes. ❤️

Lastly, a master server is like a "hub" for servers and clients. Cluster Servers connect to it with their keys. Clients are assigned a cluster or can manually pick one. The Cluster Server will handle movement, message, auth, and any other action. There's also "fragments" but it's just an "instance."

Your third question: Authentication is still a tossup. We're guaranteed to use @tur.so to store user data and scale with that. Especially since we want to support offline & local access as well. When it comes to authentication, the tossup is Supabase & Appwrite atm. But it will be a separate server.

For your second question, it's completely server-authoritative for most things. But in the future I plan to offload tiny things to the client. Things that can be checked for manipulations like movement. I'll also make it to where clients can opt-out of all peer-to-peer activity.

Thanks! To answer your first question: Sustenet used to be written in C# and I got it to be very performant. But I wanted more out of it. So I moved to Zig. It was fun but Zig didn't have much for concurrency and managing threads is a bit too much of a trade-off. So I went with Rust. A nice balance.