| 03:31.48 | *** join/#dub Pimpi_ (n=frank@gondolin.pimpi.org) |
| 03:31.48 | *** mode/#dub [+o Pimpi_] by ChanServ |
| 16:18.13 | *** join/#dub Grumpfy (n=Grumpf@about/essy/Happy/Grumpfy) |
| 16:18.14 | *** mode/#dub [+v Grumpfy] by ChanServ |
| 20:14.17 | Pimpi_ | catay: ping |
| 21:20.33 | *** join/#dub Grumpfy (n=Grumpf@about/essy/Happy/Grumpfy) |
| 21:20.33 | *** mode/#dub [+v Grumpfy] by ChanServ |
| 21:57.36 | catay | pong Pimpi_ |
| 21:58.35 | catay | Pimpi_: fyi, you can also let the plugin write the reports direclty to file instead of the default bzfs logging |
| 21:58.47 | catay | thats how I use it |
| 22:08.00 | catay | I can give you also my reporting script (very basic) if you want. |
| 22:09.21 | catay | http://catay.be/report_matches.txt |
| 22:20.09 | Pimpi_ | catay: does the plugin need any further options to report matches directly via http? |
| 22:20.17 | Pimpi_ | is the url hardcoded? |
| 22:21.27 | catay | yeah it's hardcoded for now |
| 22:21.31 | catay | it works btw :) |
| 22:21.38 | Pimpi_ | fine :) |
| 22:21.39 | catay | I am planning a rewrite of the plugin |
| 22:21.50 | catay | which makes all of this stuff much more configurable |
| 22:22.37 | Pimpi_ | don't make it use it's own config file |
| 22:22.56 | Pimpi_ | it's just another source of errors |
| 22:23.24 | catay | how would you do it ? |
| 22:23.49 | catay | because I was thinking about a config file :) |
| 22:24.00 | Pimpi_ | useful defaults and a comma separated option list |
| 22:24.26 | catay | I also want to make the /official /contest /whatever configurable for example |
| 22:25.10 | Pimpi_ | like option=value,option2=value,option3=value |
| 22:25.12 | catay | and some other cool stuff like player zelo reporting in game by querying the 1vs1 site |
| 22:25.56 | catay | thats an idea that Chestal once said to me |
| 22:26.30 | catay | yeah, I will keep your advice in mind :) |
| 22:26.49 | catay | but I agree, it will be hard to check the correctness of a config file |
| 22:27.10 | catay | an option list is far easier to check |
| 22:28.00 | Pimpi_ | yes, zelo chech would be cool, but keep in mind, that importing data from an insecure source micgt include a potential securits thread |
| 22:28.29 | Pimpi_ | damn, can't type tonight... |
| 22:28.50 | Pimpi_ | yes, zelo check would be cool, but keep in mind, that importing data from an insecure source might include a potential security thread |
| 22:28.53 | Pimpi_ | better |
| 22:30.17 | Pimpi_ | maybe i'm just a little paranoid sometimes though |
| 22:31.01 | Pimpi_ | bzfs gets data from clients all the time - and all of those are insecure |
| 22:31.21 | Pimpi_ | much more than the 1v1 site |
| 22:32.19 | catay | also true |
| 22:34.29 | catay | but it would be a http request to the 1vs1 site , which only returns a value |
| 22:34.40 | Pimpi_ | yep |
| 22:34.43 | catay | I think it can be implemented pretty secure |
| 22:34.49 | Pimpi_ | easy to check |
| 22:35.32 | Pimpi_ | hey, i didn't know bz_addURLJob |
| 22:35.45 | Pimpi_ | damn, thats a handy toy :) |
| 22:35.48 | catay | yup :) |
| 22:36.00 | catay | there is some good stuff in the bz api |
| 22:36.12 | catay | you can also implement it as a handler |
| 22:36.27 | catay | so you can work with the result the request gives back and suchs |
| 22:37.23 | catay | but I encountered some strange issue with bz_urlEncode , I have to poke JeffM about that |
| 22:37.52 | catay | it doesn't work correclty when you use it with (s)printf , don't know why |
| 22:39.44 | Pimpi_ | hm |
| 22:42.03 | Pimpi_ | the german lottery had a jackpot of 43M Euro tonight |
| 22:42.29 | Pimpi_ | i didn't get it, seems i have to keep on working for a living... |
| 22:43.15 | catay | hehe |
| 22:43.34 | catay | I could use some of that money too :) |
| 22:45.23 | Pimpi_ | bedtime, good night |
| 22:45.49 | catay | nite Pimpi_ , thanks for updating the servers so fast ! :) |
| 22:52.06 | *** join/#dub Pimpinella (n=frank@gondolin.pimpi.org) |
| 22:52.06 | *** mode/#dub [+o Pimpinella] by ChanServ |