$ man shring
The shring (pronounced “shring”) is a small web of unix-y personal sites. the word is composed of “sh” for “shell” and “ring” for “ring”.
More specifically, shring is a webring. each site links to its “next” and “previous” neighbor. If you follow the links, you’ll eventually return to the page you started on.
Every shring member site is
There are no further qualifiers.
If a site meets these requirements, it’s shringworthy.
$ shring unix-y
We don’t attempt to formalize a definition. We all have some amorphous and generally interoperable idea of what “unix-y” actually means. In a sense, our understanding of what it means to be “unix-y” is in itself unix-y.
We don’t define unix-y because that would be un-unix-y.
Instead, we offer two contrasting, non-authoritative examples.
$ shring not unix-y
A unix-y personal site is not:
An seo sloptimized “website” that only functions as a portfolio for landing an entry level developer job where every post is about the latest frontend agentic javascript ml tokenizer agent and what it taught you about b2b sales.
$ shring example
A unix-y personal site can be:
Blogs about your experience learning new programming paradigms, accounts of tinkering with shell scripts, stream-of-consciousness rambles about text editors, essays on the impermanence of being, self-hosting tutorials, linux configuration advice, the philosophy of plaintext, comics about git commands, source code repositories, kernel de(output truncated)
Your website:
The “-y” in “unix-y” is important. If you (and by extension, your personal site) appreciate free software, the unix philosophy, hacking, and tinkering, then the shring welcomes you, os choice notwithstandding.
Although shring is proudly no-js, and you certainly get bonus points for a static, javascript-free website,
member sites are welcome to include javascript.
However, If your site makes use of bloated frameworks, runs poorly on older hardware, serves ads, or tracks its visitors, it does not belong in the shring.
To apply, compile the following information:
shring.sh/your-slug/nextshring.sh/your-slug/previousPlease email your application to daniel@ficd.sh.
You will receive a response via carrier pigeon within 300 business years. If you prefer to be contacted by message-in-a-bottle, include the name of the nearest body of water with an accessible shoreline, and your request will be accommodated.
Preferably before applying, add your shring links to your website:
shring.sh/your-slug/previousshring.shshring.sh/your-slug/nextYou are responsible for styling and positioning them however you see fit. Optional 88x31px banners are coming soon.
We also have a mailing list, which is used for announcements, discussions, patches, and more. It’s not required to join, but it allows for easier communication with other members. The mailing list is maintained by jdugan6240.
The source code for shring is available at git.ficd.sh. The webring “backend” (static pages with html redirects) is built using ringfairy.
Additional pages (including this one) are generated by a shell script. They are written in markdown, converted to html with pandoc, and applied to a minimal template with awk. A forgejo actions workflow automatically generates and deploys shring to sourcehut pages with curl.