{"action":"created","issue":{"url":"https://api.github.com/repos/ctftime/ctftime.org/issues/9","labels_url":"https://api.github.com/repos/ctftime/ctftime.org/issues/9/labels{/name}","comments_url":"https://api.github.com/repos/ctftime/ctftime.org/issues/9/comments","events_url":"https://api.github.com/repos/ctftime/ctftime.org/issues/9/events","html_url":"https://github.com/ctftime/ctftime.org/issues/9","id":55383133,"number":9,"title":"CTF announcment time vs rating","user":{"login":"gynvael","id":1008844,"avatar_url":"https://avatars.githubusercontent.com/u/1008844?v=3","gravatar_id":"","url":"https://api.github.com/users/gynvael","html_url":"https://github.com/gynvael","followers_url":"https://api.github.com/users/gynvael/followers","following_url":"https://api.github.com/users/gynvael/following{/other_user}","gists_url":"https://api.github.com/users/gynvael/gists{/gist_id}","starred_url":"https://api.github.com/users/gynvael/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gynvael/subscriptions","organizations_url":"https://api.github.com/users/gynvael/orgs","repos_url":"https://api.github.com/users/gynvael/repos","events_url":"https://api.github.com/users/gynvael/events{/privacy}","received_events_url":"https://api.github.com/users/gynvael/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-01-24T20:07:34Z","updated_at":"2015-01-24T21:16:02Z","closed_at":null,"body":"I may sound like a broken record (since I've already suggested this last year), but I would like again to discuss the issue of late CTF announcements.\r\n\r\nIdeally, a ranked CTF should be announced in a time that gives teams time to allocate time/resources for it. Personally I think 2 weeks is OKish for that purpose, 4 weeks even better.\r\n\r\nIf a CTF is announced later than 2 weeks before, it should have rank 0 (i.e. not be ranked).\r\n\r\nRationale:\r\nThere were a couple of times when there were ranked CTFs showing up e.g. 24h before (the recent WCTF being a best example of that) or even after they started (I remember one such case in 2013-2014). Some teams didn't participate because they didn't notice in time. Other couldn't register because when they noticed, the registration was already closed (not all CTFs keep registration open after the start).\r\nThis leads to bad situations where the ranking is influenced by the frequency of hitting F5 on CTFTime.org (because even RSS is sometimes laggy) and not CTF skill as it probably should be."},"comment":{"url":"https://api.github.com/repos/ctftime/ctftime.org/issues/comments/71337694","html_url":"https://github.com/ctftime/ctftime.org/issues/9#issuecomment-71337694","issue_url":"https://api.github.com/repos/ctftime/ctftime.org/issues/9","id":71337694,"user":{"login":"kyprizel","id":390217,"avatar_url":"https://avatars.githubusercontent.com/u/390217?v=3","gravatar_id":"","url":"https://api.github.com/users/kyprizel","html_url":"https://github.com/kyprizel","followers_url":"https://api.github.com/users/kyprizel/followers","following_url":"https://api.github.com/users/kyprizel/following{/other_user}","gists_url":"https://api.github.com/users/kyprizel/gists{/gist_id}","starred_url":"https://api.github.com/users/kyprizel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kyprizel/subscriptions","organizations_url":"https://api.github.com/users/kyprizel/orgs","repos_url":"https://api.github.com/users/kyprizel/repos","events_url":"https://api.github.com/users/kyprizel/events{/privacy}","received_events_url":"https://api.github.com/users/kyprizel/received_events","type":"User","site_admin":false},"created_at":"2015-01-24T21:16:02Z","updated_at":"2015-01-24T21:16:02Z","body":"I like the idea - i think it should be part of huge \"weight gathering\" problem discussed in issue 1."}}