90% of people aren’t worth the time

  • 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: November 7th, 2024

help-circle





  • This is one of those things that if you really want to do it, you’ll have to live with the consequences.

    I’m an American that VPNs everything first to my VPS then down a double hop commercial VPN tunnel that finally exits in Switzerland. DNS traffic also travels over that VPN tunnel so you’ll rightly guess that my DNS is rather slow too.

    What I do is I run a resolver on the VPS (physically near me) that aggressively prefetches commonly queried DNS records. After years of using Unbound I found Blocky to be much, much faster (especially with huge blocklists). It’s to the point now where sure, it’s slower than a “normal” internet connection but it doesn’t feel slow to me anymore.






  • It’s mostly about performance. Caddy’s Go-based garbage collector starts to negatively impact performance at high load. It looks something like:

    server {
        listen 443 ssl http2;
        server_name example.com;
    
        ssl_certificate     /etc/nginx/ssl/fullchain.pem;
        ssl_certificate_key /etc/nginx/ssl/privkey.pem;
    
        location / {
            proxy_pass http://localhost:3000/;
    
            proxy_set_header Host $host;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
        }
    }
    


  • This sounds like a fun problem to solve as a developer. A web application could be written that:

    1. Takes incoming requests from the UI (presumably SearXNG-like in appearance)
    2. Hits multiple instances at once
    3. Proxies the results from the fastest successful instance

    If SearXNG offers an API you could even ditch the proxying of results. If you got really fancy you could store stats on which are the fastest/slowest and act on that in the future.