Readers searching for "web3 browsers" or "decentralized domain names" weren't finding the Browsers & web tools category because the blurb only talked about BCNR, which almost nobody types into a search box. Blurb reworded to: Web3 browsers and decentralized domain name resolvers. BCNR tooling that teaches Chrome, Firefox and other browsers to reach .x and the other decentralized TLDs. Same category, same scope — new terms up front so a crawler reading the sub-chip on /t/apps, the category hero on /c/browsers, or the <meta description> on either page sees the words a web3-curious reader would type to find it. The listing cards for Ariadne's Thread, Ariadne Navigator and Theseus Navigator inside the category pick up the SEO value by association. Single file: the blurb lives once in CATEGORIES and propagates to every surface that renders it. |
||
|---|---|---|
| deploy | ||
| public | ||
| scripts | ||
| service | ||
| .gitignore | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
Prometheus
The service behind prometheus.x — a standalone website that accepts app
listings, scans the binaries, generates APS1 records for publishers to sign,
and serves the browse pages.
The architecture decisions and the reasoning behind them live at
_coordination/sessions/prometheus-x-architecture.md.
Read that before touching the code; it answers the questions this directory
otherwise invites ("why isn't this on Sia?", "why isn't the admin on another
subdomain?", "why Node?").
service/ Node HTTP server, templates, scanner, storage, payments
public/ Static assets served under /static/
content/ Prose content in a form the templates render into pages
Run it locally
cd Prometheus
npm install # none yet; placeholder for when deps show up
node service/server.js
Opens on http://127.0.0.1:3700 by default. Override with PORT=xxxx.
Layout
The server is one node:http listener behind a trivial map-based router.
Pages are plain functions that return {title, description, body} and
layout() wraps them in the common document shell. Static files under
public/ are served directly.
There's no framework and no templating engine on purpose — a site this small does not earn a dependency surface, and the response-rendering path is short enough to read at a glance.