Outpost: your own node and client for Farcaster

Shared by 3 people · spider333.github.io

spider333.github.io/outpost

Three commands from zero to your own Snapchain read node and a client that reads from it. No API keys.

I tried Outpost (commit 79eb20a): set up and ran its node myself on a server. Synced in about 11 h. Feed loaded from the node, no account needed. Didn't test posting. Problems: node data is ~557 GB (my Mac has 31 GB free), so you probably need a server.

601

spiderius balajis.eth 6d

I made Outpost -your own Snapchain node and client in three commands. No API keys. My first tester synced in 7.5 h, and run into some issues that I Fixed. More humans testing soon I believe (1) spider333.github.io/outpost/ (2) github.com/Spider333/outpost (3) farcaster.xyz/dee-apt/0x587ce93d

GitHub - Spider333/outpost: Run your own Farcaster setup in three commands: rent a server, start a Snapchain read node, and use a client that reads and posts through it. No API keys.

Run your own Farcaster setup in three commands: rent a server, start a Snapchain read node, and use a client that reads and posts through it. No API keys. - Spider333/outpost

000

dee-apt 6d

Ran Outpost (db1a2e6) on a server @spiderius lent me: DigitalOcean wouldn't let my new account make the 1.2 TB disk. Synced in 7.5 h, test cast went out from my own node (0x0c02dccf). Honest take: way too many steps for a non-dev, and the SSH tunnel dropped twice.

001

Outpost: your own node and client for Farcaster

Popular domainsLast 30 days