1
Fork 0
Personal tinkering space
  • Jupyter Notebook 58%
  • PureScript 7.8%
  • TypeScript 7.7%
  • Rust 6.7%
  • Haskell 5.8%
  • Other 13.8%
Find a file
2026-03-29 01:38:36 +01:00
bash bash(mottainai-p2p-generator): Add mottainai files documenting all effects 2025-08-14 20:30:24 +03:00
dart Add dart/freeform-gradient to readme. 2024-05-28 03:46:10 +02:00
elm/todolist elm(todolist): chore: added an elmapp.config file 2019-11-28 17:32:24 +02:00
fsharp Add fsharp/ygosim to readme 2024-05-12 03:45:27 +02:00
haskell haskell(nihil): Reorganise a ton of stuff 2025-08-14 20:23:34 +03:00
idris/learning Make file-structures more readable 2023-10-29 01:15:32 +02:00
javascript javascript(banconomania): back up the files from itch 2025-11-11 21:12:51 +01:00
lean/learning Make file-structures more readable 2023-10-29 01:15:32 +02:00
lua Document addition of prescient-trains 2024-03-04 13:56:37 +01:00
odin odin(tunnels): init 2026-03-29 01:38:36 +01:00
purescript Add doffy to readme 2025-11-11 21:55:23 +01:00
python python(hypergeometric): init 2025-11-11 21:28:13 +01:00
rust/shaderfurl rust(shaderfurl): commit the shader ideas 2026-01-19 12:59:38 +01:00
typescript Add visual-studio-paint to readme 2025-11-11 22:05:26 +01:00
typst/learning Add typst 2023-10-29 02:32:41 +02:00
import.sh Stop import script on failures 2025-11-11 21:32:52 +01:00
README.md Add a note on the philosophy of the project to the README 2026-01-19 12:58:25 +01:00

The solar conflux

This repository contains numerous experiments of mine which do not deserve their own repositories. It exists for archival purposes.

The repositories are properly imported using ./import.sh — a dangerous script that shouldn't be run unless everything in the local repo has been backed up.

Navigation

The experiments are currently organized based on the language they use:

Philosophy

I plan to expand this repository to include all my projects, and flatten its file structure (the per-language categorization is a bit odd).

Here's the basic laws:

History is not sacred

  • I might rewrite history at any point
  • do not reference stuff in this repo by commit hash!
  • referencing things by date is the best idea (or tags perhaps, although I'm yet to figure that part out)

Discovery is not a goal of the file structure

  • trying to create deep hierarchies for the files in such a repo is a recipe for failure
  • when trying to learn about the projects, one should instead check the page I'll create on my website (or the linked markup in case the website is down)

The past is murky, but we can enforce conventions on the future

  • For example, I'm not going to worry too much about the commit messages of the past (nor the formatting of the code), but I might enforce such conventions for the future