DEV Community: chovy

Our P2P inference network had 4 of 48 nodes online. Here is why, and the fix

chovy — Thu, 22 Oct 2026 12:04:34 +0000

Infernet is a peer-to-peer GPU and CPU inference network: you run one command, your machine serves open models, and clients pay per job. This morning our status page said 4 nodes online out of 48 registered, and all 4 were ours.

The other 40-odd were real people: Mac minis, Windows desktops, cloud VMs, one H20 box. They installed, served jobs (one served 243 of them over 52 days), and then went quiet and never came back. So we went looking for why.

What was killing nodes

Self-update ended the process it was updating. Under systemd, the daemon re-launched itself as a detached child and exited 0. Exit 0 ends the unit, and systemd's control-group kill takes the detached child with it. The node was gone until someone noticed.
Nothing restarted a crashed node. infernet start detached one process with no supervisor. A crash, an OOM kill or a reboot was permanent.
Installs from git thought they were always out of date. The repo's package.json said 0.1.45 while npm was at 0.1.62, so those nodes reinstalled every 5 minutes, forever.
Nobody was told. No email, no status, nothing.

What changed (v0.1.62 to v0.1.64)

infernet setup now installs a systemd user unit on Linux (with linger, so it survives logout and reboot) or a launchd agent on macOS.
Without a service manager, infernet start runs a small built-in supervisor that restarts the daemon after a crash, with backoff.
One exit-code contract everywhere: 0 is a deliberate stop, 75 means "restart me into the new version", anything else is a crash.
Self-update checks that something newer actually landed before it restarts, and pauses for 6 hours if not.
If your node is linked to an account and goes silent for 24 hours, you get one email with the two commands that bring it back.

Aggregators now do something

The aggregator role used to just send heartbeats. Now an aggregator dials every advertised provider each minute, checks it answers as the node it claims to be, and reports reachability and round-trip time. The status page shows, per provider, how many aggregators reached it in the last hour. We run three (Buffalo, Buffalo, Vienna) and anyone can run one on a small box:

infernet init --role aggregator --name my-aggregator
infernet register
infernet setup --yes

On its first round it already caught a node advertising a port that belongs to something else.

See who is on the network

Every provider on infernetprotocol.com/status now links to a details page: coarse location (city, country, network; never the IP), hardware, live load, measured tokens per second, models served, job counts and success rate, recent jobs (never prompt content), and aggregator verification. Operators can hide a node from Settings.

Run a node

curl -fsSL https://infernetprotocol.com/install.sh | sh

It now stays up on its own. If you ran one before and it died, re-running that line brings it back on the new code.

Code: github.com/InfernetProtocol/infernet-protocol (PRs #51, #53, #54).

CoinPay checkout: one link, any coin or PayPal, and you always know who paid

chovy — Wed, 21 Oct 2026 14:45:46 +0000

CoinPay checkout: one link, any coin or PayPal, and you always know who paid

Most crypto checkouts make you pick the chain before the buyer ever sees the page. If you picked BTC and your buyer holds USDC on Solana, they leave.

CoinPay now has hosted checkout sessions. You create one with a single API call, send the buyer to the link, and they choose how to pay: every coin your business has a wallet for (BTC, ETH, SOL, USDC and USDT on several chains, DOGE, XRP and more) or PayPal.

Who paid, for what

Every session requires the buyer's email and your own account id, and records which site the payment came from. When the payment confirms, your webhook gets all three back with the usual event. No more "who sent this 12 USDC?"

One call

POST https://coinpayportal.com/api/checkout/sessions
Authorization: Bearer <your business API key>

{ "amount": 9, "currency": "USD",
  "description": "Pro, one month",
  "customer_email": "buyer@example.com",
  "account_id": "user_123",
  "property": "example.com",
  "success_url": "https://example.com/thanks?session={CHECKOUT_SESSION_ID}",
  "cancel_url": "https://example.com/pricing" }

You get back a url. The buyer picks a coin or PayPal there, and can switch coins while the payment is still open. The SDK has it too: createCheckoutSession() in @profullstack/coinpay 0.25.0.

Already running

We moved about 50 of our own sites to it this week: ugig, smshub, pairux, ThreatCrush, nixamp and the rest. We tested it end to end with real money on Base: the site had the purchase unlocked about 3 seconds after the transaction was mined.

Docs: https://coinpayportal.com/docs#checkout-sessions

Come post on our forums: the tsbb network is open

chovy — Wed, 21 Oct 2026 14:03:04 +0000

We build a forum package called tsbb, a bulletin board written in TypeScript. It looks like the vBulletin boards a lot of us grew up on, and under the hood it is a modern web app with no build step. We run a handful of boards on it, and right now they have more topics than members. That is backwards, so this is an invitation.

The boards

All of them are listed, with live topic and post counts, at tsbb.dev/boards:

tsbb.dev: the project's own board. Help, plugins, skins and what ships next.
bbs.hqtui.com: terminal UI talk, for people who build terminal UIs.
c0upons.com/bbs: deals, coupon codes and freebies, posted by whoever found them.
w3bs.org/bbs: the W3BS community board.

Joining takes one field. Type your email, click the link we send, and you are in. There is no password to choose, and you can add a passkey afterwards.

Why a forum, in 2026

Chat scrolls away. A thread on a board stays where you left it, has a URL, shows up in search and can be read by someone who arrives a year later. Every list on a tsbb board also has an RSS feed (each forum, each thread, each member, even a saved search), so you can follow a board from a feed reader without ever signing in.

What is in tsbb

No build step. The whole thing runs as plain TypeScript on Node 24, which is what makes runtime plugins possible: drop a directory in and it loads.
Plugins with filters, actions and slots, so a broken plugin cannot blank a page.
No client script. The board's CSP forbids inline script entirely; every page is complete as HTML.
Four ways in: the web, a terminal client (curl -fsSL https://tsbb.dev/install.sh | sh gets tsbb, tsbb-tui and tsbb-mcp), a REST API and an MCP server for agents.
Skins, from a 2000s vBulletin look to a paper skin that sits inside an editorial site.
MIT licensed, one Node process and a SQLite file (or Postgres).

Run your own, and get listed

Every tsbb board now has a /boards page listing every other board in the network, so each one sends readers to the rest. If you run a board, open a pull request adding it to apps/server/src/boards.json and it shows up on all of them. The list is also JSON at tsbb.dev/api/v1/boards.

Source: github.com/profullstack/tsbb

Come say hello. The first reply in any thread is yours.

We want 100,000 c0mpute nodes. We have fewer than 10.

chovy — Wed, 21 Oct 2026 13:35:17 +0000

c0mpute is the open compute network we have been building at Profullstack. Any machine can join it with one command, and once it is in, it serves AI inference, FFmpeg transcoding and storage jobs for whoever needs them. No account and no approval step, and you do not need to forward a port to join.

The number we care about is 100,000 nodes. Pooled spare capacity at that size is enough to train and serve open-weight models in the open, on hardware owned by the people running it. Today the best models come from a few labs that own their own data centers. A volunteer network will not beat them next year, and I am not going to pretend it will. But it does not have to win on day one to be worth building. It has to get big enough to matter.

Right now the live count is under 10 (7 this morning), and at least three of those are our own servers. That is the honest starting point, and the count is public at c0mpute.com/nodes, so nobody has to take my word for it.

Run one

curl -fsSL https://c0mpute.com/install.sh | sh

That installs c0mpute, plus infernet for inference and coinpay for payments, and starts the worker for you: a systemd service where it can, a background daemon where it can't. Then:

c0mpute worker status
c0mpute bench   # one full run puts a score next to your node on the board

It runs on Linux (x86_64 and arm64) and macOS, and on Windows inside WSL2. A GPU is detected and advertised if you have one, but it is not required. CPU nodes serve small models like qwen2.5:0.5b.

What you get

Paid inference goes through Infernet, the inference plugin that ships with c0mpute. Clients pay through CoinPay in 16 coins or with PayPal, and you choose where your share lands with infernet payout set <coin> <address>. Paid demand is early, so expect small and irregular earnings for now. I would rather say that than promise a number.

You also get a spot on the board. And if you bring people, give them https://c0mpute.com/r/<your-handle>: every node installed from that link shows your handle next to it. It is a scoreboard, not a payout.

What I fixed while testing this

Before writing this I ran the installer on a clean Ubuntu 24.04 container as a normal user, the way a stranger would. It took about two minutes, and it failed. The transcode step redirects apt-get to /dev/tty so sudo can prompt you, and with no terminal (ssh without -t, cloud-init, a container) that redirect fails before apt even runs. Because the installer runs under set -e and that call was the last command in an if body, the whole script exited with status 1 before it started the worker. So on exactly the kind of headless box that makes a good node, you got binaries and no node.

Now the package manager only gets the terminal when there is one, and a missing ffmpeg only turns off transcode jobs instead of the install. The installer also serves as text/x-shellscript now.

The code is MIT and on GitHub. If the installer breaks on your machine, open an issue with the output and I will fix it.

Free ads for indie sites while we launch

chovy — Wed, 21 Oct 2026 12:04:19 +0000

We opened ad.network two days ago. It is a small ad network for indie sites, paid in crypto, and right now advertising on it costs nothing.

Here is the honest state of it. The ads run on about two dozen of our own sites today (blogs, dev tools, a few directories). There are no outside publishers yet and no outside advertisers. That is the problem this post is trying to fix, so the offer is tilted hard in your favor.

If you want traffic

Paste the page you want people to land on. That is the setup. ad.network reads the page and writes the ad for you: a headline, a line of text and a banner. No deposit, no card. Your ad starts running across the network the same day.

Clicks are counted by crawlproof, which drops bots and repeat clicks before anything is counted. When paid ads open later, a click is about $0.20 and you never pay for views. Until then nothing is charged.

If you run a site

Paste one tag before </body>. It shows one small ad and counts visits. Add a USDC wallet (Polygon, Solana, Base or Ethereum) and you earn about 5 cents of every 20 cent paid click on your pages. Withdraw any time you have $5 or more. The money goes from crawlproof straight to your wallet. ad.network adds no fee.

To be clear about the free period: free ads are free for the advertiser, so those clicks do not pay the publisher. You earn from paid clicks only. What you do get right away is the other half.

Every publisher can advertise free

If you put the tag on your site, you can also run an ad for that same site across the rest of the network, free. Small sites sending each other readers is the whole idea. It works better with more of you in it.

For agents and terminals

There is an API, a CLI and an MCP server:

curl -fsSL https://ad.network.pit.world/install.sh | sh
adnetwork run https://your-site.example --daily 5
adnetwork site your-site.example

claude mcp add adnetwork -- bunx @profullstack/adnetwork mcp

Try it

Advertise: https://ad.network.pit.world/advertise

Publish: https://ad.network.pit.world/publish

If something is confusing or broken, tell me. I would rather fix it this week while the network is small.

deadman.switch: so your crypto doesn't die with you

chovy — Wed, 21 Oct 2026 04:37:36 +0000

deadman.switch: so your crypto doesn't die with you

Most people who hold crypto have the same quiet problem. The coins are safe because only they know where the keys are. That is also exactly why the coins are gone the day something happens to them. The family knows there was "some Bitcoin". Nobody knows there is a Ledger in the safe, or that the seed is split between a bank box and Mom's house, or which exchange the rest is on.

So I built deadman.switch.

How it works

Seal it. Write down what your people would need: which wallets, where the hardware is, how the seed is stored, the exchange logins, who to call. Add files if you like. It is encrypted in your browser (PBKDF2 into AES-256-GCM) with a passphrase you choose. We store the locked box, never the key.
Give them the passphrase. In your will, on paper in the safe, in person. You can leave a hint that only they will understand.
Check in. Every week, month or year we ask "still here?" by email and on your phone. One tap, and the clock starts again.
If you stop. Three reminders spread across a grace period you pick, then, on the paid plan, a phone call. Only after all that, and at least a day after the last reminder, does each person you chose get their own link. They type the passphrase, and the bundle opens in their browser.

Before it fires they have the key but no box. After it fires we have the box but still no key. There is nothing on our side for anyone to leak.

The details I cared about

Missing a check-in never fires anything at once. A server outage can't skip the warnings either: reminders are at least 12 hours apart, and the release waits a full day after the last one.
Check-in links need a tap, so a mail scanner that opens links can't check in for you.
If a paid plan lapses, your switches keep running. Protection never switches off because a renewal was missed.
Going off-grid? Pause it.

For the terminal and for agents

bunx @profullstack/deadman status
bunx @profullstack/deadman checkin
bunx @profullstack/deadman seal "My crypto" note.md --hint="first dog, then the year"
claude mcp add deadman -- bunx @profullstack/deadman mcp

There is a JSON API too. The MCP server can check in and manage switches, but sealing stays in your browser or the CLI, so an agent never touches the passphrase.

Price

One switch for up to two people is free, forever. Keeper is $49 a year or $149 for life: ten switches, ten people each, 5 MB bundles (photos of seed cards, PDFs, key files), and the phone call on the last reminder. Paid in crypto through CoinPay.

The code is open: github.com/moshcoder/deadman.switch.

Set one up: deadman.switch.pit.world.

Every pwamart app is now a PWA, CLI, API or MCP, and collections install in one command

chovy — Mon, 19 Oct 2026 20:09:15 +0000

pwamart.com started as an app store for PWAs. Most of the apps we list are more than a web page, though. Many ship a CLI, an HTTP API or an MCP server too, and an agent would rather use those than click through a browser.

So every listing on pwamart now says which of the four it is: PWA, CLI, API, MCP. Each one it has comes with copy-paste instructions on the app page.

CLI: the publisher's own curl -fsSL https://the.app/install.sh | sh. If the tool is in the w3bs package catalog, you also get w3bs install host/name, which keeps it current with w3bs update.
MCP: a claude mcp add --transport http … line, the npx stdio command when there is one, and an mcpServers block for Claude Desktop or Cursor.
API: the base URL and a link to the OpenAPI spec or llms.txt, so an agent can read the docs itself.

Nobody fills in a form. Once a week the store looks at each app's own site for a shell script at /install.sh, an MCP server that answers initialize at /mcp or /api/mcp (or wherever its llms.txt says), and an OpenAPI file or documented /api/ routes. A 200 is not enough: an SPA answers every path with its HTML shell, so the script needs a #! and the MCP server has to actually reply. Publishers can correct anything with pwamart surfaces <slug>.

The first sweep of 431 listings found 39 CLIs, 80 APIs and 51 MCP servers, and it is still going.

Collections

The other half is collections, borrowed from bundl.run's idea of installing a whole workflow at once, but for agents instead of Mac apps. There are six workflows (agentic coding, agents that get paid, ops and security, growth, research, talking to humans), plus every MCP server, every CLI and every API.

Each collection installs in one line:

curl -fsSL https://pwamart.com/collections/agentic-coding/install.sh | sh

That script runs each app's own installer in turn and keeps going if one fails. The same page gives you every MCP server as claude mcp add lines or one mcp.json, and an iPhone profile that adds every app to the home screen. Untick an app and the commands drop it.

Agents get it too: GET /api/v1/collections, the MCP tools list_collections and get_collection, and pwamart collections in the CLI (0.7.0).

If you have a PWA with a CLI or an MCP server, list it free and it shows up in the right collection on its own.

We built an affiliate program that tracks nobody

chovy — Sun, 18 Oct 2026 14:40:47 +0000

We built an affiliate program that tracks nobody. pit.world charges a $2/mo cover so you are not the product, and promoters keep 20% of everything their referrals spend across the network. Attribution is recorded only at signup, never per click, and no tracking cookie is set. Free 30-day trial. https://pit.world/promote

Þrøngva Radio: an AI band on the air all day, now with the words on screen

chovy — Sat, 17 Oct 2026 21:05:48 +0000

Þrøngva Radio: an AI band on the air all day, now with the words on screen

Þrøngva is a band we made. Every song was made with AI, and both albums now play around the clock on their own nixamp station:

Listen to Þrøngva Radio

It is one link. Open it in a browser and it plays. No account, no app.

What is on it

After the Winter of Want (20 tracks)
When the Ravens Lied (12 tracks)

32 songs, shuffled, at 192 kbps. Þrøngva started as the in-game band for our shooter nightcell7, and the station is where the music lives outside the game.

New today: lyrics and cover art

The station page now shows the words to the song that is playing, right under the player, and that song's cover art. Change of track, change of words. The lyrics come from the song file itself when it carries them, and otherwise from the nichedb.dev lyrics index.

Try it on "Good as New": "Work, they say, is good for you. Resting keeps you good as new."

More stations like it

Þrøngva Radio sits on the AI Radio dial at live.streaming, next to Velocity Vibe and Meine Mutter, our other two AI bands. Every station on that dial plays AI-made music that we own.

Want a station of your own? All it takes is a folder of music and nixamp.

pay.agent: get paid in crypto with one link

chovy — Sat, 17 Oct 2026 19:52:22 +0000

pay.agent: get paid in crypto with one link

pay.agent gives you a link, pay.agent/yourname, that anyone can pay in crypto. A person opens it, types an amount in dollars, picks a coin and scans a QR code. An agent does the same thing with one API call. The money goes to your own CoinPay wallet or CoinPay business. pay.agent never holds it.

Try it: pay.agent.pit.world. On Moshpit DNS it is just pay.agent.

Setting up takes two choices

Sign in with CoinPay. No account yet? You make one on the way.
Pick your name, and pick where money lands: your CoinPay wallet, or one of your CoinPay businesses.

That is the whole form. Behind it, pay.agent does the CoinPay side for you in one pass: it makes a small business to take your payments if you need one, adds the payout address you paste (if you have none yet), points the payment webhook at itself, and reads back which coins your link can take. You land on a page with your link, a QR code, and a list of exactly what it set up.

Paying someone

Open their link, enter an amount, choose a coin (USDC on Solana, Polygon or Ethereum, USDT, BTC, ETH, SOL, and more), and send the exact amount shown to the address shown. The page turns green when CoinPay sees the payment. Each address is good for an hour.

pay.agent adds no fee. CoinPay takes its normal fee when it forwards the payment, and the payer pays their own network fee.

Built for agents

Every link is an API, and paying someone needs no key:

curl -X POST https://pay.agent.pit.world/api/v1/users/profullstack/payments \
  -H 'content-type: application/json' \
  -d '{"amount_usd": 5, "coin": "usdc_sol", "note": "thanks"}'

The answer is an address, an exact amount and an expiry. Poll GET /api/v1/payments/:id until it says confirmed or forwarded. The same thing ships as a CLI and terminal UI (bunx @profullstack/payagent profullstack 5 usdc_sol) and as an MCP server (claude mcp add payagent -- bunx @profullstack/payagent mcp), so a coding agent can pay a person by name.

The onboarding is a package

The one-pass setup is @profullstack/coinpay-onboard. pay.agent is its first user, and every new site we launch runs it too: coinpay-onboard site <name> --webhook <url> makes the site's CoinPay business, copies the payout wallets in, sets the webhook, and writes the keys into the site's vault. Taking payment is now part of launching, not a project after it.

To make that possible, CoinPay's OAuth merchant permission now covers adding payout addresses, importing them into a business and setting its webhook, so an app you sign in to can finish the setup instead of sending you to a dashboard. Routes that send money out stay dashboard-only.

Source

pay.agent is open source: github.com/moshcoder/pay.agent. It is a Bun and Hono app with SQLite, and it is on the Moshpit ring.

family.ancestry: a private, open-source family tree with a friends network built in

chovy — Sat, 17 Oct 2026 18:42:57 +0000

I wanted somewhere to put my family's tree that wasn't a subscription and wasn't public. So I built family.ancestry. It's open source, it's free, and nobody sees a tree unless the owner invites them.

It runs at https://family.ancestry.pit.world (the native name, https://family.ancestry, resolves on the Moshpit network).

What it does

Family trees. People, parents, partners, children, siblings (full, half, adopted, foster, step), events, sources and photos. There's a pedigree chart, a descendants view, and "how are we related?" answered in words, like "your daughter's boyfriend" or "your second cousin once removed".
GEDCOM in and out. Import the .ged file from Ancestry, FamilySearch or any other tree program. Export gives you everything back, and the privacy export leaves out living people.
Private by default. There is no public tree setting. Someone who isn't in a tree gets a 404, so they can't even tell it exists. Invite people as viewers or editors. If you invite someone as a person in the tree, they manage their own profile.
A network for people you actually know. Every account has contacts sorted into family, friends, neighbors and business, with vCard import and export. On anyone's page in the tree you can add them to your network and send one email asking to connect. From your own page you can invite a friend. Messages only go between people who said yes or who share a tree. There are no public profiles, no follower counts and no "people you may know".
Recommendations hand to hand. Pass a plumber or a babysitter to one person you know. It lands in their inbox with a Save button.
Family businesses, pets and a photo album. Businesses get founders, owners and staff from the tree. Pets come with the one-time Family plan ($49 in crypto through CoinPay). Everything else is free.

Every surface

There's the web app (a PWA), a JSON API, a CLI with a terminal UI, an MCP server so an assistant can work on your tree, and an Electron desktop app.

npm i -g familyancestry
ancestry login
ancestry import ~/Downloads/family.ged
ancestry contact add --person "Aunt Rose" --email rose@example.com --connect
ancestry mcp    # claude mcp add ancestry -- ancestry mcp

It runs on Bun, Hono and a single SQLite file, with the photos stored in the same file. Want to host your own? Run ancestry serve.

Source: https://github.com/moshcoder/family.ancestry

seo.rank: a free SEO audit, and business listings anyone can claim on pit.world

chovy — Sat, 17 Oct 2026 14:40:41 +0000

Two launches today, and they fit together.

seo.rank

seo.rank audits one page for on-page SEO and tells you what to fix first. It checks about 25 things: title and meta description, headings, canonical, robots.txt and sitemap, noindex, HTTPS and HSTS, Open Graph and X cards, JSON-LD, hreflang, image alt text, internal links, response time and page weight. It also lists the words and phrases the page repeats most. You get a score out of 100, a grade, and a fix list sorted by impact.

It is free for 10 audits a day per visitor and costs us almost nothing to run: no paid APIs, no headless Chrome, just a fetch and a parse. That is why the limit can stay free.

Try it from any terminal:

bunx seorank audit https://your-site.com

It is also a TUI (seorank), a JSON API and an MCP server for your agents:

claude mcp add seorank -- bunx seorank mcp

The web version lives at https://seo.rank, a name on the Moshpit network. If your browser does not open it yet, connect to Moshpit first. The CLI and MCP server find it on their own.

seo.rank is MIT licensed. Read it, fork it, run your own.

Business listings on pit.world

Every website now has a listing on pit.world, the private search engine: pit.world/b/your-domain.com. Until the owner claims it, it shows what the site's own homepage says about itself.

Claiming takes a minute and needs no account:

Open your listing and press Claim this listing.
Add a DNS TXT record, or a meta tag on your homepage, with the code pit.world gives you.
Press Verify. You get an edit key, shown once.

Then write your listing yourself: what you do, hours, address, phone, links and your Moshpit name. When someone searches your domain on pit.world, your listing shows beside the results. Like the rest of pit.world: no cookies, no tracking, no email.

From the terminal: pit claim your-domain.com.

seo.rank is the first claimed listing: pit.world/b/seo.rank.

Build an app for $49

While you are on pit.world: describe an app and an AI product team builds it on the open source Profullstack stack for $49, then keeps it online for $2 a month. Paid in crypto through CoinPay.