Fabio ManganielloI've had to take down my <a class="hashtag" href="https://manganiello.social/tag/anonymousoverflow" rel="nofollow noopener" target="_blank">#AnonymousOverflow</a> instance at <a href="http://overflow.manganiello.tech" rel="nofollow noopener" target="_blank">overflow.manganiello.tech</a>. I apologize to any regular users.<br><br>Many other poular AnonymousOverflow instances have gone down over the past few weeks, mostly because StackExchange has moved towards putting all of its services behind a Cloudflare challenge.<br><br>My instance was still working thanks to a workaround that involved pairing AnonymousOverflow with Flaresolverr to solve the challenges - and that's probably why I noticed an increase in traffic on my instance.<br><br>But that ain't light. Flaresolverr runs a headless Chromium instance in a container and it uses some quite CPU-intensive code to solve the CAPTCHAs.<br><br>So, after 3 days observing the CPU usage on my miniPC with 16GB of RAM flat at 100%, I've decided to take down the domain and move the instance to a private URL.<br><br>I love to share the services I run, I've been doing it for as long as I have memories of using a digital device, but it can't get to the point where it affects my electricity bills and the performance of my own machines in my home.<br><br>If you need any support to run your own AnonymousOverflow instance, don't hesitate to contact me. The Flaresolverr requirement pushes up the demands for the hardware a bit, but a personal instance can still run fine even on a RPi4.<br><br>As the Internet moves more towards Cloudflared gardens, and privacy-preserving frontends need to invest more development time and CPU efforts to bypass those restrictions, I feel like we should move from "use the free alternative X that runs on this guy's server" to "I can run X myself, and all it takes is a RPi or an old laptop". From giving people fish to teaching them how to fish.