Content pfp
Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions

Andrei O. pfp
Andrei O.
@andrei0x309
Opening an open-source client UI in itself as a mini-app works to do infinite nesting until the UI is not usable or you run out of memory.
2 replies
2 recasts
22 reactions

christopher pfp
christopher
@christopher
Whoa fosscaster looks identical to Warpcast that’s crazy
1 reply
1 recast
3 reactions

Andrei O. pfp
Andrei O.
@andrei0x309
It's just a UI with a proxy that uses the Warpcast backend. Probably very hard to implement all 500+ endpoints; it just implements the basics. Only has 192 files; the main scope was to push for a web wallet with it, and it worked pretty much. The main difference is that this is meant to work with an external wallet exclusively, for everything, including signup. Signups were possible with any wallet for years, but warpcast pushed for the setup with creating a wallet, requesting email, requesting a pic, etc, this UI bypasses all of that. It would have been better if CORS were enabled on api.warpcast.com so I could get rid of the proxy. Generally, nothing to gain; only Warpcast has to gain from an alternative UI, just maybe a bit of distribution if you hardcode some static stuff, but other than that, you're limited to the Warpcast backend, and all users are Warpcast users. Already hit by 1.53k unique IPs, you can get a few users, because it is made to be viewed unauthenticated, which is great for SEO.
1 reply
2 recasts
3 reactions

Darryl Yeo 🛠️ pfp
Darryl Yeo 🛠️
@darrylyeo
Did you reverse-engineer all the endpoints yourself? Super impressive!
1 reply
0 recast
2 reactions

Andrei O. pfp
Andrei O.
@andrei0x309
Not all of them, at the moment fosscaster only uses 35 endpoints. The most essential ones, anyone could use the class with those 35 endpoints here is public ( https://github.com/andrei0x309/fosscaster.xyz/blob/main/app/lib/wc-mod.ts ) Warpacat uses 500+ endpoints as of today, as you imagine, many of them are not super important. Also, when they enabled the wallet, they leaked the code(using source maps) from their global API hooks, because the embed wallet is in an iframe, and it loads all endpoints again. So the web version loads all endpoints twice, but not all endpoints are used, because for simplicity, from the code leaked, it seems queries are in a package( probably for easy reuse) But it is simpler to remake from scratch, don't need the code just the browser is enough, the fosscaster repo duplicates a lot of types because I just use a tool to export all types to be easier, but that doesn't matter much all types are striped when vite does the transforms.
0 reply
1 recast
2 reactions