Yarrlist Github Work Apr 2026

A dev named Mara opened the repo one rain-soaked night. The README promised a "curated list of coordinates, legends, and curiosities." The first commit was titled "initial haul" and contained a single file, maps.json. Inside, instead of tidy URLs and package names, there were scraps of hand-drawn islands, each with a name written in looping ink: Cinderpoint, The Hollow Reed, Night-Glass Shoals. Alongside each island were coordinates that pointed not to ocean charts but to small patches of land in unexpected cities: a triangular park behind a library, an abandoned pier, the roof of an old observatory.

At the Hollow Reed coordinates — an alleyway between a noodle shop and a tailor — she found a tin can wired to the underside of a lamp. Inside the can was a scrap of paper with a new coordinate and a line of code: a short snippet in JavaScript that, when run, printed three words: "Follow the tides." yarrlist github work

Mara reopened an issue one winter. She typed only: "Still following." Someone named captain-echo replied with a commit: a small script that printed a single line and then exited. A dev named Mara opened the repo one rain-soaked night

The things they found were small but precise and odd. A brass key with no matching lock. A faded photograph of a ship at dock, dated in a hand none of them could place. A lockbox containing a single silver coin stamped with an unfamiliar crest and a note: "To the next finder, bring a lantern." Alongside each island were coordinates that pointed not

YarrList never became a mainstream project. It wasn't a framework or a library; it was a common ground for strangers who wanted maps that led to more than endpoints. Mara kept contributing, sometimes adding clues she found herself, sometimes writing small scripts that would softly nudge newcomers into the right frame of mind: "Go slow. Bring a lantern. Leave a scrap."