Farcaster

warpcast != farcaster

farcaster network activity dropped by 50% yesterday

probably because warpcast wasn't sending data to the protocol for a long time

if you care about decentralization, use alternative clients like @lolwildcard @yup @recaster-fc or yours truly, @supercast

web3 social all-in-one. 
crosspost to Farcaster, Twitter, Lens and Bluesky | yup.io | iOS: https://t.co/gJH0Bi07r4 | Android: https://bit.ly/3uaTz4T

https://supercast.xyz — have fun on farcaster

A Farcaster native client.
Available for iOS & Android.

Join /recaster to get more info!

Built by @haole · recaster.org

Wildcard is Farcaster gone WILD. /wildcardclub

Go wild: wildcard.lol

warpcast != farcaster

farcaster network activity dropped by 50% yesterday

probably because warpcast wasn't sending data to the protocol for a long time

if you care about decentralization, use alternative clients like @lolwildcard @yup @recaster-fc or yours truly, @super

If someone was casting via Supercast during the sync issue, their casts would not appear on Warpcast, correct?

Interesting, I did not know this. I thought it applied to both read and write. I'm guessing that what happened yesterday is related to the same sync issue we've been discussing recently. If I unfollowed someone on Warpcast yesterday, that action would not have been registered by the hubs?

surprisingly, these issues are usually one-directional, and this one was too

supercast-created content appeared in warpcast normally