Add some descriptions to the projects

README.md

@@ -33,16 +33,25 @@ A collection of random ideas
 
 ## Projects
 ### Mathematical model for Factorio
+I would love to have a model for describing the behaviour of a factorio blueprint in an abstract way.
+Ideally this would then also translate into a tool to automatically analyse such blueprints.
+
 ### PID in Rust
 ### Image Processing in Rust
 ### Custom Visualisations for Firefly III
+I am already tracking basically all of my finances in my personal Firefly III instance, but I feel like there could be more interesting insights hidden in the data that is not being shown by default.
+
 ### Sans-IO Rust implementation of minecraft protocol
 ### Custom Minecraft Proxy
+This would require the [protocol implementation](#sans-io-rust-implementation-of-minecraft-protocol) to be done first or at least developed alongside.
+
 ### Signal Processing
 ### (Fast) Fourier Transform
 ### Crystalline memory reclaimation
 ### Wait-Free memory allocator
 ### 2D Fluid Sim
+A simple 2D fluid simulation that would allow me to get a basic analysis of a cross-section of a wing or similar structures.
+
 ### Graph Layout Engine
 ### Calorie Tracker
 ### Visualise minecraft items and their relations
@@ -51,12 +60,26 @@ A collection of random ideas
 ### Postgres protocol implementation
 ### Rust crate to receive stream from OBS
 ### Sensor Fusion
+Things like Kalman-Filters etc.
+
 ### E-Graph implementation
 ### Memory SSA
 ### Vault secret engine for ceph s3
+A custom vault secret engine to dynamically generate and handle s3 credentials for ceph.
+
 ### Vault secret engine for ceph users
 ### Vault secret engine for gitlab tokens
+A custom vault secret engine to dynamically generate and handle gitlab access tokens with different scopes.
+
 ### Wordle Solver
 ### Rust crate for state machines
 ### Implement new werewolf bot
+I would love to have a more flexible werewolf bot implementation.
+The goals would be relatively ambitious:
+- Allow for custom role implementations (likely using custom programming language)
+- All role behaviour should be modeled using state machines and be deterministic for a single playthrough
+- The state of a playthrough should be saved somehow to tolerate failures or restarts of the bot
+
 ### Parse CS Demos
+I already worked a bit on analysing cs demos in the past and would love to have a solid implementation for this in rust.
+It should be flexible enough to allow one to build different tools using it.