<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel>
        <title>https://coord.info/GC89ZW4</title>
        <description> Hi
Just spotted the above - I know that some would up vote this on the checker exception list - because &amp;#039;There are criteria that you need to fulfil&amp;#039; 
However can someone check this for me and see if it should even have been published 
It requires using cache names as the criteria which is against the ruling 10 
Source of criteria : NOT allowed : These cache page elements: cache titles, cache owner, GC Codes, publishing Reviewer, or cache page text.

Thanks

Tim</description>
        <link>https://project-gc.com/forum/read?12,30364,30364#msg-30364</link>
        <lastBuildDate>Mon, 24 Aug 2026 09:20:29 +0000</lastBuildDate>
        <generator>Phorum 5.2.23</generator>
        <item>
            <guid>https://project-gc.com/forum/read?12,30364,30415#msg-30415</guid>
            <title>Re: https://coord.info/GC89ZW4</title>
            <link>https://project-gc.com/forum/read?12,30364,30415#msg-30415</link>
            <description><![CDATA[ Please note - this cache was archived due to the fact that it didn&#039;t conform to the guidelines (original requirements were along the lines of &#039;find caches that began with the letters that spelled your caching name&#039; )<br />
However for some strange reason the cache was unarchived and allowed to have completely different challenge criteria  (changed to find 50 virtuals - which did conform) - the CO has now archived it completely <br />
So voting on this one is pointless as the original reason for submitting it to the exception list is now irrelevant]]></description>
            <dc:creator>Deepdiggingmole</dc:creator>
            <category>Challenge checker exceptions</category>
            <pubDate>Wed, 03 Jul 2019 17:40:08 +0000</pubDate>
        </item>
        <item>
            <guid>https://project-gc.com/forum/read?12,30364,30390#msg-30390</guid>
            <title>Re: https://coord.info/GC89ZW4</title>
            <link>https://project-gc.com/forum/read?12,30364,30390#msg-30390</link>
            <description><![CDATA[ Thank you<br />
I knew as much - just wanted confirmation]]></description>
            <dc:creator>Deepdiggingmole</dc:creator>
            <category>Challenge checker exceptions</category>
            <pubDate>Tue, 02 Jul 2019 09:16:24 +0000</pubDate>
        </item>
        <item>
            <guid>https://project-gc.com/forum/read?12,30364,30385#msg-30385</guid>
            <title>Re: https://coord.info/GC89ZW4</title>
            <link>https://project-gc.com/forum/read?12,30364,30385#msg-30385</link>
            <description><![CDATA[ The checker was cloned by the CO. And yes, challenges like that are against the guidelines.]]></description>
            <dc:creator>pieterix</dc:creator>
            <category>Challenge checker exceptions</category>
            <pubDate>Tue, 02 Jul 2019 06:47:22 +0000</pubDate>
        </item>
        <item>
            <guid>https://project-gc.com/forum/read?12,30364,30364#msg-30364</guid>
            <title>https://coord.info/GC89ZW4</title>
            <link>https://project-gc.com/forum/read?12,30364,30364#msg-30364</link>
            <description><![CDATA[ Hi<br />
Just spotted the above - I know that some would up vote this on the checker exception list - because &#039;There are criteria that you need to fulfil&#039; <br />
However can someone check this for me and see if it should even have been published <br />
It requires using cache names as the criteria which is against the ruling 10 <br />
Source of criteria : NOT allowed : These cache page elements: <b>cache titles</b>, cache owner, GC Codes, publishing Reviewer, or cache page text.<br />
<br />
Thanks<br />
<br />
Tim]]></description>
            <dc:creator>Deepdiggingmole</dc:creator>
            <category>Challenge checker exceptions</category>
            <pubDate>Mon, 01 Jul 2019 17:34:05 +0000</pubDate>
        </item>
    </channel>
</rss>
