←back to thread

WikiTok

(wikitok.vercel.app)
1459 points Group_B | 1 comments | | HN request time: 0s | source
Show context
aizk ◴[] No.42936923[source]
Hi! I'm the dev here! I built this on a whim at after seeing someone ask for it on twitter. It was 12:30 at night but I couldn't pass down the opportunity to build it.

The code is very simple, there's no backend at all actually, I believe because wikipedia's api is very permissive and you can just make the requests in the frontend. So you just simply request random articles, get some snippets, and the image attached!

I used Claude and cursor do 90% of the heavy lifting, so I am positive there's plenty of room for optimizations. But right now as it stands, it's quite fun to play with, even without anything very sophisticated.

Here is the source code. https://github.com/IsaacGemal/wikitok

replies(18): >>42936962 #>>42936974 #>>42937696 #>>42937871 #>>42937989 #>>42938002 #>>42938007 #>>42938164 #>>42938260 #>>42938330 #>>42939286 #>>42939520 #>>42940031 #>>42940626 #>>42942340 #>>42944933 #>>42945717 #>>42947803 #
tomashubelbauer ◴[] No.42938330[source]
Shoutout to APIs that do not enforce CORS preventing requests be made from FE without a need for a BE. There's so many toy apps I started building that would have just worked if this was more common, but they have CORS restrictions requiring me to spin up a BE which for many one-off tools and personal tools just isn't worth doing and maintaining. Same with OAuth.
replies(9): >>42938463 #>>42938484 #>>42938836 #>>42939162 #>>42939366 #>>42939679 #>>42939693 #>>42939990 #>>42944599 #
anon3459 ◴[] No.42944599[source]
Using nextjs with a serverless function acting as a proxy is pretty simple
replies(1): >>42945530 #
1. Liquidor ◴[] No.42945530{3}[source]
Don't you mean Node.js ? I don't see why you would use a full Next.js framework for just a reverse proxy.