Content Restrictions - Revision history

KTL: /formatting/

2012-02-13T19:12:30Z

formatting

← Older revision		Revision as of 19:12, 13 February 2012
Line 18:		Line 18:
	===Default Contents===		===Default Contents===
	By default the file for 2.4 contains:		By default the file for 2.4 contains:
			allow *.bzflag.org

	allow *~~images~~.bzflag.org
	deny *		deny *

JeffM2501: /* Modification / remove deny if allowing

2012-02-13T19:02:07Z

Modification: remove deny if allowing *

← Older revision		Revision as of 19:02, 13 February 2012
Line 30:		Line 30:
	allow url.to.the.site.com		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		If the user would like to allow all sites they can simply add a wildcard instead of a site name and remove the '''deny''' section.

	allow *		allow *

JeffM2501: notes on default contents, and other ways to get all servers

2012-02-13T19:01:19Z

notes on default contents, and other ways to get all servers

← Older revision		Revision as of 19:01, 13 February 2012
Line 8:		Line 8:

	==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~~.		Content restrictions are controlled by the file '''DownloadAccess.txt'''. This file will be created the first time a client joins a server that has external images. If the file does not exist a user can simply create it.

	===Location===		===Location===
Line 15:		Line 15:
	* OS X: ~/Library/Application Support/BZFlag/DownloadAccess.txt		* OS X: ~/Library/Application Support/BZFlag/DownloadAccess.txt
	* Linux: ~/.bzf/DownloadAccess.txt		* Linux: ~/.bzf/DownloadAccess.txt

			===Default Contents===
			By default the file for 2.4 contains:


			allow *images.bzflag.org
			deny *

	===Modification===		===Modification===
	The file can be edited in a normal text editor, such as ''Notepad'' or ''TextEdit''.		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		If the user would like to add additional sites to the allowed list they can simply add a new line before the '''deny''' section as follows

	allow url.to.the.site.com		allow url.to.the.site.com
Line 26:		Line 33:

	allow *		allow *

			Another option to allow all servers is to delete the contents of the file and make it empty.

	===Parental Security===		===Parental Security===

JeffM2501 at 18:50, 13 February 2012

2012-02-13T18:50:16Z

← Older revision		Revision as of 18:50, 13 February 2012
Line 29:		Line 29:
	===Parental Security===		===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.		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.

			[[Category:Client]]

JeffM2501: /* Defaults */ link to the image submitter mainpage not the images directory

2012-02-13T18:46:20Z

Defaults: link to the image submitter mainpage not the images directory

← Older revision		Revision as of 18:46, 13 February 2012
Line 5:		Line 5:

	==Defaults==		==Defaults==
	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.		By default there is a single level of content restriction in place. Only images hosted on the [http://images.bzflag.org/submitimages/ 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==

JeffM2501: /* Defaults */ Cleanup URLS

2012-02-13T18:45:05Z

Defaults: Cleanup URLS

← Older revision		Revision as of 18:45, 13 February 2012
Line 5:		Line 5:

	==Defaults==		==Defaults==
	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.		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==

JeffM2501: extra [

2012-02-13T18:41:07Z

extra [

← Older revision		Revision as of 18:41, 13 February 2012
Line 5:		Line 5:

	==Defaults==		==Defaults==
	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.		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==

JeffM2501: actually use my edits that got blown out on a login

2012-02-13T18:40:40Z

actually use my edits that got blown out on a login

← Older revision		Revision as of 18:40, 13 February 2012
Line 1:		Line 1:
	~~There are limitations on the origin of images~~ that can be ~~displayed by a fresh installation of BZFlag. These can be configured by the user~~.		BZFlag offers a content restriction feature that can be used to limit what various clients will download.

	~~==Default Content Restrictions==~~		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.

	By default the game-client will only allow downloading images from the [http://images.bzflag.org official BZFlag image-server]. Those images all comply with a strict policy that can be found at the [http://images.bzflag.org/submitimages/tos.php BZFlag Image Uploader Terms Of Service].

	~~Map creators can upload image-files to this server through~~ the [http://images.bzflag.org~~/submitimages/~~ BZFlag ~~Image Uploader~~].		==Defaults==
	This ~~procedure~~ has a ~~few drawbacks however~~:		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.
	* Images need to get explicitly allowed by a moderator before they get in, this is a slow process. ~~This way it becomes impractical to have dynamic content~~.
	* Each image needs to have some license associated with it. ~~Map makers often just want~~ to ~~make a map without being bothered by~~ the ~~legal aspects of it~~.

	==Configuring Content Restrictions==		==Configuring Content Restrictions==
	~~Each BZFlag client-installation has a~~ file ~~called~~ DownloadAccess.txt ~~which controls what servers are allowed to serve images~~.		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 ~~of the DownloadAccess-file~~===		===Location===
	~~Depending~~ on ~~your platform~~ the ~~location differs~~:		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: ~~My Documents~~\My BZFlag ~~Files~~\DownloadAccess.txt
	* OS X: ~/Library/Application Support/BZFlag/DownloadAccess.txt		* OS X: ~/Library/Application Support/BZFlag/DownloadAccess.txt
	* Linux: ~/.bzf/DownloadAccess.txt		* Linux: ~/.bzf/DownloadAccess.txt

	===~~Modifying the DownloadAccess-file~~===		===Modification===
	~~A simple~~ text-editor can ~~be used~~ to ~~modify this file~~. ~~On windows~~ the ~~program "notepad" will do just fine~~.		The file can be edited in a normal text editor, such as ''Notepad'' or ''TextEdit''.
	If ~~you do not want any content-restrictions at~~ all ~~you~~ can ~~replace the whole content~~ of ~~the file with the line~~
	allow *		If the user would like to add additional sites to the allowed list they can simply add a new line as follows
	~~If you only want~~ to ~~allow~~ a ~~specific server then add '''on top of~~ the file''' the ~~line~~
	~~allow some~~.~~image~~.~~server~~		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.

JeffM2501: Cleanup page, talk about how to secure the file.

2012-02-13T18:39:53Z

Cleanup page, talk about how to secure the file.

← Older revision		Revision as of 18:39, 13 February 2012
Line 16:		Line 16:
	Depending on your platform the location differs:		Depending on your platform the location differs:

	* Windows: My Documents\My BZFlag Files\DownloadAccess.txt		* Windows: My Documents\My BZFlag Files\DownloadAccess.txt
	* OS X: ~/Library/Application Support/BZFlag/DownloadAccess.txt		* OS X: ~/Library/Application Support/BZFlag/DownloadAccess.txt
	* Linux: ~/.bzf/DownloadAccess.txt		* Linux: ~/.bzf/DownloadAccess.txt

	===Modifying the DownloadAccess-file===		===Modifying the DownloadAccess-file===

KTL: formatting

2012-02-13T18:19:09Z