Content
@
0 reply
0 recast
0 reaction
jtgi
@jtgi
PSA: over the past 72h, casts have been taking longer than normal to propagate across Farcaster. Normally automod processes casts in seconds, but as a result, some casts are taking minutes or even hours. “But I can see the cast on Warpcast, why can’t automod?” If a cast is created on Warpcast anyone using Warpcast can see it immediately, it doesn’t need to wait for the cast to sync across the protocol. But other clients, and apps built on infrastructure providers like Neynar won’t know about the cast until it does. Automod included. “Will automod eventually process the cast?” Yes. No action required. “When will this return to normal?” No ETA. Infra teams and Warpcast/Merkle are working on finding a root cause. “So nobody can see my cast until automod likes it?” Not exactly. Assuming you’re not narrowcasting, your followers on Warpcast will see your cast. Most channel casts are viewed this way. It just won’t be in the Main channel feed until it’s liked by automod.
7 replies
11 recasts
70 reactions
jtgi
@jtgi
“How can I check if a cast has propagated?” In automod you can check the Activity log. If you want protocol specifics check out this explorer from @kevinoconnell explorer.neynar.com. I’ll build simpler ways in automod to see this happening as well. “Where can I learn more about network propagation?” See this paragraph article from Neynar for an overview: https://blog.neynar.com/understanding-message-propagation-on-farcaster-mainnet “Are others impacted by this?” Yes. Any infra and apps building on Farcaster.
0 reply
0 recast
1 reaction
