slosh.git/web, branch v0.1.3 an opinionated terminal multiplexer in C with programmable pane chrome https://git.sl0p.foo/slosh.git/atom/web?h=v0.1.3 2026-09-02T13:21:52Z web: the released version in the hero, linking to the release 2026-09-02T13:21:52Z user user@clank 2026-09-02T13:21:52Z urn:sha1:670add69317750ebc62f92662ea55d2e42439334 Stamped by build-site from ./VERSION, which the release invariant keeps equal to the newest tag -- so the page cannot advertise a version that was never cut, and nothing is bumped by hand. web: contributing section, shorter 2026-09-02T13:20:50Z user user@clank 2026-09-02T13:20:50Z urn:sha1:aea3e11f4cfa233db008076365e08a401c0e02a1 web: a contributing section -- the github and the discord 2026-09-02T13:19:28Z user user@clank 2026-09-02T13:19:28Z urn:sha1:578f2fe4901fbb82ea93fe2125598327dfc9bb14 The multiplayer patch proved the repo takes patches; say so where people can see it, and give the not-yet-an-issue conversations somewhere to happen. web: no em dashes on the landing page 2026-09-02T13:14:21Z user user@clank 2026-09-02T13:14:21Z urn:sha1:2aa0e70288ce40e2a576291144d626c134e1252b Colons, commas and semicolons where twelve of them stood. People read an em dash as the house style of a language model, and the landing page is not the place to argue. web: the sessions step mentions shared attach 2026-09-02T13:13:14Z user user@clank 2026-09-02T13:13:14Z urn:sha1:c61059374bcd09101f877521a54544fe4e8ec768 web: chore 2026-09-02T13:06:16Z user user@clank 2026-09-02T13:06:16Z urn:sha1:c94edfcd692e745408234483a35b5f7df926e619 webdemo: version from contrib/version, published by ship 2026-09-02T12:47:30Z user user@clank 2026-09-02T12:47:30Z urn:sha1:3578eefea5b53bce2c1dbbc7f104f3cf85c8aa5b The demo's Makefile said VERSION := 0.1.0 by hand, so the in-browser slosh announced a release two tags old no matter what was built into it. It now derives from contrib/version like every other artifact, suffixed +webdemo so the guest build names itself. And ship gains a website step: the site (demo included) is rebuilt from the tag checkout and published as part of a release, so the demo cannot fall behind again. web: the real site is the only site, and web/publish ships it 2026-09-02T12:22:37Z user user@clank 2026-09-02T12:22:37Z urn:sha1:c36d7d07060f5d49a068724bc889a14460f16853 The coming-soon gate (FULL=1) and its page go: the site is finished enough to be the default. web/publish (make www-publish) builds, refuses to sync a tree that does not look like the site, and rsyncs to /opt/slosh -- around /arch, which contrib/ship owns, and around the served demo when a NO_DEMO build has none to offer. web: chore 2026-09-02T12:20:22Z user user@clank 2026-09-02T12:20:22Z urn:sha1:2dd4d89d32d9e4bca78c3e12a285667f1eb72ee3 web: deprecate install.sh and the served dist/ 2026-09-02T12:19:15Z user user@clank 2026-09-02T12:19:15Z urn:sha1:7805e90209c59a9a4a1ff9cfdd645e45a2bb6297 GitHub releases host the binaries now; installing is a package manager (brew, pacman) or a manual download from the releases page. The curl|sh script and slosh.foo/dist are gone -- one less channel to keep in sync, one less thing to trust.