progrium

SSH and Plan 9 rcpu Compared

Executive summary

SSH and Plan 9’s modern rcpu stack solve superficially similar problems, but they embody very different architectural bets. SSH is a single, standardized, layered protocol family: a transport protocol provides encryption and host authentication, a user-authentication protocol authenticates the client, and a connection protocol multiplexes multiple logical channels over one encrypted tunnel. That design makes SSH broadly interoperable and feature-rich, especially for shells, port forwarding, X11 forwarding, agent forwarding, and subsystem execution. The core architecture is explicitly defined in RFC 4251-4254. citeturn29view0turn29view1turn29view2turn29view3

Plan 9’s rcpu stack is different in kind. It is not one giant transport with a large built-in channel taxonomy. Instead, it is a composed system service: rcpu, rimport, rexport, and rconnect are front-end commands; tlssrv/tlsclient provide mutually authenticated encrypted

progrium

Translating WebUSB Into USB/IP Wire Packets

Executive summary

The clean way to think about this bridge is not “WebUSB emits USB/IP.” The practical model is: your bridge acts as a USB/IP server, the Linux side acts as the normal USB/IP client, and every incoming USB/IP request is executed against a real device through WebUSB, then answered with the corresponding USB/IP reply. In other words, the Linux side remains authoritative for URB submission order and sequencing; the browser side is an execution engine plus descriptor source. USB/IP itself uses a short discovery/import phase (OP_REQ_DEVLIST/OP_REP_DEVLIST, OP_REQ_IMPORT/OP_REP_IMPORT) followed by a persistent URB channel carrying USBIP_CMD_SUBMIT, USBIP_RET_SUBMIT, USBIP_CMD_UNLINK, and USBIP_RET_UNLINK. All integer fields in the USB/IP protocol are in network byte order. citeturn10search0turn4view0turn5view0

For actual I/O, the mapping is straightforward for generic control, bulk, interrupt, and most *

progrium

HTTP Filesystem Protocol Specification

Overview

The HTTP Filesystem Protocol provides a RESTful interface for performing POSIX-like filesystem operations over HTTP. It enables hierarchical file and directory manipulation using standard HTTP methods with filesystem-specific metadata encoded in HTTP headers.

Protocol Design

Core Principles

progrium

FROM node:22-alpine
ARG VSCODE_VERSION=1.103.2
RUN apk add -u krb5-dev libx11-dev libxkbfile-dev libsecret-dev git build-base python3
RUN git clone --depth 1 https://github.com/microsoft/vscode.git -b $VSCODE_VERSION
WORKDIR /vscode
RUN npm i
RUN npm run gulp vscode-web-min

progrium

const w = new Wanix()
Object.getPrototypeOf(w)
// {readFile: ƒ, writeFile: ƒ, readDir: ƒ, exists: ƒ}
await w.readDir(".")
// ['dom/', 'fsys/', 'proc/', 'term/', 'vm/']


await w.readDir("fsys")
// ['ctl', 'new/']
await w.readDir("fsys/new")

progrium

io package

Core interfaces

type Reader interface {
	Read(p []byte) (n int, err error)
}

type Writer interface {
	Write(p []byte) (n int, err error)

progrium

Sponsor on GitHub to get access to this POC

progrium

#!/bin/sh
apptron app indicator - ./icon.png <<MENU |
Timers
	5 seconds
	10 seconds
	30 seconds
Say Hello
---
Quit
MENU

progrium

function dateTimeFormat(timestamp, locale, str, ...opts) {
	const d = new Date(timestamp);
	return str.replace(/{(\d+)}/g, function(match, number) { 
		return typeof opts[number] != 'undefined'
			? new Intl.DateTimeFormat(locale, opts[number]).format(d)
			: match;
	});
}

console.log(dateTimeFormat("2021-11-19T19:19:36.598071-06:00", "en", "{0} at {1}!", {dateStyle:"short"}, {timeStyle:"long"}))

progrium

// styling module provides a helper for building style
// and class attributes for elements.

type Styling = string | Object | Style | (() => boolean);
type ConditionedStyle = [string, () => boolean];

export function from(...styling: Styling[]): Style {
    return Style.from(...styling);
}