{"author_link":"\/users\/tustin2121","author_name":"Tustin2121","author_uid":"tustin2121","comments":[],"epoch":1569519982,"event":"LD45","format":"md","ldjam_node_id":162229,"likes":21,"metadata":{"p_key":"133391","p_author":"Tustin2121","p_authorkey":"1122630","p_urlkey":"349595","p_title":"Ok, so theme slaughter is officially broken","p_cat":"LDJam ","p_event":"LD45","p_time":"1569519982","p_likes":"21","p_comments":"0","p_status":"WAYBACK","us_key":"1122630","us_name":"Tustin2121","us_username":"tustin2121","event_start":"1570147200","event_key":"78","event_name":"Ludum Dare 45"},"node":{"_collation":{"body_sanitizer":"TextUtils::SanitizeHTML via existing importer","event":"LD45","removed_author":false},"_superparent":159347,"_trust":1,"author":122630,"body":"I've been saying for the past 4 days (or million years, however long this theme slaughter has been going on for, I can't tell anymore) that there seems to be several duplicate themes in this year's batch of themes, and that they should de-dupe the themes before giving them to us.\n\nTurns out, no, it's just that the theme voting page is entirely broken.\n\nThere's been a few people in this feed that have pointed out that the recent themes list when you load the page is always the same.\n![brokethemes1.PNG](\/\/\/raw\/60f\/d1\/z\/25383.png)\nThis I think is indicative of the bigger problem. The page seems to not be keeping track of the themes that have already been voted on *entirely*. I pulled open the JSON giving the web page all the themes to vote on. (Incidentally, the 10 themes on the recent list here are the first 10 themes in the JSON, go figure.) (EDIT: Just not in my screenshot, I just realized, because it's apparently keeping somewhere that I haven't voted on some of the themes, but it's not filtering out voting based on that?! What even is going on here...?)\n\n\"All about perspective\" is in the list exactly once. But I've voted on it *at least* three times, once because I liked it, once again later as it was a duplicate (and that made my recent themes list all red, which I thought at the time was odd), and once more today, just now, and look, there's a green in my recent themes list that's there again!\n\n\"It's not a bug, it's a feature\" is a distinctive theme that I remember not liking (why would you make a weird development concept into a game?), and I voted on it a second time just moments ago! I wondered how many times it had been submitted. I went and checked, and lo it's only in the JSON once. This whole exercise is now pointless if you can't do it in one sitting, because if you don't, you're going over old ground again, while simultaneously you'll never see some themes! Why even bother counting how many themes we've slaughtered if you're not going to keep track of which ones we've seen already!\n\nBasically what I'm saying is, I'm giving up. I'd rather not have to rejudge the same 1500 themes again and again and again simply because I didn't do it in one sitting and got logged out. Now excuse me while I go upend a table.\n\n----\n\nIncidentally, while I have the JSON here:\n\n* \"Time\" is a word in 87 submitted themes this time around (not counting where it's part of another word).\n* \"Space\" is part of 32 submitted themes.\n* \"Light\" is in 28 themes.\n* \"Power\" is in 38 themes.\n* \"Death is in 23 themes, while \"Life\" is in 58 themes (not exclusive).\n* \"Islands\" is only in 6 themes, the same number of times as \"Climate\".","comments":7,"comments-timestamp":"2019-10-02T23:49:37Z","created":"2019-09-26T17:19:46Z","files":[],"files-timestamp":0,"id":162229,"love":21,"love-timestamp":"2020-04-08T08:10:56Z","meta":[],"modified":"2020-04-08T08:10:56Z","name":"Ok, so theme slaughter is officially broken","node-timestamp":"2019-09-26T17:53:20Z","parent":161258,"parents":[1,5,9,159347,161258],"path":"\/events\/ludum-dare\/45\/$161258\/ok-so-theme-slaughter-is-officially-broken","published":"2019-09-26T17:46:22Z","scope":"public","slug":"ok-so-theme-slaughter-is-officially-broken","subsubtype":"","subtype":"","type":"post","version":483310},"node_metadata":{"n_key":"162229","n_urlkey":"349595","n_parent":"161258","n_path":"\/events\/ludum-dare\/45\/$161258\/ok-so-theme-slaughter-is-officially-broken","n_slug":"ok-so-theme-slaughter-is-officia","n_type":"post","n_subtype":"","n_subsubtype":"","n_author":"122630","n_created":"1569518386","n_modified":"1586333456","n_version":"483310","n_status":"WAYBACK"},"source_url":"https:\/\/ldjam.com\/events\/ludum-dare\/45\/$161258\/ok-so-theme-slaughter-is-officially-broken","text":"I've been saying for the past 4 days (or million years, however long this theme slaughter has been going on for, I can't tell anymore) that there seems to be several duplicate themes in this year's batch of themes, and that they should de-dupe the themes before giving them to us.\n\nTurns out, no, it's just that the theme voting page is entirely broken.\n\nThere's been a few people in this feed that have pointed out that the recent themes list when you load the page is always the same.\n![brokethemes1.PNG](\/\/\/raw\/60f\/d1\/z\/25383.png)\nThis I think is indicative of the bigger problem. The page seems to not be keeping track of the themes that have already been voted on *entirely*. I pulled open the JSON giving the web page all the themes to vote on. (Incidentally, the 10 themes on the recent list here are the first 10 themes in the JSON, go figure.) (EDIT: Just not in my screenshot, I just realized, because it's apparently keeping somewhere that I haven't voted on some of the themes, but it's not filtering out voting based on that?! What even is going on here...?)\n\n\"All about perspective\" is in the list exactly once. But I've voted on it *at least* three times, once because I liked it, once again later as it was a duplicate (and that made my recent themes list all red, which I thought at the time was odd), and once more today, just now, and look, there's a green in my recent themes list that's there again!\n\n\"It's not a bug, it's a feature\" is a distinctive theme that I remember not liking (why would you make a weird development concept into a game?), and I voted on it a second time just moments ago! I wondered how many times it had been submitted. I went and checked, and lo it's only in the JSON once. This whole exercise is now pointless if you can't do it in one sitting, because if you don't, you're going over old ground again, while simultaneously you'll never see some themes! Why even bother counting how many themes we've slaughtered if you're not going to keep track of which ones we've seen already!\n\nBasically what I'm saying is, I'm giving up. I'd rather not have to rejudge the same 1500 themes again and again and again simply because I didn't do it in one sitting and got logged out. Now excuse me while I go upend a table.\n\n----\n\nIncidentally, while I have the JSON here:\n\n* \"Time\" is a word in 87 submitted themes this time around (not counting where it's part of another word).\n* \"Space\" is part of 32 submitted themes.\n* \"Light\" is in 28 themes.\n* \"Power\" is in 38 themes.\n* \"Death is in 23 themes, while \"Life\" is in 58 themes (not exclusive).\n* \"Islands\" is only in 6 themes, the same number of times as \"Climate\".","title":"Ok, so theme slaughter is officially broken","wayback_source":[]}