Daegalus

https://magic.wizards.com/en/news/mtg-arena/on-whiteboards-n...

But other than that, everything is just humming along.

We had reached out to him when we discovered his work back then. But he refused to join our effort unless we 100% open source everything then and there. Due to legal reasons at the time (related to the T4C owners and T4C using similar code to BMC), we had to stay closed source. He still refused to work with us even with a promise that we plan to open source eventually.

We shared with him all the packet data models and such but he was kind of unresponsive after our initial conversations.

He is also working 100% blackbox while we have sources for the client and assets/server data.

Hopefully all that makes sense. I haven't really paid attention to his project since then and it seems he stopped all work efforts on it 2 years ago.

But to answer your question, it's quite a bit far behind what we have. But there is so much work that goes into an MMO. We have solved the network stuff, we are just working now on world state as we have the ability for multiple people to log in and do stuff with dummy data. I have been writing tools and importers for the server data. Like zone files, creature, NPC, item, etc data. All the monster spawners are in the zone files for example and then needs to be cross-referenced with other data, and then assets to actually draw spawn mobs.

I have client sources as I am working with the person that owns the rights.

Protocol is not documented, so reverse engineering, but having the clientside helps.

The server software was lost to time and accidents. But we have dumps of quest data, times, mobs, etc and all assets in original form. So as soon as I get the server in a working state. We have the full game.

We plan to open source/creative commons everything when we get something playable.

I've done 4 massive redactors as the code grows, to accommodate changes in understanding and design flaws.

I'm building the server in Go. I use goroutines a lot. I use a shrinking/growing ring buffer for requests and responses. Uses UDP and I just receive a request and pop it onto the queue. I keep the address of the client along with the packet request. The queue is read by another goroutine and gets processed and sent to a packet handler. Which does game state work, and queues a response, or passes it off to another handler. Then the go routine for the responses picks it up, reads the address and port of the client and sends it the packet.

All I have maybe 5-6 threads running in parallel and I already can log into the game and walk around with others. There's tons of work still needed. But it's nice to know my underlying design is sufficient to maybe handle the dozens of people playing for nostalgia.

It is possible but I don't know. Just was trying to point out that it's more than just some demo that it was used for.

The film was shot almost entirely in Unity, then the final render used some extra stuff and other tools. But the scenes, shots, etc were done in Unity. A quick google shows you this.

https://www.youtube.com/watch?v=WupuXjvO9uA Making of videos on Youtube, you see the Unity editor in many places while they film in VR

Either way, I don't think either is ready for prime time as its still early development.

Consul is just a nice distributed KV store and Consul Templates integrate well with vault secrets.

It can also be used as a storage engine for Vault of needed.

Maybe call it OpenVLT and OpenCNSL. Then we can wrap it in a larger OpenHC or OpenMoto umbrella of projects.

Especially with the integration points between Terraform, Vault, and Consul, those can be maintained better.

Hell, I would do it myself, it I had the connections and time to do it. I might still try if no one else does. I would model it after OpenTF

The backend development capabilities have been left to rot. It's all flutter.

When it came out it had so much potential to displace NodeJS. But they threw that away when they couldn't get into the browser and pivoted to flutter.

I still maintain some of my packages like uuid, otp, etc. But my API handlers and other backend stuff is kinda dead as there is 0 interest in it nowadays.

I would use Deno before Dart for backend nowadays, even though I would prefer Dart.

But it would be also nice to have a standard mutable variant too.

If you want a little more stability but still rolling release, do Debian Testing. Packages are only really delayed by 2-10 days (except during release windows where they do branching). The only criteria for something getting into Testing is that it passes all tests while in Sid for multiple or all supported platforms.

But overall, Sid is fairly rock solid. If anything I think Rhino Linux should have taken Debian Sid or Testing as a source, adding all the niceties/desktop/sane defaults of Ubuntu that they like. and released that.

I think the ideal middle is using a stripped down HTTP subset, with HTML5 (maybe with some things removed, like script tags), and the latest CSS.

No JS. Focus on the document. Make any changes needed to improve things. No crossdomain cookies. Maybe no cookies at all. Only GET and POST maybe. Only allow some very specific headers maybe and strip anything else. Figure out a more novel system for secure transmission, maybe by default.

I'm thinking of starting something with Servo, I know it's not HTML5 yes but it could be a good way to limit things. Or maybe Libweb from the Ladybird project.

According to this it's in Rawhide, there are probably some slowdown with the imminent branching of F39 from Rawhide.

Or there might be build or compatibility issues somewhere and they have to hold it back.

I regularly cancel and restart subscriptions depending on usage, to keep things balanced and not waste money.

If I pay for a year, even if I stop using it say 6 months in, I've already paid for another 6months, losing that money.

I refuse to pay yearly subscriptions for most things. Amazon Prime is the only one because I use them year-round.

Though Sourcehut would be one I pay yearly for if I did a full move there, but I would start with monthly at first.

I figured extracting them as much as possible and just making it like a museum to my past self. Images are all gone but layout and text is there.

I was even considering making a historical section where I unearth old projects and sites I built. I recently found the wayback machine had saved some of my old blogs and sites that I have lost, so I plan to back them up and put them up as a historical type thing on my site and your layout gives me ideas on how to do it best.

I think this is a great end result for the NUC. Asus makes some good stuff and they can probably push the NUC some more for reasonable prices.

Other than that Crystal is fantastic and I hope to use it more in the future

I have settled in Hugo + Cloudflare Pages. I just write markdown, and commit it. Cloudflare does the rest.

Though I am building my own static site generator / server for my blog just for fun that I might switch to. Simple, tailored. And it's written in a way that instead of static files, it's a go app, with all my of my blog posts are embedded and the site lives in an in-memory filesystem.

Most of this was because I wanted to add webmentions.

I don't write often (mostly lack of time), but I try to write technical articles on how to set things up, or if I want to share an opinion on the state of some things (most of them are older ramblings from when I was younger)