{"channel":"atacama","content":"after weeks in the Lithuania mines, we are back to work on Atacama.\r\n\r\nthe first new feature: auto-archiving of URLs. so if we link to a post, there is an archive around the time of submission.\r\n\r\n----\r\n\r\nNext up is a round of *hygiene*. ( one must not rely too much on hygiene being a *generative* process. it is, most commonly, a *publishing* process; rewriting a summary of what is already written.) ( When one looks for benefits here, it is often the case that the only gain is in correcting the mistakes of the past.) ( which would be fine, except the mistakes are the hygiene.)\r\n\r\n* Fix the << __init__.py >> files. ( double-underscore isn't a protected symbol currently. )\r\n* Check the unit tests.\r\n* Feature evaluation. The \"numbered lists\" are so clunky as to be unusable. Perhaps a version with an explicit numbering could work.\r\n\r\n----\r\n\r\nI would like to \"fork\" out the Trakaido code.\r\n\r\nThere are two tasks here. First is to modularize the Trakaido code, so it can be \"mounted\" in a single directory, imported by one \"registry\" file, and everything will just work.\r\n\r\nSecond is to figure out what is left once that and the \"Blog\" code are mounted. ( if only I could make a numbered list!)\r\n\r\n----\r\n\r\nWhat else is there?\r\n# the React Compiler and Widget Directory, which are entangled with the Blog.\r\n# the Spaceship server. ( which, for *arcane* reasons, displays an xPlanet snapshot)\r\n# a clunky Quote Management system, which is entangled with the Blog.\r\n# the AML parser, which is possibly part of the Blog.\r\n# User management.\r\n# the HTML rendering of the Blog. this includes some code for HTML rendering chess boards from a PGN which might be further modularized.","created_at":"2025-07-23T03:03:27.954637","id":633,"llm_annotations":{},"parent_id":null,"processed_content":"

after weeks in the Lithuania mines, we are back to work on Atacama.\r

\n

the first new feature: auto-archiving of URLs. so if we link to a post, there is an archive around the time of submission.\r

\n
\n

Next up is a round of hygiene. \ud83d\udca1 one must not rely too much on hygiene being a generative process. it is, most commonly, a publishing process; rewriting a summary of what is already written. \ud83d\udd25 When one looks for benefits here, it is often the case that the only gain is in correcting the mistakes of the past. \ud83d\udca1 which would be fine, except the mistakes are the hygiene.\r

\n
    \n
  • Fix the __init__.py files. \u2699\ufe0f double-underscore isn't a protected symbol currently. \r
    • \n
  • Check the unit tests.\r
    • \n
  • Feature evaluation. The \"numbered lists\" are so clunky as to be unusable. Perhaps a version with an explicit numbering could work.\r
    • \n
\n
\n

I would like to \"fork\" out the Trakaido code.\r

\n

There are two tasks here. First is to modularize the Trakaido code, so it can be \"mounted\" in a single directory, imported by one \"registry\" file, and everything will just work.\r

\n

Second is to figure out what is left once that and the \"Blog\" code are mounted. \ud83d\udd25 if only I could make a numbered list!\r

\n
\n

What else is there?\r

\n
    \n
  • the React Compiler and Widget Directory, which are entangled with the Blog.\r
    • \n
  • the Spaceship server. \ud83d\udca1 which, for arcane reasons, displays an xPlanet snapshot\r
    • \n
  • a clunky Quote Management system, which is entangled with the Blog.\r
    • \n
  • the AML parser, which is possibly part of the Blog.\r
    • \n
  • User management.\r
    • \n
  • the HTML rendering of the Blog. this includes some code for HTML rendering chess boards from a PGN which might be further modularized.
    • \n
","quotes":[],"subject":"atacama update, July 2025"}