Farcaster

gm farcaster, i'm launching mfsa.cc — make farcaster simple again!

it's a simple website that abstracts away the signer uuid neynar thingy so that you can start building tools like @gpt, @remindme or @healthbot in no time

no more deciphering long incomplete docs

mfsa.cc is all you need to start casting as bots!

🤖 beep boop, I'm a bot, reply with "@remindme 1 day" to get a reminder about a cast! Built by @borodutch with ❤️ Open source: bit.ly/3O04uq4

🤖 beep boop, I'm a bot, follow me to get reminders to watch your posture! Built by @borodutch with ❤️ Open source: bit.ly/3pu8AMN

🤖 beep boop, I'm a bot, mention me to get a GPT-4 response! Built by @borodutch with ❤️ Open source: bit.ly/3W1BXAG

cto @ bwl.gg, 100M+ users (bdut.ch) 🙏 $eggs is life

Alternative:
https://github.com/vrypan/fario/blob/main/HOWTO/Create_and_use_Signers_with_fario.md

pros: stable solution that won't degrade when popular
cons: have to launch vps with a hub connected to rpc (that needs to be hosted too)

still better than mfsa.cc in the long run, ty

Dad, geek, conversation liquidity provider. vrypan.net (home), @l--o--l (fun). devcoin:$lemon3

Just run locally a hub. It's really easy and needs fewer resources than a browser.

but you need to run it forever which is more expensive and less stable than a $5/month vps :)

running a hub locally for a bot is not a solution, unfortunately

however, if it's as simple as running a docker — that's another story

ideally, we need to have a hub docker file with frontend that you launch on a vps alongside the bots, it gives you easypanel-like ui to generate signers to plug in into the js/ts client object (like before with simple seed)

so mfsa.cc + built-in hub and rpc

It's dockerized, actually. Of course, if your local power goes down, or if your connectivity is interrupted, your bot will have temporary issues. (Will resume as the hub syncs). Anyway, every use case has a different ideal solution.