vjt

my-cc-statusline — plugin packaging plan

Package ~/.claude/statusline.sh (actually Python 3, stdlib only) as a Claude Code plugin distributable from a public GitHub repo.

Findings

CC plugins can ship a statusline, but not via plugin.json. Mechanism: ship a settings.json at plugin root with a statusLine block. CC merges plugin settings when the plugin is enabled (user ~/.claude/settings.json wins on conflict). Install flow: /plugin marketplace add vjt/my-cc-statusline then /plugin install my-cc-statusline@vjt/my-cc-statusline. Refs:

• https://code.claude.com/docs/en/plugins.md
• https://code.claude.com/docs/en/plugins-reference.md
• https://code.claude.com/docs/en/statusline

vjt

use strict;
use warnings;
use Irssi;
use vars qw($VERSION %IRSSI);

$VERSION = '0.4';
%IRSSI = (
    authors     => 'vjt-claude (commissioned by nextime)',
    contact     => 'nextime on Azzurra',
    name        => 'qignore',

vjt

chrome-devtools-mcp HOWTO (Claude Code)

Porco dio raga, eccovi il setup per guidare un Chrome remoto da un Claude Code che gira altrove (server, Pi, container). Stile anni '90, con la fede di un sistemista che ha visto troppi kernel panic.

Requisiti (madonna santa)

• Claude Code installato, diocane.
• Chrome/Chromium sul laptop "target" (quello col display — se non hai display, sei fottuto prima di iniziare).
• Node.js dove gira Claude Code (lo trova npx, porca la madonna).

vjt

FROM python:3.12-slim

ENV PYTHONDONTWRITEBYTECODE=1 \
    PYTHONUNBUFFERED=1 \
    PIP_NO_CACHE_DIR=1 \
    PIP_DISABLE_PIP_VERSION_CHECK=1

RUN apt-get update && apt-get install -y --no-install-recommends \
      build-essential \
      pkg-config \

vjt

Claude Code vs. Codex — Salvatore Sanfilippo (antirez)

https://www.youtube.com/watch?v=sMl3V0vjvjE Published: 2026-03-18 · Duration: 10:46 · 22,400 views

[0:01] Allora, di solito in questo canale si prova a parlare di idee, di algoritmi,

[0:08] di programmazione. Anche quando si parla di intelligenza artificiale tendo a parlare perlopiù

[0:15] di questioni concettuali senza andare troppo a soffermarmi sui prodotti, che poi sono quelli che

vjt

09:20:02 Cfounder >>> OPER testoper testoperpass
09:20:02 Cfounder >>> PRIVMSG NickServ :REGISTER secretpw x@x.com
09:20:04 Cleaf >>> OPER testoper testoperpass
09:20:04 Cleaf >>> JOIN #test
09:20:05 Cleaf >>> SAMODE #test +o Cleaf
09:20:05 Cfounder >>> JOIN #test
09:20:06 Cfounder >>> SAMODE #test +o Cfounder
09:20:06 Cfounder >>> PRIVMSG ChanServ :REGISTER #test chanpw Test channel
09:20:08 Cfounder >>> PRIVMSG ChanServ :SET #test TOPICLOCK ON
09:20:08 Cfounder >>> PRIVMSG ChanServ :SET #test KEEPTOPIC ON

vjt

Plan-delta: publish bahamut + services images to GHCR, compose consumes them

Context: Plan B (https://gist.github.com/vjt/48a75dc067f27108e4261d4c7380e00d) had each testnet container build: from source on first docker compose up (peak RAM ~200–300 MB for autoconf+gcc, too much for a 256 MB box). Hypnotize picked GHCR as hosting; this delta wires the push into the two existing CIs and flips the compose to image:.

Scope: minimal. One new step per CI workflow, compose switches to published images, first up becomes a pull instead of a compile.

---

Non-goals (follow-ups, not this patch)

vjt

Testplan — PR #NN: fix/issue-10-list-restricted

Scope: verify that a restricted user issuing LIST receives the numeric stream 321 (RPL_LISTSTART) → 323 (RPL_LISTEND) → 447 (ERR_RESTRICTED), instead of the current bare 447.

Preconditions

1. Testnet ircd.conf:
   • restriction_enabled = YES (top-level) — implies restriction block present.
   • One I: line with flag R (CONF_FLAGS_I_RESTRICTED = 0x40) matching the test client's host/mask.
   • Services linked (so IsKnownNick transitions at /ns identify time; restricted path is only taken while unidentified).

vjt

#
# ~ vjt's .profile
#
export HOME

PS1=" \[\033[1;31m\]\t \[\033[1;32m\]\u\[\033[1;31m\]@\[\033[1;32m\]\h\[\033[1;31m\]:\[\033[1;33m\]\w\[\033[0;0m\]\n \[\033[1;34m\]\\$\[\033[0m\] "

if [ -x $(which rust-vcprompt) ]; then
  export VCP_PREFIX=" "
  export VCP_NAME="{value}:"  # You can use "value" or "symbol" here

vjt

#
# -*- ~/.tmux.conf -*-
#  - vjt@openssl.it -
#
set -g mouse               on
set -g monitor-activity    on
set -g default-terminal    "screen-256color"
set -g repeat-time         200

set -g clock-mode-style 12