diet256 VS space-craft-22

I'm working on INET256, an API for secure identity based networking. The reference implementation, mesh256 is a mesh network using a distributed routing algorithm. There is also diet256, which is a centrally coordinated network with direct connections using QUIC over The Internet.

https://github.com/inet256/inet256

https://github.com/inet256/diet256

I have a fairly simple save system in [this repo](https://github.com/eamonnmr/surviveSpace) that I'm probably going to port to a [similar game](https://github.com/EamonnMR/space-craft-22/) soon. I can answer questions about how I did it right here if you'd like. The gist of it is serialization and de-serialization-you need to decide what data is needed to reconstruct a scene and write code that marshals that into and out of a save file. I tend to like adding `serialize` and `deserialize` methods to my classes and leaving the details of how those work inside the class, then let scenes that represent levels enumerate the things that expose those methods, call the methods, and wrap up a big file with the contents. I use Json here for simplicity, but any format will do (and you might not want something as easy for a user to read/modify as json!!

Gooher server that connects to your WordPress site and exposes it to the phlogosphere

https://github.com/EamonnMR/gopher-wp-bridge

And my life wouldn't be complete without working on another space game

https://github.com/eamonnmr/space-craft-22