Content
@
https://warpcast.com/~/channel/modbot
0 reply
0 recast
0 reaction
Haole
@haole
Sharing some thoughts on why I'm working on ModBot, a forked version of @automod. Mainly two reasons: - Learn Remix: I'm tired of Next.js, and @jtgi shared some Remix experience with me before he open-sourced Automod. Then Automod becomes a great opportunity for me to dive into Remix. - Convert Recaster into a channel-focused or OnlyFans-like client: it needs gated channels, casts, lists, and bookmark folders, all require a rule engine. ModBot is the perfect match for this. As Channel V2 is coming, Farcaster community has already built many channel tools. You can try them all and choose the one that suits you best. I'll keep ModBot free for as long as possible. If I start charging, it's because the costs have become too high. You can always deploy your own version or switch to other tools, ModBot should never become a single point of failure.
9 replies
8 recasts
28 reactions
Andrei O.
@andrei0x309
Remix will not live for long though, it will be merged with react router at version 7 in a few months, you'll be mostly able to keep all the code with minor differences with RR7. Also remix is a good choice if you're forced to use react, because it has SPA only mode. Still svelte kit works much better for client/code separation and the router in SvelteKit is much more advanced than in Remix, for advanced cases you basically need to make your own router with RR. And if it's SPA, router is 90/100 of the underlaying code of the framework.
2 replies
0 recast
0 reaction
Haole
@haole
Thanks for sharing this. Good to know.. Have you tried tanstack router? It mixed the Next and Remix, and I love react query, it should be next try..
1 reply
0 recast
1 reaction
Andrei O.
@andrei0x309
I haven't tried it yet, had another project that used the query dep, but that is very common. I did write my own routers because they were optimized for SPA like browser extensions or apps not meant to be indexed. Generally, the strategy for a SPA router is similar to what Ionic does meaning you don't remove routes from the DOM, but you hide them, that way you consume a bit more memory but you can increase performance as long as you keep the DOM under 3-5k nodes. This strategy is very good for mobile, extensions, and apps(electron Tauri, etc), but is bad for SEO as it might confuse some bots.
0 reply
0 recast
0 reaction
