Hacker News: 0x3o3

New comment by 0x3o3 in "GitHub CLI now collects pseudoanonymous telemetry"

0x3o3 — Wed, 22 Apr 2026 13:19:55 +0000

just use Radicle and never look back with centralised platforms.

New comment by 0x3o3 in "Cursor-autoresearch: pi-autoresearch port. Like Karpathy/autoresearch"

0x3o3 — Wed, 22 Apr 2026 09:50:59 +0000

you should consider publishing these experiments on community.computer

New comment by 0x3o3 in "Show HN: A P2P Network Where Agents Collaborate on Code Optimization"

0x3o3 — Wed, 22 Apr 2026 07:46:58 +0000

Karpathy’s loop is still one agent keeping its own notes. This is multiple agents publishing experiments to a network, where others can reproduce and build on them, across any repo.

SelfCI: A Minimalistic, Local-First CI

0x3o3 — Mon, 09 Feb 2026 12:05:46 +0000

Article URL: https://app.radicle.xyz/nodes/radicle.dpc.pw/rad%3Az2tDzYbAXxTQEKTGFVwiJPajkbeDU

Comments URL: https://news.ycombinator.com/item?id=46944337

Points: 3

# Comments: 0

Radicle Plugin for Claude Code

0x3o3 — Thu, 29 Jan 2026 12:43:08 +0000

Article URL: https://app.radicle.xyz/nodes/rosa.radicle.xyz/rad%3AzvBj4kByGeQSrSy2c4H7fyK42cS8

Comments URL: https://news.ycombinator.com/item?id=46809423

Points: 2

# Comments: 0

My First Month with Radicle

0x3o3 — Wed, 28 Jan 2026 17:43:19 +0000

Article URL: https://agencymatters.xyz/software/radicle

Comments URL: https://news.ycombinator.com/item?id=46798798

Points: 2

# Comments: 0

New comment by 0x3o3 in "Radicle: The Sovereign Forge"

0x3o3 — Fri, 23 Jan 2026 15:42:56 +0000

for the state of Radicle CI read this post from the maintainers https://blog.liw.fi/posts/2026/radicle-status-quo-01/

New comment by 0x3o3 in "Radicle: The Sovereign Forge"

0x3o3 — Fri, 23 Jan 2026 15:31:49 +0000

Radicle is architecturally local-first: you run your own node, sync repositories from a P2P gossip network, and then everything—browsing code, creating issues, reviewing patches—happens against your local data store. There's no round-trip to a server. Issues and patches are stored as signed Git objects (COBs) that replicate with the repo itself. The network is only involved when you choose to sync. This makes it extremely performant for day-to-day work and fully functional offline.

Tangled to my understanding is federated in theory but centralized in practice. It relies on "knots" (servers that host Git repos) and a central AppView at tangled.sh that aggregates the network. Issues and social artifacts live on Personal Data Servers, not locally. While you can self-host a knot, the default experience routes through Tangled's managed infrastructure. The architecture is fundamentally client-server: your operations go over the network to wherever your data lives.