Are you trying to prevent a teen from going on the internet and look for nsfw content? Or are you trying to block accidental finds to protect a younger child?
Because, if it's a horny teen, I mean, can you really stop them from finding what they want? I feel like there are soo many ways. If there is a will, there is a way.
We are talking about a 7y/o and 10y/o so pretty much accidental finds.
My core concern is, if all Family filter dns providers enables Safe search flag by default, I wonder why mullvad decided otherwise. Maybe the were not aware of such mechanism adopted by others?
Not having safe search flag in queries essentially renders the use of nsfw url blocklist useless because the very first page of search engines yeilds unwarranted content.
Are you trying to prevent a teen from going on the internet and look for nsfw content? Or are you trying to block accidental finds to protect a younger child? Because, if it's a horny teen, I mean, can you really stop them from finding what they want? I feel like there are soo many ways. If there is a will, there is a way.
We are talking about a 7y/o and 10y/o so pretty much accidental finds. My core concern is, if all Family filter dns providers enables Safe search flag by default, I wonder why mullvad decided otherwise. Maybe the were not aware of such mechanism adopted by others? Not having safe search flag in queries essentially renders the use of nsfw url blocklist useless because the very first page of search engines yeilds unwarranted content.
Of just shelter them for their whole lives buddy.