This wiki is archived and useful information is being migrated to the main bzflag.org website
Difference between revisions of "Content Restrictions"
(Cleanup page, talk about how to secure the file.) |
(actually use my edits that got blown out on a login) |
||
| Line 1: | Line 1: | ||
| − | + | BZFlag offers a content restriction feature that can be used to limit what various clients will download. | |
| − | + | The primary use of these restrictions is to limit the downloads of images so that parents can prevent inappropriate images being shown to their children. | |
| − | |||
| − | + | ==Defaults== | |
| − | This | + | By default there is a single level of content restriction in place. Only images hosted on the [[http://images.bzflag.org|BZFlag image submission system] will be allowed. This system has a 'family friendly' [http://images.bzflag.org/submitimages/tos.php|content policy] and all images are reviewed manually by project staff to ensure that they follow the policy and are properly licensed. |
| − | + | ||
| − | + | ||
==Configuring Content Restrictions== | ==Configuring Content Restrictions== | ||
| − | + | Content restrictions are controlled by the file '''DownloadAccess.txt'''. This file may not be created by default and if it does not exist the user should simply create a file with the correct name. | |
| − | ===Location | + | ===Location=== |
| − | + | The location of the file depends on the operating system that the client is installed on: | |
| − | + | * Windows: OSDRIVE:\Users\USERNAME\AppData\Local\BZFlag\2.4\DownloadAccess.txt | |
| − | * Windows: | + | |
* OS X: ~/Library/Application Support/BZFlag/DownloadAccess.txt | * OS X: ~/Library/Application Support/BZFlag/DownloadAccess.txt | ||
* Linux: ~/.bzf/DownloadAccess.txt | * Linux: ~/.bzf/DownloadAccess.txt | ||
| − | === | + | ===Modification=== |
| − | + | The file can be edited in a normal text editor, such as ''Notepad'' or ''TextEdit''. | |
| − | If | + | |
| − | + | If the user would like to add additional sites to the allowed list they can simply add a new line as follows | |
| − | + | ||
| − | + | allow url.to.the.site.com | |
| + | |||
| + | If the user would like to allow all sites they can simply add a wildcard instead of a site name | ||
| + | |||
| + | allow * | ||
| + | |||
| + | ===Parental Security=== | ||
| + | Parents may wish to secure the file from editing in order to prevent a child from circumventing any restrictions. Securing the file involves setting the child's user account in such a way that it does not have permission to edit the file. This method varies by OS and can be found using simple internet searches. | ||
Revision as of 18:40, 13 February 2012
BZFlag offers a content restriction feature that can be used to limit what various clients will download.
The primary use of these restrictions is to limit the downloads of images so that parents can prevent inappropriate images being shown to their children.
Contents
Defaults
By default there is a single level of content restriction in place. Only images hosted on the [image submission system will be allowed. This system has a 'family friendly' policy and all images are reviewed manually by project staff to ensure that they follow the policy and are properly licensed.
Configuring Content Restrictions
Content restrictions are controlled by the file DownloadAccess.txt. This file may not be created by default and if it does not exist the user should simply create a file with the correct name.
Location
The location of the file depends on the operating system that the client is installed on:
- Windows: OSDRIVE:\Users\USERNAME\AppData\Local\BZFlag\2.4\DownloadAccess.txt
- OS X: ~/Library/Application Support/BZFlag/DownloadAccess.txt
- Linux: ~/.bzf/DownloadAccess.txt
Modification
The file can be edited in a normal text editor, such as Notepad or TextEdit.
If the user would like to add additional sites to the allowed list they can simply add a new line as follows
allow url.to.the.site.com
If the user would like to allow all sites they can simply add a wildcard instead of a site name
allow *
Parental Security
Parents may wish to secure the file from editing in order to prevent a child from circumventing any restrictions. Securing the file involves setting the child's user account in such a way that it does not have permission to edit the file. This method varies by OS and can be found using simple internet searches.
