all repos — eyes-like-fire @ ed5d32be66b0fefb153de3d6311b82b8f30c7675

Source code for the main eyes-like-fire website 

Blog
Juniper Beatitudes [email protected]
Sun, 25 Jan 2026 09:33:27 -0600
commit

ed5d32be66b0fefb153de3d6311b82b8f30c7675

parent

7b0511440b59ae6f7e86f05da54ef6c6ed90345f

9 files changed, 63 insertions(+), 15 deletions(-)

jump to
M Makefile → Makefile 
@@ -1,5 +1,5 @@
 PANDOC := pandoc
-PANDOC_OPTS := -N -s -fmarkdown -tchunkedhtml --shift-heading-level-by=-1 --toc=true --template=src/template.html --lua-filter=extern/include-files/include-files.lua
+PANDOC_OPTS := -N -s -fmarkdown -tchunkedhtml --shift-heading-level-by=-1 --toc=true --template=src/template.html -Fmermaid-filter --lua-filter=extern/include-files/include-files.lua
 
 build: src/*.md src/*.tex src/template.html 
 	rm -rf build/*

@@ -7,15 +7,15 @@ latex -output-directory=build -output-format=dvi src/projects-chart.tex
 	dvisvgm build/projects-chart.dvi -o src/projects-chart.svg -n
 	pandoc -o build/english.zip src/english.md $(PANDOC_OPTS)
 	pandoc -o build/francais.zip src/francais.md $(PANDOC_OPTS)
-	pandoc -o build/russkij.zip src/russkij.md $(PANDOC_OPTS)
+	pandoc -o build/blog.zip src/blog.md $(PANDOC_OPTS) --toc-depth=1
 	unzip build/english.zip -d build
 	unzip build/francais.zip -d build/francais
-	unzip build/russkij.zip -d build/russkij
-	rm build/english.zip build/russkij.zip build/francais.zip
+	unzip build/blog.zip -d build/blog
+	rm build/english.zip build/blog.zip build/francais.zip
 	rm build/projects-chart.dvi build/projects-chart.aux build/projects-chart.log
 
 deploy: build src/lighttpd.conf
 	rsync -r build juniper@hestia:/home/juniper/website
 	rsync src/lighttpd.conf juniper@hestia:/home/juniper/website
 	rsync src/Dockerfile juniper@hestia:/home/juniper/website
-	ssh juniper@hestia "cd website; podman build -t eyes-like-fire:latest .; podman run --network=host -d -v.:/var/www:Z eyes-like-fire:latest"
+	ssh juniper@hestia "cd website; podman build -t eyes-like-fire:latest .; podman run --network=host -d -v.:/var/www:Z --replace --name website eyes-like-fire:latest"
M flake.nix → flake.nix 
@@ -18,6 +18,7 @@ (with pkgs; [
             gnumake
             pandoc
             unzip
+            mermaid-filter
             (texlive.combine {
               inherit (texlive)
                 scheme-basic
A src/blog.md 
@@ -0,0 +1,54 @@
+---
+title: On Micro-Blogging
+author: Juniper Emily Rose Beatitudes
+---
+
+# On Micro-Blogging {#on-blogging}
+
+## On Implants and Wearables (2026-01-25) {#on-implants-and-wearables}
+
+I have multiple implants (`adora`, a [NEXTv2](https://dangerousthings.com/product/next-v2/), and `entrapta`, an [xG3](https://dangerousthings.com/product/xg3/)) and one wearable (`pythia`, a Fitbit Inspire 3). Of course, I'm planning on getting more---short term plans include a [CoM conversion](https://dangerousthings.com/product/conversion/) for tap-to-pay and a [FlexNT](https://dangerousthings.com/product/flexnt/) for reasons I will discuss below, and in the longer term I plan on getting a [BodyBytes implant](https://forum.dangerousthings.com/t/bodybytes-implant/12270/126) in my leg (also to be discussed below). However, from an engineering design perspective, I think having implants and wearables work together is an interesting concept I'd like to explore.
+
+### Implants Alone
+
+An implant alone, with the current state of the art, is not a super useful thing. Sure, being able to present an NFC chip or payment module in my hand is a neat party trick, and magnets help me carry screws and small ferromagnetic parts, but on the whole, the problem of *powering it* means that without an external device to accompany, most implants cannot do anything on their own.
+
+![`adora`, just kind of being there](src/adora-alone.jpg)
+
+### Smart Implant, Dumb Wearable
+
+What about pairing a "smart" implant with a "dumb" wearable, which would provide only power? An example of this is found in the *BodyBytes* implant mentioned earlier, which is an OpenWrt wireless access point that can be implanted in the leg and used as a file server. It has no power source of its own, and requires an external Qi battery mounted near it (for example, attached to a garter or holster) to function. This allows it to work continuously, but the implant itself is large, expensive, and requires a high level of skill to implant (though, knowing its creators, such skill is definitely available).
+
+![The BodyBytes PCB design, as of 2026-01-25](src/Bodybytes[3DTOP].PNG)
+
+### Dumb Implant, Smart Wearable
+
+Another compromise can be found by pairing a relatively "dumb" implant with a "smart" wearable; that is, the implant only stores data, with power *and* computation occurring on the wearable. For example, a current (extremely early stage, possibly infeasible) project I'm workshopping involves pairing a flexible NFC implant placed under my neck tattoo with a choker that can act as a FIDO2 device, allowing me to split credentials between the implant and the choker and use them for authentication (such as for SSH or OpenID Connect). This would result in a cheap implant and a simple wearable that can together perform a complex function. However, without the wearable, the implant itself is useless (possibly a brick, if credentials are split using XOR, encryption, or Shamir secret sharing).
+
+```mermaid
+---
+title: NFC OVERKILL Choker Design
+caption: NFC OVERKILL Choker Design Block Diagram
+---
+flowchart
+    usbc[USB-C 2.0 Jack]
+    mcu[RP2040]
+    buzzer[Piezo Buzzer]
+    fsense[Fingerprint Sensor]
+    jtag[JTAG Debug Port]
+    flash[QSPI Flash]
+    nfc[CR95HF NFC Reader]
+    implant[FlexNT Implant]
+    usbc <-- FIDO2 ---> mcu
+    usbc -- Power/GND ---> mcu
+    jtag <-- SWD ---> mcu
+    mcu <-- I2C ---> fsense
+    mcu <-- Quad SPI ---> flash
+    mcu -- PWM ---> buzzer
+    mcu <-- SPI ---> nfc
+    nfc <-- 13.56MHz ---> implant
+```
+
+### Engineering Design
+
+It all comes down to engineering design: it makes sense in many cases to have the implant itself be smart with the wearable being "dumb"; the reverse can be just as true. The engineering requirements should always drive the design decisions, not the other way around.
M src/english.md → src/english.md 
@@ -30,6 +30,8 @@ - `artemis`: Dell Precision 5570 running Debian 13
 - `athena`: Macbook Pro 2019 running Debian 13, hosting a workhorse server and a media server
 - `hestia`: Lenovo ThinkCentre M700 mini-tower running Debian 13, hosting a proxy and this website
 - `areia`: [Digilent Arty-S7](https://digilent.com/shop/arty-s7-spartan-7-fpga-development-board/) FPGA development board, with a Xilinx Spartan-7 FPGA chip and 256MiB of DDR3L RAM
+- `persephone`: LilyGO T-Display-S3 running a custom software stack
+- `tamamizu`: 
 
 ### Tools
 - `catra`: [Flipper Zero](https://flipperzero.one/) used as a digital multitool and as a development platform for [BEATRIX](#beatrix)
D src/russkij.md 
@@ -1,9 +0,0 @@
----
-title: Juniper Emily Rose Beatitudes
----
-
-# Джунипер Эмыли Роз Биятитудз {#juniper-beatitudes}
-
-## Этот веб-сяйт строится! {#under-construction}
-
-qwq
M src/template.html → src/template.html 
@@ -99,7 +99,7 @@ $body$
 <footer style="text-align: center">
 <span class="navlink"><a href="/index.html">English</a></span>
 <span class="navlink"><a href="/francais/index.html">Français</a></span>
-<span class="navlink"><a href="/russkij/index.html">Русский</a></span>
+<span class="navlink"><a href="/blog/index.html">Blog</a></span>
 </footer>
 </body>
 </html>