| 00:02.57 | *** join/#bzflag zuii (~akos@BC06BF93.catv.pool.telekom.hu) |
| 00:06.59 | *** join/#bzflag Delusional (~Delusiona@unaffiliated/delusional) |
| 00:07.22 | macsforme | how soon are you planning to take away the http list server interface? |
| 00:08.59 | macsforme | oh, I guess /etc/ssl/certs is empty on my device... that would do it |
| 00:10.18 | *** join/#bzflag zuii (~akos@BC06BF93.catv.pool.telekom.hu) |
| 00:21.22 | macsforme | I guess the options are 1) don't use ssl, 2) configure curl not to try to verify the certificate authority, or 3) try to package a certificate bundle with the application (which is a bit of a time bomb) |
| 00:31.03 | blast007 | http://curl.haxx.se/docs/sslcerts.html "curl_easy_setopt(curl, CURLOPT_CAPATH, capath);" http://curl.haxx.se/docs/caextract.html |
| 00:37.32 | macsforme | it looks like the COMODO certificate expires in 2029... I think it's probably safe to package that one with it (unless we move to a different CA... some of the certificates expire much sooner) |
| 00:40.43 | blast007 | I would probably switch to Let's Encrypt at some point |
| 00:45.11 | macsforme | and those expire like every three months :P |
| 00:45.55 | macsforme | think I'll just do #2, and skip local verification for now... maybe later firmware updates will include a better solution |
| 00:47.16 | the_map | github is down! |
| 00:56.15 | blast007 | do not skip verification |
| 00:57.37 | macsforme | then what's a better solution? |
| 00:58.03 | blast007 | not releasing it at all |
| 00:58.35 | macsforme | wow |
| 00:58.44 | blast007 | why must we support every braindead platform out there? |
| 01:00.29 | macsforme | well, you're right in a sense... we have a lot of legacy cruft in our code from abandoned platforms |
| 01:00.41 | macsforme | but if someone else wants to, why is it a problem? I'm not planning to push this code to our main repository |
| 01:01.08 | blast007 | because you're reducing security just to shove the game into that platform |
| 01:01.19 | *** join/#bzflag alpha1-2 (~alpha1@host95.201-252-189.telecom.net.ar) |
| 02:25.03 | *** join/#bzflag Shuist (~Shuist@ppp203-122-213-220.static.internode.on.net) |
| 02:50.49 | the_map | github is back up! |
| 02:55.58 | zuii | yaay |
| 02:58.04 | zuii | calling bz_sendTextMessage from another thread is not safe right?! can i have threads in a plugin? |
| 03:04.13 | allejo | what are you doing with a plugin that needs threads? |
| 03:04.24 | BulletCatcher | BZFlag is mostly not thread-safe. |
| 03:04.27 | BulletCatcher | We save screenshots in a thread, but that doesn't interact with the rest of the system. |
| 03:04.29 | BulletCatcher | You could do similar decoupled things in threads, but it would be necessary for the main process (er, thread) to use the API to ensure data consistency. |
| 03:05.59 | zuii | write to disk etc. |
| 03:07.49 | zuii | or i have sql connection; |
| 03:21.50 | *** join/#bzflag brlcad (~sean@66-118-151-70.static.sagonet.net) |
| 03:24.42 | *** join/#bzflag Notify (~notify@66-118-151-70.static.sagonet.net) |
| 03:46.18 | the_map | can't load the server list right now, but it's entirely possible that it's my internet connection hating me again |
| 03:49.26 | BulletCatcher | It isn't just you. |
| 03:49.27 | BulletCatcher | It looks like I can open a TCP connection to bzflag.org:443, but can't send any data. |
| 03:50.02 | the_map | thanks for the confirmation :) |
| 03:55.17 | allejo | http://bzstats.strayer.de/servers/?lang=en |
| 05:00.20 | BulletCatcher | The list server is its usual snappy self again. |
| 05:04.46 | the_map | ...an FPS of 10 does *not* look good |
| 05:04.56 | the_map | also, message of the day is not available again |
| 05:20.51 | *** join/#bzflag brlcad (~sean@66-118-151-70.static.sagonet.net) |
| 05:23.10 | *** join/#bzflag Notify (~notify@66-118-151-70.static.sagonet.net) |
| 05:38.24 | the_map | just spent a while at apoc with RC3, the only issue being the FPS, but that might just be me |
| 05:38.56 | the_map | is on Ubuntu 15.10 |
| 05:40.16 | the_map | I was in obs the whole time though |
| 05:40.41 | macsforme | did you set up your drivers? :) |
| 05:41.50 | the_map | what? |
| 08:17.55 | *** join/#bzflag ruskie (~ruskie@sourcemage/mage/ruskie) |
| 08:23.37 | *** join/#bzflag ruskie (ruskie@sourcemage/mage/ruskie) |
| 09:42.59 | *** join/#bzflag valera_rozuvan (~Valera@176.104.51.77) |
| 10:58.33 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 12:58.27 | *** join/#bzflag valera_rozuvan (~Valera@176.104.51.77) |
| 13:10.57 | *** join/#bzflag zuii (~akos@BC06BF93.catv.pool.telekom.hu) |
| 13:31.36 | *** join/#bzflag blast007 (~blast007@bzflag/developer/Blast) |
| 13:40.09 | *** join/#bzflag blast007 (~blast007@bzflag/developer/Blast) |
| 13:46.55 | *** join/#bzflag blast007 (~blast007@bzflag.org) |
| 13:46.56 | *** join/#bzflag blast007 (~blast007@bzflag/developer/Blast) |
| 14:08.53 | blast007 | There does seem to be some network issues with my provider. Collecting some info to pass on to their support. |
| 14:16.46 | *** join/#bzflag blast007 (~blast007@bzflag/developer/Blast) |
| 14:19.10 | blast007 | At least this immediate incident was apparently a "massive DDoS" directed at my provider's network. |
| 14:22.06 | kierra | apoc went down? |
| 14:32.14 | *** join/#bzflag blast007 (~blast007@bzflag/developer/Blast) |
| 15:24.36 | the_map | I wonder if blast007's issues are related to the github issues yesterday |
| 15:25.00 | blast007 | no |
| 15:27.15 | *** join/#bzflag kaadmy (uid135503@gateway/web/irccloud.com/x-xsibvxnefijgkeqb) |
| 16:09.51 | *** join/#bzflag valera_rozuvan (~Valera@176.104.51.77) |
| 16:58.01 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 17:40.49 | *** join/#bzflag alpha1-2 (~alpha1@host95.201-252-189.telecom.net.ar) |
| 18:01.23 | alpha1-2 | Hi, some questions: regarding to that bug in which you lose the target of GM just after shooting your last shot, then the missile surely fails: I am almost sure it's still active in RC2 (I saw it the other day, but it's a little hard to test it in-game), then the questions are: 1) since it's an old bug, is it necessary I check it in a local server, o you would open a new issue in Github directly? 2) Would it be fixed before the next |
| 18:01.25 | alpha1-2 | release or it's not so important/you don't fix all bugs necessarely before doing it? 3) If, in the remote possibility, I could fix it, and since I don't want to register, could someone commit it by me saying just "alpha1"? (Are you hurried about it? How much time would I have to do it?) |
| 18:17.28 | allejo | Fixing that would give 2.4.4 clients an advantage over 2.4.2, so the fix will have to wait until 2.6 |
| 18:20.48 | allejo | https://github.com/BZFlag-Dev/bzflag/issues/24 |
| 18:25.02 | alpha1-2 | oh, really? is it so serious? :) Ah, I see the bug there... and that pro tip by BC is true, I remember it, though hard |
| 18:26.11 | allejo | It is not serious. Like I said, it'll give 2.4.4 clients an advantage over 2.4.2 clients |
| 18:26.37 | alpha1-2 | I don't see it so serious, it's just a bug; and people should use the last version anyway |
| 18:27.32 | allejo | Debian Wheezy distributes 2.4.2 and that'll be last version for Wheezy |
| 18:27.37 | allejo | iirc |
| 18:28.23 | allejo | And I said, it is not serious. But it's an inconsistency between point releases |
| 18:28.39 | allejo | Therefore it has to wait until 2.6 |
| 18:30.02 | blast007 | jessie was the one with 2.4.2 |
| 18:30.34 | alpha1-2 | why are you basing in a linux release which is known to update very slowly? |
| 18:30.48 | blast007 | alpha1-2: anything that alters gameplay in a way that would make one client version behave differently than another requires waiting for a new major release of the game |
| 18:31.12 | allejo | Besides, BZFlag is known to update very slowly ;) |
| 18:32.42 | alpha1-2 | ah, okay, then gameplay issues are seriously, I understand... would I be able to start fixing it anyway? |
| 18:32.50 | alpha1-2 | serious* |
| 18:34.06 | alpha1-2 | there is a 2.5 branch, isn't there? |
| 18:34.17 | allejo | The master branch |
| 18:34.58 | alpha1-2 | and the way to commit it, as I mentioned? |
| 18:35.32 | allejo | Pull request |
| 18:35.43 | alpha1-2 | *w/o registration* |
| 18:36.16 | allejo | I may be wrong, but you can't |
| 18:36.26 | alpha1-2 | in the past it was possible |
| 18:36.52 | alpha1-2 | anonimity in internet is important |
| 18:37.06 | allejo | There were patches submitted to Sourceforge. But that still requires registration |
| 18:37.11 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 18:37.18 | allejo | Our process now is pull requests and I don't see that changing |
| 18:39.04 | alpha1-2 | see "(War Pig)", "(cobrafast)" and "(harry666t)" in example. Were they registered? |
| 18:39.26 | alpha1-2 | hi Cobra_Fast |
| 18:39.38 | allejo | Before my time, but most likely yes |
| 18:40.08 | allejo | There are no anonymous commits, if there are that's because the commit info was lost or not accurate from the beginning |
| 18:40.46 | allejo | WarPig has an account on github so it's safe to assume he was on sourceforge. Same for cobra |
| 18:43.01 | alpha1-2 | then commiting by someone else is not "allowed" or what? is there a GitHub license issue about it? is there not a techical way to write "nick-x" in the author field? |
| 18:43.50 | alpha1-2 | I knew another project (other country) which run their own version of git, also |
| 18:45.17 | allejo | It's not a matter of GitHub. It's so we can keep history of where or how something came about, kinda the point of version control |
| 18:45.34 | alpha1-2 | or... any... workaround? the important thing is that the fix is mentioned in the credits part and in the details, IMO |
| 18:45.38 | allejo | We're not going to start accepting patches and start committing them for other people |
| 18:46.54 | blast007 | it's also about copyright |
| 18:47.15 | blast007 | we're not going to accept code from random places |
| 18:49.31 | alpha1-2 | yes, I understand the technical part (version control)... Okay, about Copyright too... well, I will continue thinking; I though it was allowed since I saw it but if they were registered, then not |
| 18:49.45 | alpha1-2 | thought* |
| 18:50.11 | alpha1-2 | maybe Cobra_Fast will say something later |
| 18:51.00 | allejo | There's nothing he can say that will change the current process |
| 18:51.05 | alpha1-2 | is it not possible by forums/development section? |
| 18:51.11 | allejo | He had an account on SF and had/has commit access |
| 18:51.19 | alpha1-2 | I am registered there |
| 18:51.21 | allejo | No it is not |
| 18:51.31 | allejo | Then registering in github should not be an issue |
| 18:52.11 | alpha1-2 | in a very centralized system? I have some issues about that :) |
| 18:52.38 | blast007 | alpha1-2: If you're not comfortable registering on GitHub, don't worry about it. I'm sure someone else can work on that issue. |
| 18:52.51 | alpha1-2 | well, just saying, the copyright part could be covered by forums |
| 18:53.08 | blast007 | what |
| 18:54.14 | alpha1-2 | but the version control one, not sure |
| 18:54.23 | alpha1-2 | no problem, just wated to help :) |
| 18:54.39 | alpha1-2 | at least I can continue testing things |
| 18:55.28 | alpha1-2 | if blast started a localized version of git like I saw, then version control part would be fixed too, just saying, don't worry :) |
| 18:55.32 | kierra | seems like we discuss and waste time on non issues |
| 18:55.39 | blast007 | what |
| 18:57.03 | zuii | nothing wrong with git version control, i dont get it whats your problem alpha; send your patches someone if u have problem with github |
| 18:57.22 | allejo | we're not doing that ^ |
| 18:57.45 | blast007 | we're already less strict than we should be about this kind of stuff |
| 18:58.26 | zuii | we should include signatures to source files |
| 18:58.58 | blast007 | I mean about copyright, not that |
| 18:59.27 | alpha1-2 | last phrase: IMO, what I can see in CREDITS file, which I understand is the final legal part of Copyright, is the important part. And I can see there only nicks (and I want that). The technical part is apart. |
| 19:01.51 | alpha1-2 | zuii: it seems I can't do it, according to what I was told by allejo |
| 19:02.55 | alpha1-2 | I can nowadays handle git (from GitHub) by doing clone etc, BTW |
| 19:03.55 | alpha1-2 | I can't push OFC, or pull request, tho, if I am right. But I could send diff files to someone else |
| 19:04.01 | allejo | we are not including signatures in the source code. that will quickly get out of hand and clutter up the code with useless information that is available in git |
| 19:04.50 | allejo | accepting diffs or patches from random people and applying for them is not something i see us doing |
| 19:11.45 | alpha1-2 | blast007: what do you mean by "less strict" if you can explained me it please? |
| 19:13.10 | alpha1-2 | explain it to me* |
| 19:14.30 | alpha1-2 | AUTHORS file* |
| 19:14.32 | blast007 | alpha1-2: read DEVINFO |
| 19:14.58 | blast007 | in this case, specifically the "Committing Changes" sections |
| 19:16.03 | blast007 | the AUTHORS file has nothing to do with your misunderstanding |
| 19:37.32 | alpha1-2 | blast007: I read that part (and the Developer Agreement again), I understand the developing process now. But, by "less strict", do you mean that Copyright still belongs in some way to the original author or what? Sorry, I still don't understand that part |
| 19:38.29 | blast007 | "less strict" as in there's no formal written/signed agreement between contributors and the project, and no formal company that copyrights is assigned to |
| 19:39.33 | alpha1-2 | okay, thanks |
| 19:40.50 | alpha1-2 | I found a bug in DEVINFO: "Submiting changes... you should create a pull *request*." |
| 19:41.28 | alpha1-2 | (I contributed with something!) |
| 19:41.44 | alpha1-2 | Public Domain, np ;) |
| 19:58.29 | alpha1-2 | thanks allejo too |
| 20:05.14 | *** mode/#bzflag [+o blast007] by ChanServ |
| 20:06.17 | kierra | bakes cookies laced with arsenic for alpha1-2 |
| 20:06.50 | alpha1-2 | I don't know "arsenic"... is that a new taste? :P |
| 20:07.05 | kierra | you won't know till you try them :) |
| 20:07.13 | *** topic/#bzflag by blast007 -> http://BZFlag.org || http://ohloh.net/p/bzflag || https://wiki.bzflag.org/Getting_Help || Channel Logs: http://infobot.rikers.org/%23bzflag/ || 2.4.4-RC3 https://forums.bzflag.org/viewtopic.php?f=62&t=19175 |
| 20:07.19 | *** mode/#bzflag [-o blast007] by blast007 |
| 20:08.09 | alpha1-2 | ;S |
| 20:08.20 | alpha1-2 | you first |
| 20:10.19 | kierra | you're the one who asked me for cookies: [15:05:40] <alpha1-2> cookies |
| 20:10.20 | kierra | [15:05:50] <alpha1-2> I want my prize! |
| 20:10.57 | alpha1-2 | aawww, but you are evil :P |
| 20:11.09 | blast007 | not as evil as I am |
| 20:11.35 | alpha1-2 | ok |
| 20:19.11 | *** join/#bzflag sanandresm (~andres@181.49.254.102) |
| 23:18.41 | *** join/#bzflag zuii (~cauchy@BC06BF93.catv.pool.telekom.hu) |
| 23:20.31 | *** join/#bzflag zuii (~cauchy@BC06BF93.catv.pool.telekom.hu) |
| 23:37.47 | *** join/#bzflag Shuist (~Shuist@ppp203-122-213-220.static.internode.on.net) |