[05:10] Wait, hold up. [05:11] Are we not grabbing URL shorteners? [05:18] correct [05:18] the tracker needs rewritten [07:21] Oh mean. [07:21] Man. [07:21] OK, I really wish this was brought to my attention sooner. [07:21] I just didn't grock what was going on. [07:22] OK, whose tracker was it? [07:26] it was soultcer [07:26] he retired from urlteam [07:36] OK, and we are waiting for what to happen? [07:36] A coder? A person to find a coder? [07:49] the fire in our bellies [10:26] Well at the moment, we need a coder. [10:26] The previous tracker was, 1. too unstable, 2. too unsecure, and 3. too tedious to use [12:24] Well 2 and 3 for sure. 1) was most likely due to the setup you had, GLaDOS? [12:40] I think it was half my setup, half it not handling most things well [12:41] yeah, alright [12:42] in other words, it's not completely useless - but a rewrite would ease operations generally [15:54] GLaDOS What kind of resources are needed to host the tracker? I know a bit about python and my fiancé was a python developer who could probably help out a bit. [15:54] email me if you are interested [REDACTED] [15:54] no idea why he said that in PM, but ok [17:18] hm [18:20] I have a server I could try to get the tracker running on if you wanted [18:43] Twem: Sure. [19:23] i wish i could help with a rewrite if i was paid [22:10] ? [22:10] If you agree, Step 1: Get the tracker back up and running using the code we have, Step 2: Rewrite. At least we can continue to preserve the data that is soon to be lost with the code we have, then improve on it. Could someone point me in the right direction for the scripts/install method. Is there more than what is in git? Who has the database [23:18] we already had it hosted on GLaDOS' server, no? [23:18] it was just unstable (possibly because of sqlite)