IRC log for #bzflag on 20140212

00:15.46*** join/#bzflag JeffM (~JeffM@107-209-61-105.lightspeed.irvnca.sbcglobal.net)
01:03.44*** join/#bzflag ahs3- (~ahs3-@adsl-065-005-193-158.sip.rdu.bellsouth.net)
01:11.04*** join/#bzflag mebigfatguy (~dave@128.177.74.185)
03:17.36*** join/#bzflag spldart (~james@c-76-30-94-74.hsd1.tx.comcast.net)
03:17.36*** join/#bzflag spldart (~james@bzflag/contributor/spldart)
03:17.36*** mode/#bzflag [+v spldart] by ChanServ
03:21.23*** join/#bzflag JeffM (~JeffM@unaffiliated/jeffm2501)
03:21.24*** mode/#bzflag [+v JeffM] by ChanServ
03:42.30*** join/#bzflag ashvala (~ashvala@unaffiliated/ashvala)
04:40.43*** join/#bzflag ruskie (ruskie@sourcemage/mage/ruskie)
04:51.22*** join/#bzflag khonkhortisan (~kyle@c-50-132-81-139.hsd1.wa.comcast.net)
04:53.32*** join/#bzflag khonkhortisan (~kyle@c-50-132-81-139.hsd1.wa.comcast.net)
04:58.44*** join/#bzflag contempt (contempt@unaffiliated/contempt)
05:45.42*** mode/#bzflag [-v short_circuit] by ChanServ
08:22.46*** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535)
11:50.30*** join/#bzflag Pimpinella (~frank@gondolin.pimpi.org)
11:53.41*** join/#bzflag _lmnop (~lmnop@24-134-41-57-dynip.superkabel.de)
11:57.23*** join/#bzflag _lmnop2 (~lmnop@24-134-41-57-dynip.superkabel.de)
13:30.38*** join/#bzflag Pimpinella (~frank@gondolin.pimpi.org)
15:12.07*** join/#bzflag sirquine (~quine@c-24-8-100-27.hsd1.co.comcast.net)
15:47.12*** join/#bzflag macsforme (~josh@bzflag/developer/Constitution)
15:47.55*** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535)
15:49.41*** join/#bzflag raindog_ (~quassel@50.42.152.218)
15:51.30*** join/#bzflag blast007_ (~blast007@bzflag/developer/Blast)
16:03.34*** join/#bzflag ahs3- (~ahs3-@adsl-065-005-193-158.sip.rdu.bellsouth.net)
16:19.15*** join/#bzflag ruskie (ruskie@sourcemage/mage/ruskie)
16:54.42*** join/#bzflag TimRiker (~TimRiker@bzflag/projectlead/TimRiker)
16:54.43*** mode/#bzflag [+o TimRiker] by ChanServ
16:55.03*** join/#bzflag _lmnop (~lmnop@24-134-41-57-dynip.superkabel.de)
17:42.13*** join/#bzflag Pimpinella (~frank@gondolin.pimpi.org)
17:58.16*** join/#bzflag SpazzyMcGee (~SpazzyMcG@4e56a1e6.skybroadband.com)
18:22.06*** join/#bzflag JeffM (~JeffM@12.167.61.62)
19:11.30*** join/#bzflag thrakattak (cz3141@gateway/shell/devio.us/x-hdmkwdepoklibtut)
19:17.36*** join/#bzflag ts (~ts@66-118-151-70.static.sagonet.net)
19:18.27*** join/#bzflag SpazzyMcGee_ (~SpazzyMcG@bcdc6566.skybroadband.com)
19:20.30*** join/#bzflag SpazzyMcGee (~SpazzyMcG@2e40e6e9.skybroadband.com)
19:25.34*** join/#bzflag SpazzyMcGee_ (~SpazzyMcG@bcdc656b.skybroadband.com)
19:36.32kierraChestal: ping
19:38.21*** join/#bzflag SpazzyMcGee_ (~SpazzyMcG@4e56a1e6.skybroadband.com)
19:40.39*** join/#bzflag SpazzyMcGee (~SpazzyMcG@bcdc6573.skybroadband.com)
19:44.34*** join/#bzflag SpazzyMcGee_ (~SpazzyMcG@bcdc6576.skybroadband.com)
19:47.52*** join/#bzflag SpazzyMcGee (~SpazzyMcG@5ec38f23.skybroadband.com)
19:52.55allejo~Constitution++
20:36.04JeffMwhat's the main issue with auto-reporting?
20:36.17JeffMjust bugs in the plug-in? because I'd assume it'd be super easy
20:40.24blast007the GU site has also been down a number of times recently
20:41.43JeffMwhy?
20:42.02blast007bacon stuck in the PSU
20:42.07JeffMagain, can't be that hard to run a little website :)
20:42.45blast007iirc, it's behind cloudflare, which I think is a bit overkill.. or a sign the server can't handle a simple dynamic site
20:43.28JeffMmy cheapass VPS handles that level of traffic just fine
20:43.39blast007yeah..
20:43.45JeffMI'd not want to host a game on it, but for normal stuff it's fine
20:45.28blast007there's plenty of ways to handle the site being down..  dump the JSON data to the log and allow that to be copy/pasted into the site later, have a local SQLite database that it dumps pending data to (even though I know we got rid of that), etc..
20:46.02JeffMown two cheapss VPSs that are in sync
20:46.32blast007the trouble spots would be if it actually receives the data but doesn't return a success back to the plugin
20:46.41JeffMyeah
20:46.50blast007but something like a UUID generated by the plugin could help prevent duplicate entries
20:46.58JeffMyeah
20:47.18JeffMI'd stage it and have a backend system be what the plugin connects to then that logs and pushes to the display site
20:47.32blast007or even at the start of a match having the plugin tell the server "I'm starting a match - give me a number" and then the server just waits for that data to come back
20:47.44blast007the web server, that is
20:47.48*** join/#bzflag contempt (~contempt@unaffiliated/contempt)
20:47.58JeffMyeah
20:48.02blast007a transaction system, of sorts
20:48.11JeffMnot of sorts, that's what you are doing :)
20:48.14blast007:)
20:48.21JeffMthen you know how many matches failed to complete
20:48.39blast007and you also possibly know ahead of time if the match site is down
20:48.44JeffMyeah
20:48.49JeffMI'd round robbin them
20:48.56JeffMhave multiple match reporters
20:49.06JeffMand you work with the one that you connect to
20:49.12blast007separate from the website?
20:49.16JeffMyeah
20:49.21JeffM2-3 small match reporters
20:49.22blast007yeah, that'd be ideal
20:49.29JeffMthen it's there job to merge into the central database
20:49.35JeffMalso use them as live sync backups
20:49.42JeffMthen a read only copy on the website
20:49.55blast007makes it a slight bit more complicated, of course :)
20:49.57JeffMyou've got a lot of unique IDs going on already
20:50.03JeffMyeah but it's not hard to merge
20:50.19JeffMyou know you can't have 2 matches reported at the same start time from the same source server
20:50.23JeffMso it's easy to sort them out
20:50.58JeffMgetting a UID for the match based on those makes it very easy to resolve
20:51.21blast007and by "round robin" you're not necessarily referring to DNS, right?  just the general idea of multiple systems picked at random?
20:51.28JeffMyah
20:51.55blast007k.  not sure if our code would even pick an IP at random if a DNS server returned multiple IPs.
20:51.57*** join/#bzflag SpazzyMcGee_ (~SpazzyMcG@5d605e7d.skybroadband.com)
20:52.00JeffMand when you generate a match ID those match reporters then try to sync between all 3
20:52.24JeffMyeah I'd do it in code, match1,match2,match3 etc..
20:52.27blast007yep
20:52.40JeffMon startup have the plugin get the list of match servers that are up now from some central
20:52.46JeffMor use the last one if it can't
20:53.25JeffMI started the design for my leauge/auth system I just need a web person to implement it :)
20:53.59JeffMhttp://www.bzflag.me/login.html :)
21:03.53*** join/#bzflag contempt (contempt@unaffiliated/contempt)
21:26.40*** join/#bzflag Constitution (~josh@bzflag/developer/Constitution)
22:21.25bradfyi, the error with autoreport was: "The BZIDs (x,y,z) were not found on the same team. Match invalidated."
22:21.45braddon't think there's been issues with the reports not reaching the site, apart from when it was down last week
22:22.05bradbut the match servers dont go through cloudflare
22:22.35brad(which was put in place because of some jerk DDoSing)
22:23.25bradand one more thing, I think allejo has fixed that bug in recent builds
22:36.47*** join/#bzflag JeffM (~JeffM@107-209-61-105.lightspeed.irvnca.sbcglobal.net)
22:58.23blast007never said the match servers were behind cloudflare - we were talking about the website
23:09.54JeffMi was just curious why the rollout's taken so long
23:13.41blast007bugs, architecture changes (went from the web server sending SQL queries over HTTP to the plugin for updating the local cache to sending JSON data), difficulty integrating into the website (as it wasn't really designed with autoreport in mind)
23:17.29*** join/#bzflag Delusional (~delusiona@unaffiliated/delusional)
23:18.37JeffMahh
23:21.29JeffMso it took them time to design it right
23:24.08*** join/#bzflag AAA_awright (~aaa@2001:41d0:1:d632::1)
23:34.39*** join/#bzflag dcat (~dcat@c-98-244-106-246.hsd1.va.comcast.net)
23:59.56*** join/#bzflag ashvala (~ashvala@unaffiliated/ashvala)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.