0 reply
0 recast
0 reaction
3 replies
2 recasts
16 reactions
1 reply
0 recast
1 reaction
No backend, uses warpcast api.warpcast.com ( that was supposed to be public per docs)
Is using Netlify proxy to bypass CORS, imo since rate limits are per users, CORS should be enabled for projects like this to work without a proxy.
Without a proxy, it can scale indefinitely since 100/100 of the code is client-side, and all users are tethered to warpcast, so basically is just a UI.
If the warpcast API dies, this UI dies.
But still, such UI is large. The amount of code to implement for most of the APIs is significant; a project like this has a lot of frontend code.
Main idea is that this UI offers some features that are possible with Warpcast backend, but Warpcast doesn't offer them like, sign-up/login with a wallet directly.
Most of the code was written in 2 batches of 2 weeks. Giving a month or so, I can add most of what Warpcast provides.
Don't need any access to source code or anything because you can just write your own FE implementation out of endpoints.
cc: @deodad 2 replies
0 recast
2 reactions
