dOCKER

Trying to convince for more credits.

Inspiration

nextDNs

What it does

It's a DNS server implemeting DNS-over-TLS, DNS-over-HTTPS, typical port 53 DNS running via a zig-server.

You set a limit and there are three modes:

Shared You share a set limit of requests to social media per day, with a friend. e.g. 3,000 If you use all your requests in the morning, you have to deal with your friend who now cannot use social media all day.
Set with borrow. You and your friend have, e.g. 3,000 each, both have their own limits. But if you run out you can "request" more limit from your friend. beg to them, good luck.
Bargain with the AI Set limit for the day, but you can try and convince google gemini to give you more credit, it does not give up lightly. ## How we built it DNs server written in zig, tls breaking via a go-proxy that forwards it. Uses nginx for streaming and https etc. nextjs for web app golang for backend api server on digital ocean cloudflare kv as a database.

Challenges we ran into

ZIG DOES NOT HAVE A NATIVE TLS LIBRARY I SPENT 7 HOURS TRYING TO WRITE WHAT WOULD HAVE TAKEN ME 5 MINUTES AND 20 LINES IN GOLANG. I HAD TO DO IT ANYWAY