Coaliting Dev Log

Entry 4 (Mid May 2021)

Hello there, here’s the junior dev writing. We’ve made a plan for the next coapp instalment - a coahive, which will be a graph of coahive cells, each hosting a private hell for a coalite. There might be connections across coahives as well. The coahive is responsible for fetching coalites and traping them in hive cells for direct user control. Coalites can meet while being controlled by different users. This is challenging and will take a while. I’m thinking the rendering will be all server-side and served as a pixel stream to the frontend (low res, such as 32x32 pixel art image). Logic handling such as movement and collisions and etc will all be mapped to pixel-matrix math I think. I must consult with the senior dev and the senior client as well.

Entry 3 (Somewhere in May 2021)

Hello this is the developer writing. Tomorning I finished fixing the crypto key format fiasco. We’re now expecting PKCS#1 encoded keys from the client and nothing else (we might add a key format specifier later but for now it’s hardcoded). Two nuget tools can be used to fetch coalites code-free: coaget and coakeygen. An example follows after this line:

coakeygen # Generate a public/private key pair (default 4096 len. Run coakeygen help for usage.)

coaget https://lore.071224.xyz CLAIM .\key.pkcs1.prv .\key.pkcs1.pub > coalite.json # Claim the current coalite for your user id, save it in a json file.

coaget https://lore.071224.xyz hoarder MINT .\key.pkcs1.prv .\key.pkcs1.pub coalite.json .\payload.b64 > coalited.minted.json # Mint the claimed coalite with a base64 payload (e.g., a payload.b64 file)

# OR for example, BURN the coalite. coaget https://lore.071224.xyz hoarder BURN .\key.pkcs1.prv .\key.pkcs1.pub coalite.json

Entry 2 (Somewhere in May 2021)

Development went well after the coabroker (blazor) was put to sleep. This entry relates to events which took place since the last event. I recently merged dev to master which means a deploy is coming soon and a new coaget dotnet tool was also developed to test the thing.

A friend of mine

A friend of mine gave me the ideia to include a console/terminal below the 32x32 planned view port for the coalite hell world. Good ideia.

Entry 1 (Somewhere in May 2021)

This is the coaliting dev log page. This is raw input material. Development of the new signing scheme is going well, although tooling problems have already been encountered. The junior developer insisted on using Blazor Webassembly for its first coaliting use-case, the coabroker project. The lead developer then realised that dotnet webassembly does not support the cryptography library yet, and so, he now must interop with javascript for the cryptography functions. This will have some kind of impact on the roadmap of the project (which is undefined, but still).