thetruedoormat

You're confusing private and anonymous. Anonymous would be that no one knows you searched "cucumber." Private would be that someone could know that you did but it isn't shared with every single person for any reason. DuckDuckGo for instance is private in the sense that no one knows you searched what you searched, but Bing Ads knows the query to serve you a relevant ad. Signed-in to Google, Google would know your query and target an ad based on it, while adding it to a profile— in other words, it isn't private or anonymous. In a perfect world or using a search engine like searx, it's private in the sense that only the searx server knows what you searched and anonymous in the sense that Google wouldn't know who from that searx instance searched a query.

Author of the (terrible) article here. I woke up to messages from people in Farer saying "Congrats, you're on the front page of HN" which was an interesting way to start my day considering how I am not awake still. I wanted to thank everyone for the advice you've been putting out; all of us have been looking into basically all of it and seeing what we want to go moving forward based on it.

A few people have asked if documentation and an infra plan would ever be public. Right now, we're in such an early state of spinning around and seeing what works best not only for us, but for future us in 5-10yrs. Why should we waste time implementing service X if it's going to be a PITA to maintain; service Y is plenty decent and fits the same criteria? It's a matter of the seemingly easy decision between service X and Y. Sometimes we go with Y because that makes sense, other times we go with X because it (somehow) makes more sense.

All I can say is keep adding your two-cents! It's helping us think even more about what needs to be done, and we really appreciate all the help so far. I (never) check this website, but I'll keep looking here throughout the day to see if there's something more. My email (should) be at the bottom of that article as well if you want to make sure I see what you have to say. Cheers!

Author of that (terrible) article here. The blunt of this article written at (probably) 1 in the morning is something I think either I failed to mention or should have made more clear: for most of this, we just want to side-skirt the major outages of people like Cloudflare. For the few like myself, this is a breeding ground to experiment. Right now, I don't have the energy to convert services I maintain that are public to other platforms. It would mean significant downtime just to learn. However, Farer lets me play around and see what works, K8s/K3s being a prime example.

> making a mistake ... in banking on CoreDNS Well, I'll start by quoting the article: "Sanely hosting services 101 ... The first step is to not be us ... we created a lot of complexity that was generally [un]necesssary." You are 100% right in saying that BIND is more than likely a better solution than CoreDNS. And although some of it is "well, I found this that should work," it sometimes boils deeper, namely in the case of CoreDNS. It's something included in every pod of K3s and makes sense to get familiar with; which loops back to the start of wanting to learn how things work.

tl;dr : I appreciate the insights! Things are done for: a reason, for fun/experiment, or no reason. The Internet has some expected uptimes (not to say we don't for our intranet), but considering the small circle of trust, we aren't as constrained to the angry fist-waving when it goes down, rather we're all trying to figure out what happened, how to fix it, and how to prevent it from being an issue again: a fun "practicum," per se.

Hey, author of that (terrible) article here. The only "public" service I run is a Shynet instance for some friends. We're just a bunch of secondary or uni students wanting to still be able to do things we like if Cloudflare decides to turn turtle.