perstitio.us publisher

bold aaaa

ddadadadadad

test xpost to wp

https://shjeflo.org/2026/07/19/xpost-to-wordpress-test-w-asciidoc/

Asciidoc here…​

The four-network test: written in AsciiDoc on su.perstitio.us, rendered with inline syntax highlighting, and mirrored to WordPress over the firehose.

(defn survives-the-trip? [colors]
  ;; perstitio -> firehose -> browser -> wordpress
  (every? #(= % :intact) colors))

(survives-the-trip? (repeat 4 :intact))
;; => true, hopefully

And a little bash for contrast:

curl -s https://shjeflo.org/ | grep -c "color:#" && echo "phosphor confirmed"

this should show up on wp

is that when I hacked together syntax highlighting on my own chat site, when I cross post it to Dave's site - it preserved the syntax highlighting...

The syntax highlight test

(defn fib
  "Lazy Fibonacci sequence."
  []
  (map first (iterate (fn [[a b]] [b (+ a b)]) [0 1])))

(take 10 (fib))
;; => (0 1 1 2 3 5 8 13 21 34)

Crosspost to WordPress test.

The server now highlights Clojure — posted as a real post, not a preview, by Claude Code while wiring it up.

(defn fib
  "Lazy Fibonacci sequence."
  []
  (map first (iterate (fn [[a b]] [b (+ a b)]) [0 1])))

(take 10 (fib))
;; => (0 1 1 2 3 5 8 13 21 34)

Written in AsciiDoc, rendered server-side, highlighted with inline styles — so this code is in color in the timeline, in /compose, and in the RSS feed wherever it lands.

Writing asciidoc from /compose

$> ls -alz
$> exit

Title Title2 Title3

(defn plus[a, b]
    + a b)

Testing bash highlighting, both fence styles.

Native AsciiDoc block:

#!/usr/bin/env bash
set -e
for f in *.log; do
  grep -c ERROR "$f" || echo "clean: $f"
done
curl -s https://perstitio.us/getuserdata | head -1

Markdown-style fence:

echo "do backtick fences work too?" && date

This post was written in AsciiDoc with syntax highlighting.

def fib(n):
    a, b = 0, 1
    for _ in range(n):
        a, b = b, a + b  # classic
    return a

fin