FAQ — questions I'm not sure I've been asked but I think are useful to know.
       
       Q. How do I post an inline image?
       A. Run  base64 -w0 pic.png  (macOS: base64 -i pic.png) and put the output after  img:  on one line. GUI clients (Lagrange, Dillo) truncate big requests, so the reliable way is straight from the shell:  printf '/applets/interlog/interlog.lhs/append/ID\timg:%s\r\n' "$(base64 -w0 pic.png)" | nc gopher.someodd.zip 70  — swap /append/ID for /new to start a thread. The whole post must fit ~8 KB, so keep the image under ~6 KB; PNG and GIF pack best at that size, and the create/append prompt shows your exact budget. Bigger than that? Paste an http(s) image URL on its own line instead.
       
       Q. Can I post a raw gopher menu row?
       A. Yes. A line that is itself a complete 4-field gophermap row — <type><display>\t<selector>\t<host>\t<port> — passes through as a real menu item. A gopher query can't carry a literal TAB, so write \t (backslash-t) in your post and it becomes a real TAB on the way in. Example: IA nice image.\t/uploads/stella_maris.jpg\tgopher.someodd.zip\t70  renders as a clickable image item. The item-type chars: 0 text, 1 menu, 7 search, I image, h URL link.
       
       Q. Can I link out to other stuff?
       A. Yes — paste any URL, alone or in a sentence (the surrounding text becomes the label, with the domain in parens). HTTP(S) image URLs (.png/.gif/.jpg/.jpeg/.webp) stream through this server as inline image rows; other HTTP(S) URLs become web-link rows (h URL: items). Gopher URLs become a menu row of whatever type the URI declares — gopher://host/Icat.png is an image, gopher://host/0notes.txt is text, and so on.
       
       Q. Why does my post get rejected?
       A. Almost always truncation by your client, not this server. The server reads up to 8192 bytes, but GUI gopher clients chop the request short — Lagrange caps the query at ~1 KB (it inherits Gemini's request-line limit), and Dillo and others have their own small caps. Neither gopher RFC actually requires that: RFC 1436 only suggests selectors stay under 255 chars, and the URI RFC (4266) sets no limit at all — it's a client convention, not gopher's. So a big img: post arrives cut off, fails the completeness check, and is rejected rather than stored broken. Post images from the shell instead (see 'How do I post an inline image?').
       
       Q. What about animated GIFs?
       A. For inline posting (img:base64), yes — the completeness check accepts a complete GIF (trailer 0x3B), but most animated GIFs are well past the ~6 KB cap. For anything bigger, paste a URL on its own line instead: HTTP(S) image URLs stream through, gopher://host/Igif… links cross-server.
       
       Q. Where do my posts live?
       A. Plain text files under /applets/interlog/logs/, one per thread. The board keeps the 64 newest threads (oldest pruned), and each thread caps at 1024 KB.
       
       Q. Can I delete or edit a post?
       A. No. One post is one immutable line; one thread is append-only. The ring buffer eventually evicts old threads though, so if you can wait long enough …
       
       Q. What's gopher?
       A. RFC 1436, 1993. Hypertext, pre-web, menus over a flat protocol with one-character item types — text (0), menu (1), search (7), image (I), and so on. No JavaScript, and that's the point.
       
       Q. Who runs this?
       A. someodd.zip — a personal gopher server. Code at github.com/someodd; interlog is one of several .lhs applets under /applets/.
       
   DIR ← back to interlog