0 reply
0 recast
0 reaction
25 replies
1 recast
170 reactions
3 replies
0 recast
5 reactions
1 reply
0 recast
1 reaction
1 reply
0 recast
2 reactions
4 replies
0 recast
2 reactions
2 replies
0 recast
1 reaction
Both /automod and /glass are farcaster-native and have a hard dependency on Merkle and the network growing.
It's both risk & opportunity. On one hand, things might change to make your app obsolete, on the other a) its early so there's less competition, and b) Merkle is actually well intentioned, well staffed and funded so having them on your side I view as a major advantage.
As far as Farcaster apps go, yeah, builders should be careful. For ex: don't be long on a use case that a reasonable user would demand Warpcast to implement or could create revenue (payments, decent search). If you are that should just be an acquisition strategy.
And it's not wise to have a high burn rate or time preference since its unlikely you can do anything meaningful to move dau. So, my approach is to stay lean and frugal, build cash netural+ businesses that could live for years at current dau. If Farcaster grows, great, well positioned. If not, bummer, at least it was fun. 2 replies
0 recast
1 reaction
1 reply
0 recast
1 reaction
1 reply
0 recast
0 reaction