re: How do you practice safe public wifi access? VIEW POST

re: @jason No one forced you to follow up with this solution. There are people who actually know what they are talking about and also people who rant ...

You're not in the first group apparently.

Gosh, wish I'd known that before I'd gone and run a secure, production-grade development server for six years. I'll be sure to tell those two IT friends of mine they aren't knowing professionals either. They've wasted years of their lives successfully doing a job they apparently can't do.

Deserved sarcasm aside, I merely said that it wasn't a "fix-all". It's a valid solution, but not the only solution, and not necessarily one that magically works in every imaginable scenario. (P.S. My experience with dnsmasq was from about two years ago, not today.)

"RTFM" is never an appropriate response to anyone. My anger is directed at that, and rightly so. There are many people here on DEV who would be crushed by that remark, with its deliberately hateful insinuation of stupidity. "I read the documentation, but I didn't get it. I must not be legitimate." An insinuation you just helped add fuel to.

I came here to say that maybe the topic of setting up your own "central" server could be a good dev.to article!

I did write a handful of articles on dnsmasq, for ad-blocking, conditional DNS request proxying, and such.

Indeed you have! Thanks for pointing that out, I'll bookmark them. :)

If you find anything ambiguous or have any questions, don't hesitate to ask on associated articles.

I don't see those as automatic reasons to avoid it

pokes oar in

Not specifically against Cloudflare, but personally I don't like encouraging anyone to go with the centralised solution. As long as everyone does it because "that company's alright", people will keep seeing it as safe. I see it as comparable to the "why would I use free software when I can pay for something good?" point of view.

code of conduct - report abuse