bmadhu

5 ms·

1.
by bmadhu 14y ago
When it comes to websites that require content inspection, we resolve the DNS requests to a web proxy which does the content filtering. To get around the issue of the average consumer not being able to change their DNS settings, we are work
2.
by bmadhu 14y ago
Correct. But only for the sites that are known to have content that might be age inappropriate.
3.
by bmadhu 14y ago
Our key differentiators are (1) Being able to filter inappropriate content on trusted websites (Google, YouTube, Wikipedia, etc) that children use frequently. Domain based blocking allows or denies the entire website. But cannot for example
4.
by bmadhu 14y ago
Your feedback is well taken. A couple of things (1) Based on our experience, we ran into a lot of empirical evidence that parents don't take the lead in talking to their kids about what they might run into on the Internet (2) The pro-choice
5.
by bmadhu 14y ago
Thanks for the feedback. We are in the process of revamping our website to include FAQ -- but we felt like we could get away with launching on HN without it given the high density of early adopters here.
6.
by bmadhu 14y ago
Thanks for all the support, Bill! Really appreciate it.
7.
by bmadhu 14y ago
Thanks Cliff. Yes, SafeEyes (we are ex McAfee as well) and similar software based solutions are painful to manage across devices. We are already working towards addressing the DNS setting issue by not only providing instructions on our site
8.
by bmadhu 14y ago
Thanks for the feedback. We intend to revamp our site to show each use-case in the front page itself.
9.
Show HN: Securly - Keep your kids safe on your home network
17 points by bmadhu 14y ago|22 comments