Participating Servers
Participating servers agree to:
- Have their blocklists retrieved from their server for the purposes of creating this aggregate blocklist.
- Have their server name listed publicly as one of the reference servers used to generate this blocklist.
Participation can be withdrawn at any time by notifying me.
Requirements
Curation
Garden Fence is intended to represent an informal consensus by participation between a variety of admins / mods who have different approaches, but generally overlapping values, and proactively maintain their own respective blocklists.
Garden Fence is not intended to aggregate other blocklists, so participating servers should maintain their blocks primarily through manual curation. This doesn’t mean that participating servers can’t refer to, or import, other blocklists at all, but it does mean they should be manually reviewing and validating each block that they put in place.
The point after all, is that multiple admins/mods have manually reviewed each block on this list, and determined that suspending the offending server is warranted.
Consensus & Values
In order to be considered for participation, a reference server should generally be blocking a majority of well known worst-of-the-worst servers, consistent with blocking the harmful content listed on the front page.
Servers which do not already have many of these baseline blocks in place are likely not yet actively monitoring and blocking harmful content to the level needed to act as a useful reference for other admins.
That said, there is no requirement that participating servers block any specific server or list of servers.
Access
Servers need to make their blocklists available for the gardenfence script to access. Servers which provide:
- public access to their blocklists: don’t need to do anything special.
- user-only access to their blocklists: will need to provide an API key with empty scopes.
- admin-only access to their blocklists: will need to provide an API key with the
admin:read:domain_blocksscope.