I'm using that to communicate with my AI. Perhaps one day we'll speak a New Ithkuil variant with AI.
1,705 karma · joined June 10, 2010
plays board games offline and online (BGA, TTS, Board Games VR, Tabletop Playground, AllOnBoard or Vassal)
groks books and dance
interact - bsky.app/profile/monsuta - fsiefken at gmail - meet.hn/city/52.0907006,5.1215634/Utrecht
I'm using that to communicate with my AI. Perhaps one day we'll speak a New Ithkuil variant with AI.
* using short boardgames to measure cognitive performance on various metrics
* creating simple 3d boardgames with raylib kolibri_engine
* dancing and studying vajra dance and the vajra song from namkai norbu
* reading and studying about: mahamudra and dzogchen vs christian contemplative traditions and mystics, and transpersonal psychology
In this video Fischer briefly and enthusiastically talks about this topic. He talks about Fischer Random and he suggests the Capablanca proposal might be even better, and there can be even more creative variants. https://www.youtube.com/watch?v=vb7-0R2qg98
I like Seirawan Chess and Euroshogi a lot, next to King of the Hill and other games like Minishogi, Tak, Tzaar and RftG.
On the Amiga4000 and Apple you could run their 'native' OS, or you could run a modern day NetBSD or a BeOS version (HaikuOS wouldn't run).
On the Pentium-66, modern Freedos would run, Windows 3.11+win32s+calmira, Windows98SE, Windows2000sp5, XPlite, NetBSD and perhaps even an absolutely stripped down Linux 6 kernel with all the features that would be handy.
You could program in a modern i586 build FreePascal, Zig, Lua, juniper, micropython/shedskin, mruby/natalie, picoruby, juniper - perhaps a low memory JVM could run (OpenJDK 8 or JamVM).
It'd be possible to use sqlite, raylib and r3d-freepascal for efficient 3D games/apps next to Quake/Darkplaces, Doom2/GZDoom, Duke3D, Counterstrike 1.5, Halflife, perhaps Unreal1, Irrlicht and FTEQW.
Modern LambdaMOO's Toastunt/Moor could be made to run and inform6 and tads3 interactive fiction compilers. Fairy-Stockfish could be compiled - so enough creativity for gaming. I am just worried about getting Vassal, the java boardgame game engine to run comfortably... but the resolution would be pretty low to play many boardgames comfortably: the highest ATI card could drive 1280x1024. I would really like to use it so I don't have the real world board game setup time. Keldons Race for the Galaxy would compile and run though.
For internet, Dillo+ supports https, gemini and gopher. https://github.com/crossbowerbt/dillo-plus This can also be used to browse zim offline wikipedia files with kiwix-serve.
Now my only real problem is that we wouldn't have GenAI - probably EVER - would that be a blessing or a curse?
--- Handy Linux kernel 6 tweaks for low memory situations if you don't want to run NetBSD (which perhaps would be the best choice):
* zram + zstd zram creates a compressed block device in your RAM. To the OS, it looks like a regular swap partition, but it lives entirely in memory. When your 64MB fills up, the kernel sends data to /dev/zram0. The data is compressed (usually 3:1 ratio) and stored back in a small slice of your RAM. Version 6.19 includes better compression ratios and rebalancing. It prevents the CPU from over-working itself on decompression.
* zswap + zstd zswap is a front-end for a physical swap file on your hard drive. It intercepts pages headed for the hard drive, compresses them, and keeps them in a RAM pool. If that pool gets too full, it evicts the oldest compressed data to the actual disk. Starting in 6.18, zswap transitioned to using the zsmalloc allocator by default. This reduces "internal fragmentation," meaning it packs those compressed bytes tighter.
* frontswap API that allows the kernel to intercept swap-outs and store them in a transient memory pool; it works with Zswap to keep the system responsive during high load.
* Maple tree Replaces old "Red-Black trees" for memory management; it reduces the CPU cycles needed to find data in RAM.
* SLUB sheaves A modern memory allocator optimization that packs small objects into "sheaves" to reduce fragmentation.
* CONFIG_SLOB_BERBER A specialized 2025 backport of the old "SLOB" allocator; a memory-efficient way to handle kernel objects, saving roughly 1-2MB of overhead compared to the standard SLUB used in modern PCs.
* Ext4 without journaling Disable the "Journal" to save RAM and disk writes; it provides the best file-allocation speed without the memory overhead of Btrfs.
* Reiser4 patch An efficient file system for small files; it packs them directly into the tree nodes, which saves disk space and reduces I/O.
* KSM (Kernel Shared Memory) Scans RAM for identical pages (like duplicate library code) and merges them into one; it’s a "free" RAM upgrade if you run multiple instances of the same program.
* Very High Frequency (VHF) HZ Tuning Manually setting CONFIG_HZ to 100 (instead of the modern 1000); this reduces the number of times the CPU "wakes up" per second, saving precious cycles for actual work.
* DevTmpfs Automates device node creation entirely within the kernel; it saves you from running a heavy udev or mdev daemon in userland, freeing up roughly 2–5MB of RAM.
* LZ4 Compression for Kernel/Initramfs Using LZ4 instead of xz, gzip or zstd for the kernel image.
It records the death of the last Sasanian king, Yazdegerd, in 651 AD and notes that the "Persian kingdom was completely destroyed" and its people became "slaves paying tribute to the Arabs." It describes the Romans being driven out of Syria and Egypt, noting that "no foreign people had inhabited it" since the time of Christ until now.
At the same time, there were fierce theological debates about the nature of Jesus Christ. He was seen as a human, a rabbi, a prophet, and God incarnate—but how could one reconcile these different views into a consistent christology? The document lists a few positions:
Chalcedonian: 2 natures, 2 wills (Marcian, Pulcheria). Deemed positive.
Miaphysite: 1 united nature (Dioscorus, Severus). Deemed tyranny.
Monothelite: 2 natures, 1 will (Macarius, Theodore of Pharan). Deemed sympathetic.
Eutychian: 1 divine nature (Eutyches). Deemed misguided.
Severus of Antioch, the preeminent Miaphysite theologian, was called a "leader of sectarianism". Theodoret of Cyrus was mentioned as a Greek teacher and a defender of the 2-nature Christology, but was often accused of Nestorianism by his enemies.
The Romans (and by that century fellow Christians) condemned the Maronite-specific theology of Monothelitism. The Chalcedonians (Rome/Byzantium) said Christ had 2 natures (Divine and human), while the Miaphysites (Egypt/Syria) said he had one united nature. In the 630s Emperor Heraclius and Patriarch Sergius proposed a middle ground: "Christ has 2 natures, but he only has one single divine Will.
The Western Church (Rome) and later Byzantine emperors eventually decided this view was a heresy, arguing:
If Christ doesn't have a human will, he isn't fully human. If he isn't fully human, he couldn't have truly suffered or saved humanity. Therefore, Christ must have two wills (Divine and Human) perfectly in sync.
At the 3rd Council of Constantinople (680-681 AD), the 2 wills (dyothelitism) view was made official. Monothelitism was banned and its leaders were "excommunicated, deposed, and banished," including Pope Honorius of Rome, Sergius of Constantinople, and Macarius of Antioch. Sympathy for these people and Theodore of Pharan highlights the Maronite origins of the chronicle, as the Maronites originally held to the Monothelite view and resisted the 681 AD council.
The Arabs, the new rulers, offered a form of stability but demanded tribute. In section [148b], the author describes the Roman defeat at the Battle of Jabiya as a "wondrous sign... revealing the wrath that would befall the land."
In section [154a], after describing the Council of 681, the author notes a great military defeat and says: "This great calamity befell them because they had corrupted and defiled the sacred trust they were supposed to uphold." Furthermore, in section [149a], the text claims that King Heraclius sought peace with the Arabs to stop the bloodshed, but they did not respond because they were "the very embodiment of justice" (if this is the correct translation).
In his work, Gabriel Reynolds discusses the influence of the Church of the East (the Nestorian Church) as a major presence in the 7th-century Near East and a key part of the Quran's original audience.
Reynolds notes that some critical scholars find the East Syrian (Nestorian) Christology congenial to a docetic view of the crucifixion - the idea that Christ only appeared to suffer. See "The Muslim Jesus, Dead or Alive" (2009): https://web.archive.org/web/20220925142210/https://www3.nd.e...)
Classical Muslim commentators sometimes used Nestorianism as a heresiographical foil, anachronistically attributing certain beliefs - like Jesus being the "Son of God" - to this specific sect to contrast them with the original 'Muslim' followers of Jesus.
Reynolds critiques the common scholarly practice of searching for obscure Christian heresies to explain the Quran's views on Jesus. Instead, he highlights the presence of mainline late-antique Churches: the Melkite Church (imperial Roman), the Syrian Orthodox Church (Jacobite/Monophysite), and the Church of the East (Nestorian) as the predominant influences. He notes how the Quran reshapes these Christian narratives to serve it's own theology:
The Quran's charge of shirk (associating partners with one God) mirrors late antique Christian disputes where different sects accused one another of tritheism (three Gods: The Father, The Son, The Spirit - as a millenium later is exemplified by Joseph Smith Mormon visions).
He argues the Quran's crucifixion pericope is in "close conversation" with the New Testament and the Syriac topos of the risen Christ acting as an apocalyptic witness against his murderers, not in opposition.
Reynolds also argues that the Quran does not deny Jesus' mortality but rather alludes to it in passages like 19:33 where Jesus speaks of the "day I die". He highlights the verb tawaffa (often translated as "to take"), arguing its standard Quranic meaning is "to make die" or "separating the soul from the body".
Reynolds interprets "they did not kill him" (4:157) not as a denial of the crucifixion and death itself, but as a denial of Jewish power over death. The Jews arrogated to themselves God's power over life and death, but in reality, God was in control the Quran says. The prophets are under God's rule. The popular "substitution theory" is a product of later Islamic tafsir and is not explicitly stated in the Quran itself.
Another noteworthy article on the christological and theological debate between christianity and islam: https://churchlifejournal.nd.edu/articles/is-the-quranic-god...)
As for my own answer as someone who has been raised Catholic (and still is in a way), having made a tour through Eastern Orthodoxy, humanism, Sufism, shamanism, and buddhism: I noticed that Gene Wolfe, a Catholic SF writer well-versed in church history, has a main character in his Solar Cycle series called Severian.
Severian's name could be an allusion to these one-nature theology debates (. He absorbs the memories and consciousness of countless people, most notably the previous Autarchs, becoming a singular being with a unified nature composed of many. Like the 7th-century church debates, Wolfe describes Severian as a figure of turmoil and schism (severing) - a Christ figure who divides the world, acting as both a bringer of death (a torturer) and life (the New Sun).
As both a Christian and Vajrayana practitioner, I relate to the nature of Christ as a form of Tibetan guru yoga (Bon or Buddhist) and Eucharistic adoration. Guru Yoga is a process of identifying with the lineage and universal wisdom, the teacher, God or Sunyata. Severian’s fate is to become the Autarch, a role that is not an individual office but a literal lineage lived out in one body.
At the heart of Guru Yoga is the "transmission that occurs through the meeting of two minds," making them inseparable. Severian undergoes this literally when he, like the Eucharist, consumes the remains of the previous Autarch and Thecla. In this state Severian, perhaps like Jesus, is no longer a separate ego; he is a manifestation of a 'unified nature' where human and divine (or cosmic) minds are inseparable. Theosis.
In his book Rainbow Body and Resurrection, Francis Tiso follows the Christological splits of the 5th century and the Syro-Oriental (Nestorian) Church. Tiso writes that during the early 7th century, the Persian Sassanid dynasty began persecuting these Christians. Babai the Great managed to guide the church through this, allowing for theological studies independent of the Byzantine empire.
Because these ongoing Christological divides (and the subsequent Arab/Muslim conquests) isolated the Syro-Oriental Church from Europe and Asia Minor, the church there was forced into a life of its own. This theological and political isolation is what pushed their missionary expansion eastward along the Silk Road - eventually reaching China and Tibet, where they engaged in the cross-cultural dialogues that Tiso suggests influenced the development of the Dzogchen "rainbow body" phenomenon through the mystical practices of the desert fathers.
I am sure this is already worked on in Russia, Ukraine and The Netherlands. A lot can go wrong with autonomous flying. One could load the VLM on a high end android phone on the drone and have dual control.
The 'Intertwinkled' project ceased following Joe Armstrong's passing in 2019. From the video I gather Joe and Jeremy worked on 3 specific technical implementations together:
# 'Mailboxes' for Tiddlers To give Tiddlers and Wikis specific "addresses" so they could send messages to one another (e.g., a "Request for Information"). This was implemented as a prototype where a TiddlyWiki could act as a front-end "office" and forward queries to an Erlang backend process.
# Bayesian & TF-IDF auto-tagging
If Wikis are going to talk to each other, they need a shared ontology (understanding of words). Joe wrote code to analyze Tiddlers and predict tags based on content. The presentation showed that Bayesian inference worked well for predicting existing tags (85% accuracy) but TF-IDF provided tags that felt more "human." Similar functionality exists via modern plugins (like the TiddlyWiki Natural Language Processing plugins), though not the specific Erlang implementation Joe built.
# Provenance tracking
To track exactly where a Tiddler they borrowed the idea from Ted Nelson’s Project Xanadu). TiddlyWiki today has fields for source and creator, but the deep, automated chain-of-custody tracking across the web (Xanadu style) was a theoretical goal rather than a concrete feature.
-- In time TiddlyWiki has developed other methods to achieve similar goals of "Inter-tiddler" communication.
TiddlyWiki 5 uses an internal messaging system that mirrors the Actor model slightly. Widgets (UI elements) send messages up the DOM tree (eg. tm-navigate, tm-save-tiddler). It is event-based, but it is strictly local to the browser session and hierarchical, whereas the Erlang prototype was distributed and peer-to-peer.
TiddlyWiki standardized on Node.js for its server-side implementation. This allows TiddlyWiki to run as a server, load tiddlers from the file system, and serve them to multiple clients. As it was simpler I preferred using the 1 TiddlyWiki html file solution. https://talk.tiddlywiki.org/t/how-to-tiddlywiki-on-nodejs-ng...
You can HTTP fetch tiddlers from other TiddlyWikis, but it is a pull model (importing), not the asynchronous push/mailbox model Joe Armstrong envisioned. If you wanted to build a "Federation" of wikis today without using complex custom backends, you would indeed use tm-http-request to poll other wikis for updates. https://tiddlywiki.com/#WidgetMessage%3A%20tm-http-request
A community version of TiddlyWiki called Bob (by OokTech) implements real-time, two-way communication between the server and the browser, and between different wikis managed by the same server. This is the closest functional equivalent to what Joe and Jeremy discussed, but it's built on WebSockets and Node.js. https://github.com/OokTech/TW5-Bob
recent talk by bunnie, sean "xobs" cross
https://events.ccc.de/congress/2025/hub/en/event/detail/xous...
https://app.media.ccc.de/v/39c3-xous-a-pure-rust-rethink-of-...
One could convert the Markdown/PDF to a very long image first with pandoc+wkhtml, then use ffmpeg to crop and move the viewport slowly over the image, this scrolls at 20 pixels per second for 30s - with the mpv player one could change speed dynamically through keys.
ffmpeg -loop 1 -i long_image.png -vf "crop=iw:ih/10:0:t*20" -t 30 -pix_fmt yuv420p output.mp4
Alternatively one could use a Rapid Serial Visual Presentation / Speedreading / Spritz technique to output to mp4 or use dedicated rsvp program where one can change speed.
One could also output to a braille 'screen'.
Scrolling mp4 text on the the TV or Laptop to read is a good idea for my mother and her macula degeneration, or perhaps I should make use of an easier to see/read magnification browser plugin tool.
It has transparent compression built-in and has support for natural language queries. https://buckenhofer.com/2025/11/agentic-ai-with-duckdb-and-s...
"DICT FSST (Dictionary FSST) represents a hybrid compression technique that combines the benefits of Dictionary Encoding with the string-level compression capabilities of FSST. This approach was implemented and integrated into DuckDB as part of ongoing efforts to optimize string storage and processing performance." https://homepages.cwi.nl/~boncz/msc/2025-YanLannaAlexandre.p...
Rust port feature: The implementation "passes 93.8% of Mozilla's test suite (122/130 tests)" with full document preprocessing support.
Test interpretation/sensibility: The 8 failing tests "represent editorial judgment differences rather than implementation errors." It notes four cases involving "more sensible choices in our implementation such as avoiding bylines extracted from related article sidebars and preferring author names over timestamps."
This means that the results are 93.8% identical, and the remaining differences are arguably an improvement. Further improvement, extraction accuracy: Document preprocessing "improves extraction accuracy by 2.3 percentage points compared to parsing raw HTML."
Performance:
* Built in Rust for performance and memory safety
* The port uses "Zero-cost abstractions enable optimizations without runtime overhead."
* It uses "Minimal allocations during parsing through efficient string handling and DOM traversal."
* The library "processes typical news articles in milliseconds on modern hardware."
It's not explicitly written but I think it's a reasonable assumption that its "millisecond" processing time is significantly faster than the original JavaScript implementation based on these 4 points. Perhaps it's also better memory wise.I would add a comparison benchmark (memory and processing time), perhaps with barcharts to make it more clear with the 8 examples of the differing editorial judgement for people who scan read.