HAM 🍖

building /automod, /glass • prev manifold.xyz, twilio.com

9. Using @neynar managed signers to like casts from different automod accounts.

Reactions are limited per storage unit of each account, this was required to make sure some very high volume channels didn't wipe out reactions for others.

1. Approving signer access for the account [some awkwardness req'd due to how the lib initializes as soon as it mounts]: https://github.com/jtgi/automod/blob/main/app/routes/signer.tsx
2. Storing the signer uuid: https://github.com/jtgi/automod/blob/main/app/routes/api.signer.tsx
3. Using to like a cast: https://github.com/jtgi/automod/blob/main/app/lib/validations.server.ts#L1496-L1509

Fun side story on why there's 10 different @automod accounts.

When moderation switched to require likes on protocol it created a problem: you only get 2,500 likes per storage unit, after that its fair game for hubs to prune old reactions.

Well, some channels like /lp are very high volume. They could do 30k casts in a single day which means others channel's likes would be dropped and no longer shown in Main.

Thing is, even though @dwr.eth and @v alluded something like this might be necessary, I didn't fully process what they meant until about 8h before channels pivoted over.

So I went with this: take all the high volume channels, about 5 or so, and dedicate separate accounts like @automod-ringo, @automod-davinci for them. That gives them 2,500 casts worth on their feed each, more than anyone would page through. Then take all the free accounts, beef up the storage and put them on the shared account @automod (its now got capacity for 500k likes, s/o caststorage . com).

cont'd

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

automod.sh — power tools for your channel. Setup in < 2min.

This way, all channels can still have their reactions shown on Main while ensuring high volume channels don't dominate. It's a bit of a unique solution, but it seems to be working well so far