Articles‎ > ‎Homemade Software‎ > ‎

Force Your Teen To Communicate


I am the internet gatekeeper!

Problem: My teenager doesn't communicate as much as I would like
Situation: I control Internet access and my teen likes to use the Internet
Solution: Internet access is prohibited unless I get regular written communication


Sad Face
Warning: Restricting internet access may not make you popular


Here's how I did it:
  • My router is set up to deny or allow Internet access based on the number of written words that have been submitted
  • When the number of written words drops below 100, Internet access attempts always show my Wordeater (my own name, not related to any other stuff that might already use the name) page
  • When the number of written words exceeds 100, Internet access is allowed

The effect of this is that my teenager now has incentive to write me regular communication. The more I get, the more Internet access is allowed. If too much time passes between messages, then there is incentive to write again. It helps me feel like I'm staying in touch a little better and it gives my teen some freedom to enable Internet access when desired.

I've provided attached examples of the files that I'm using to set up this system. The files are text files, suitable for examples, but obviously modified so that our own real email addresses are not used.

Some basic setup is required in order to make this sort of thing possible, beyond just the files that the examples illustrate.

My home network gets Internet access from my router, which is a PC I've customized to do the job. It is running CentoOS, a version of Linux I favor for systems I don't want to change very often. CentOS works nicely with the webserver apache and iptables, which are needed for this to work.

I have set up apache to work with PHP and set aside the directories /var/www/wordeater and /var/www/wordeater.results for it to use. Apache has a customized configuration file I store in /etc/httpd/conf.d called wordeater.conf which sets it to listen on port 8080 and to direct all access attempts to the file at /var/www/wordeater/index.php. Apache has the rights to read and write to the directory /var/www/wordeater.results so that it can store information.

I use a script I store at /root/bin/wordeater.process.bash to remove one word each time it is run and count the number of words that are stored as submissions at /var/www/wordeater.results. When it has enough words, it enables normal Internet access and when the number of words drops too low, it stops and redirects Internet access attempts using another script I store at /root/bin/router.wordsinsufficient. It updates a status note to indicate the state of blocking, including blocking it does for bedtime hours.

The script at /root/bin/router.wordsinsufficient requires a start or stop argument and it checks to see if internet access is blocked or enabled, then makes the changes to the firewall as indicated by the argument. It uses iptables and based on the start and stop argument will redirect Internet access attempts to apache on port 8080 when it is being blocked.

I have a scheduled task that runs /root/bin/wordeater.process.bash once every ten minutes, effectively meaning that six words are eaten each hour, or 144 words per day. It also checks the time and updates a status message indicating why Internet access is enabled or disabled, how many words are in the bank and whether internet access has been disabled for bedtime hours.

My page uses some images I've grabbed from the web that make sense to me as embodying "Not Hungry", "Sorta Hungry" and "Very Hungry" to give a nice visual to the current word count status. I am not including them because I don't want to worry about potentially infringing on anyone's copyrights.


Disclaimer:
The software, examples and descriptions are free to use to the best of my knowledge, but that doesn't mean you really can or should. Any attempt to use any of these examples is done at your own risk and you accept that risk as being yours alone if you should try. As much as I try to make my examples safe to use, they might still cause serious problems and you acknowledge and accept all such risk with no expectation that I'll fix anything if something goes wrong, no matter how horribly. If it turns out that you didn't have the right to do it, or I didn't have the rights to offer it or something else goes wrong, you acknowledge that is your problem and not mine and agree not to hold me responsible.

ċ
index.php.txt
(6k)
Boyce Crownover,
Mar 7, 2012, 7:02 PM
ċ
router.wordsinsufficient.txt
(5k)
Boyce Crownover,
Mar 7, 2012, 6:58 PM
ċ
wordeater.conf.txt
(0k)
Boyce Crownover,
Mar 7, 2012, 6:57 PM
ċ
wordeater.process.bash.txt
(4k)
Boyce Crownover,
Mar 7, 2012, 6:58 PM
Comments