<feed xmlns='http://www.w3.org/2005/Atom'>
<title>slosh.git/web/index.html, branch v0.1.4</title>
<subtitle>an opinionated terminal multiplexer in C with programmable pane chrome</subtitle>
<id>https://git.sl0p.foo/slosh.git/atom/web/index.html?h=v0.1.4</id>
<link rel='self' href='https://git.sl0p.foo/slosh.git/atom/web/index.html?h=v0.1.4'/>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/slosh.git/'/>
<updated>2026-09-02T13:21:52Z</updated>
<entry>
<title>web: the released version in the hero, linking to the release</title>
<updated>2026-09-02T13:21:52Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-09-02T13:21:52Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/slosh.git/commit/?id=670add69317750ebc62f92662ea55d2e42439334'/>
<id>urn:sha1:670add69317750ebc62f92662ea55d2e42439334</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>web: contributing section, shorter</title>
<updated>2026-09-02T13:20:50Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-09-02T13:20:50Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/slosh.git/commit/?id=aea3e11f4cfa233db008076365e08a401c0e02a1'/>
<id>urn:sha1:aea3e11f4cfa233db008076365e08a401c0e02a1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>web: a contributing section -- the github and the discord</title>
<updated>2026-09-02T13:19:28Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-09-02T13:19:28Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/slosh.git/commit/?id=578f2fe4901fbb82ea93fe2125598327dfc9bb14'/>
<id>urn:sha1:578f2fe4901fbb82ea93fe2125598327dfc9bb14</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>web: no em dashes on the landing page</title>
<updated>2026-09-02T13:14:21Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-09-02T13:14:21Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/slosh.git/commit/?id=2aa0e70288ce40e2a576291144d626c134e1252b'/>
<id>urn:sha1:2aa0e70288ce40e2a576291144d626c134e1252b</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>web: the sessions step mentions shared attach</title>
<updated>2026-09-02T13:13:14Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-09-02T13:13:14Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/slosh.git/commit/?id=c61059374bcd09101f877521a54544fe4e8ec768'/>
<id>urn:sha1:c61059374bcd09101f877521a54544fe4e8ec768</id>
<content type='text'>
</content>
</entry>
<entry>
<title>web: chore</title>
<updated>2026-09-02T13:06:16Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-09-02T13:06:16Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/slosh.git/commit/?id=c94edfcd692e745408234483a35b5f7df926e619'/>
<id>urn:sha1:c94edfcd692e745408234483a35b5f7df926e619</id>
<content type='text'>
</content>
</entry>
<entry>
<title>web: chore</title>
<updated>2026-09-02T12:20:22Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-09-02T12:20:22Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/slosh.git/commit/?id=2dd4d89d32d9e4bca78c3e12a285667f1eb72ee3'/>
<id>urn:sha1:2dd4d89d32d9e4bca78c3e12a285667f1eb72ee3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>install: source tab clones from github</title>
<updated>2026-09-02T12:08:53Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-09-02T12:08:53Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/slosh.git/commit/?id=add400603fb02495b1a50bbf5e316b526ecbf3c0'/>
<id>urn:sha1:add400603fb02495b1a50bbf5e316b526ecbf3c0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>install: key enrollment commands right in the pacman tab</title>
<updated>2026-09-02T12:08:40Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-09-02T12:08:40Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/slosh.git/commit/?id=e18a4f1d41c777f42d64da3cb75e18d6a0f75415'/>
<id>urn:sha1:e18a4f1d41c777f42d64da3cb75e18d6a0f75415</id>
<content type='text'>
The three commands were a link away in contrib/arch; a repo whose
packages refuse to install without the key should hand them over
where the repo is advertised.
</content>
</entry>
<entry>
<title>public links: point at github.com/sl0p-foo/slosh instead of cgit</title>
<updated>2026-09-02T12:07:37Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-09-02T12:07:37Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/slosh.git/commit/?id=597135f7851e83e31d99fc9c97fbb087c3df4fce'/>
<id>urn:sha1:597135f7851e83e31d99fc9c97fbb087c3df4fce</id>
<content type='text'>
GitHub is the public interaction point now. The formula and PKGBUILD
fetch GitHub's /archive/ tarballs (same git-archive bytes, per-ref
stable); the PKGBUILD is bumped to 0.1.2 while at it, and its cd's
drop the v -- GitHub tag archives extract to slosh-X.Y.Z/. The cgit
remote stays for pushing; only published URLs change.
</content>
</entry>
</feed>
