veg/tmux-party
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

style: reword em-dashes; put colons inside bold run-in labels

Browse source 
Punctuation sweep across README, ROADMAP, and the script's comments:
em-dashes become colons, commas, or parentheses; bold list labels take
the colon inside the bold with lowercase text after. Comments only in
the script, no code changes.
This commit is contained in:
veg 2026-07-11 11:57:04 +00:00
parent ff92d812ad
commit be3fb049d2
3 changed files with 30 additions and 30 deletions
Download patch file Download diff file Expand all files Collapse all files

30
ROADMAP.md
View file

@ -3,49 +3,49 @@
Direction, not promises. Two rules govern everything below (README
§Security has the long form):
- **Accidents, not adversaries.** New checks earn their place by
preventing a plausible mistake — stale state, a typo, a race — not by
- **Accidents, not adversaries:** new checks earn their place by
preventing a plausible mistake (stale state, a typo, a race), not by
closing a hypothetical attack from a friend.
- **Social, not mechanical.** New features earn their place by
- **Social, not mechanical:** new features earn their place by
encouraging people to work together in a terminal, not by adding
machinery.
## Next — small, high value
## Next: small, high value
- **`party knock <name>`** — an uninvited group member pings the host
- **`party knock <name>`:** an uninvited group member pings the host
via `write(1)`: "veg wants to join fiesta". `party list` already
shows invite-only parties; knock completes that loop. The feature
most likely to cause spontaneous pairing.
- **`party log`** — per-party transcript via `tmux pipe-pane` into the
- **`party log`:** per-party transcript via `tmux pipe-pane` into the
per-party dir (group-readable so every attendee can grab a copy);
`party log --stop` ends it. "What did we do last night?" for
collectives, and the audit trail human+AI co-work needs.
- **`party clean`** — remove the caller's own crash leftovers (dirs
- **`party clean`:** remove the caller's own crash leftovers (dirs
they own whose socket is dead), turning the manual `rm -rf` recovery
in host's error message into a verb.
## Later
- **Group ergonomics** — the default `party` group needs root and a
- **Group ergonomics:** the default `party` group needs root and a
relog before anyone's first party. On boxes where everyone already
shares a group, `host` could offer (or default to) the caller's
primary group when `party` doesn't exist. Fits the trust model;
costs a little existence-confidentiality.
- **One liveness primitive** — fold `is_party_alive` into
- **One liveness primitive:** fold `is_party_alive` into
`party_conn_state`; two concepts where one would do.
- **Matrix** — live validation on NetBSD and DragonFly; one
- **Matrix:** live validation on NetBSD and DragonFly; one
interactive attach/role/switch pass per release (automated coverage
is all non-interactive).
## Resist — by design, not by neglect
## Resist: by design, not by neglect
- **No network transport.** Same-host is the perimeter; beyond it lies
- **No network transport:** same-host is the perimeter; beyond it lies
reinventing ssh.
- **No per-pane ACLs.** tmux can't enforce them; faking it with hooks
- **No per-pane ACLs:** tmux can't enforce them; faking it with hooks
would be a leaky abstraction. Document the limitation instead.
- **No config files, no plugin system, no ACL syscalls.** One POSIX
- **No config files, no plugin system, no ACL syscalls:** one POSIX
file that runs on a 30-year spread of UNIXes is the identity; the
2026-04 simplification that removed per-OS ACL dispatch is not to be
unwound.
- **Watch the file size.** Heavy why-comments are a feature; feature
- **Watch the file size:** heavy why-comments are a feature; feature
growth that pushes the single file far past its current size is not.