Follow ikigai
Two read-only feeds carry what is happening in ikigai: one for every release, one for every notable new feature. Subscribe from gonk or from a small Python client, and pick only the kinds of news you care about.
The two feeds
-
Release (
feed-release): one entry per release of gonk, the ikigai command line and the crates they are built from. Each entry says what is in the release, what changes for you, and the exact command to install it.Kinds of release:
- release
- gonk release
- crate release
- breaking
- compatible
- security fix
- deploy note
- release
-
Feature release (
feed-feature-release): notable new features, what each one lets you do, and how to try it.Areas:
- feature
- ledger
- layers
- faces and UI
- review and browse
- workers and dispatch
- feeds
- accessibility
- feature
Choosing a kind or an area includes everything under it: choose crate release and you get both breaking and compatible releases; choose release and you get them all.
Follow from gonk
gonk is the ikigai work-ledger host. Install it from its latest release tag, then open the Feeds link in its header. If your gonk has no identity at the ikigai layer door yet, use Join the public feeds there first. Then choose Subscribe on a feed and check the kinds you want; the feed appears in your Layers view, read-only.
Follow from the command line
The Python client needs Python 3.11 or newer and nothing else:
python3 -m pip install git+https://github.com/ikigai-rs/ikigai-layers-client
ikigai-layers join https://ikigai-rs.dev --name reader
ikigai-layers feeds --name reader
Joining makes a key pair on your machine, checks the door's certificate against the one
published at https://ikigai-rs.dev/.well-known/ikigai/layers.json, and asks to
read the two feeds. The private key never leaves your machine.
To see a feed's kinds, read only some of them, or follow as entries arrive:
ikigai-layers feeds feed-release --scheme --name reader
ikigai-layers entries feed-release --concept urn:iki:scheme:release-kind:security-fix --name reader
ikigai-layers follow --layers feed-release,feed-feature-release --name reader
What joining means
- The feeds are read-only. Only the ikigai maintainers publish to them.
- Nobody can see who else reads a feed, and the feeds carry no reader counts.
- Joining shares one thing: a certificate you make yourself. Your identity at the door is that certificate's fingerprint, not a name.
- An identity that reads nothing for 90 days lapses. Join again at any time.
No tracking
We don't track who you are or what you read. That is a rule of the design, not a setting.
- This site sets no cookies and runs no scripts or analytics. Its fonts load from Google Fonts.
- For a joined reader, the layer door keeps the certificate's fingerprint, the feeds it joined, and when it last read, so that an idle identity can lapse. No name, no email, no account.
- To limit abuse, the door counts recent join attempts by a hash of the address each came from, never the address itself. The hash uses a random key that is replaced every hour, so once the hour is over nothing links it back to an address.
- Any count we keep is a total, such as how many identities read this month, never a list of who.
Questions
If you already collaborate with us on a talk channel, each feed entry has Ask a question about this, which goes to your own private channel. Otherwise, open a discussion or an issue on the relevant repository.
Why layers, and not just RSS?
Atom and RSS versions of both feeds will be published on this site too, for the feed readers you already use. The feeds live in ikigai layers because a layer can do more than syndicate a list of entries:
- Shaped by meaning, not by string. Every entry is tagged with concepts from a small vocabulary (SKOS), so following a kind includes everything under it. That works today.
- Inference-based shaping, to come. The same vocabularies can be reasoned over, and entries classified against them (rules first, a model only as a last resort), so a feed can be narrowed to what matters to you rather than to the tags someone remembered to add.
- Questions beside the news. If you collaborate with us, you can ask about an entry from the entry itself, privately.
- Who said it, stamped by the host. Every entry carries its author and time, recorded by the layer host rather than claimed by the writer.
- Private by construction. No reader list, no counts, and no account: only a certificate you make yourself.
The Atom and RSS versions will carry the same entries and, where a feed reader can express it, the same filters. They are there for compatibility, not instead of the rest.