| 18:43.42 | *** join/#bzflag infobot (ibot@rikers.org) |
| 18:43.42 | *** topic/#bzflag is http://BZFlag.org || https://www.ohloh.net/p/bzflag || http://wiki.BZFlag.org/Getting_Help || Channel Logs: http://ibot.rikers.org/%23bzflag/ || 2.4.2 Current version http://goo.gl/PI9KFD |
| 18:43.42 | *** mode/#bzflag [+v infobot] by ChanServ |
| 18:44.29 | *** mode/#bzflag [+o blast007] by ChanServ |
| 18:45.20 | BulletCatcher | To expand on what Chestal said, Git branches and tags are both just pointers to specific commits, and either of them can mark the end of a commit sequence to keep it on the books. |
| 18:45.25 | BulletCatcher | Git lets you add and remove tags, but once added they always point to the same commit. |
| 18:45.30 | BulletCatcher | Git supports a much wider set of operations on the commit pointers called "branches", including renamimg them and changing them to point to different commits. |
| 18:45.35 | BulletCatcher | A single commit can have multiple branches and/or tags pointing to it. As long as at least one branch or tag points to a commit, it and its ancestors will be preserved in the repo. |
| 18:45.40 | BulletCatcher | This leads to one of the differences between Subversion and Git: a Subversion commit exists forever because there is no method for removing a commit from the middle of a Subversion repo's sole linear sequence of commits. |
| 18:45.45 | BulletCatcher | Git, on the other hand, supports multiple linear sequences of commits in a single repo that may or may not be branched from each other. Git makes it easy to copy (cherry-pick) or move (rebase) commit sequences from one place to another, and deleted commit sequences are a normal byproduct of these actions. |
| 18:45.52 | BulletCatcher | Garbage collection is not performed immediately on commit sequences without any branch/tag pointers, so don't panic if you mistakenly do a "git branch -D master" command. You have 90 days (by default) to learn the simple process to recover that deleted branch. |
| 18:48.07 | zuii | wow |
| 18:48.28 | zuii | where do you read this? |
| 18:48.28 | BulletCatcher | I had been working on that speech for the last hour. :-) |
| 18:48.38 | blast007 | :) |
| 18:48.48 | zuii | im looking for a book or something.. |
| 18:49.55 | zuii | sry for interrupt |
| 18:50.15 | zuii | great stuff btw |
| 18:50.42 | BulletCatcher | http://gitolite.com/gcs.html has a pretty nice Git introduction. |
| 18:50.53 | zuii | i want to make a regex pattern for callsign validation, registration page says "Username must be between 2 and 20 chars long and use alphanumeric, space or -+_[] characters." |
| 18:51.08 | zuii | ([a-z][A-Z])([a-z]|[A-Z]|[0-9]){1,} |
| 18:51.38 | blast007 | zuii: the forums and the game doesn't quite match up with each other. What are you needing a validator for? |
| 18:52.12 | zuii | ah just a little plugin |
| 18:52.37 | blast007 | a bzfs plugin? |
| 18:52.40 | zuii | it is not really necessary, just for sanity check |
| 18:52.43 | zuii | yes |
| 18:52.47 | blast007 | then I'm even less clear why you'd need a validator |
| 18:53.13 | zuii | https://github.com/akooos/bzflag-import-3/tree/v2_4_x/plugins/KeepQuiet |
| 18:53.46 | blast007 | still unclear |
| 18:53.53 | zuii | server side mute plugin(without permission) |
| 18:54.01 | zuii | slides are great btw |
| 18:54.16 | blast007 | right, but why do you need to check for callsign validity? |
| 18:54.31 | blast007 | what if we change what we allow later? then you'll have to update your plugin |
| 18:55.03 | Patlabor | all you need is the BZID |
| 18:55.10 | Patlabor | if it has a BZID it's valid |
| 18:55.21 | zuii | ..trolls won't reg |
| 18:55.32 | blast007 | trolls won't keep the same name either |
| 18:55.41 | zuii | so i use callsign but it can changed |
| 18:55.44 | Patlabor | then it doesn't matter if you "validate" the callsign |
| 18:55.55 | Patlabor | whatever callsign they are using is what htey will use |
| 18:56.03 | Patlabor | for non reg, filter by IP |
| 18:56.05 | Patlabor | or IP range |
| 18:56.18 | Patlabor | by the time the callsign gets to you it's already in bzfs |
| 18:56.28 | Patlabor | so it has to be valid for bzfs |
| 18:56.30 | Patlabor | what more can you validate? |
| 18:56.42 | blast007 | their SSN |
| 18:57.05 | zuii | SSN ? |
| 18:57.10 | blast007 | a joke :P |
| 18:57.13 | Patlabor | it's a joke |
| 18:57.14 | zuii | social security number? |
| 18:57.18 | Patlabor | yeah |
| 18:57.25 | zuii | :) |
| 18:57.26 | Patlabor | all you need is a way to Identify them |
| 18:57.37 | Patlabor | BZID, IP/Hostmask |
| 18:57.50 | Patlabor | I see no need to use callsign, ever |
| 18:58.06 | blast007 | except for the command to actually mute someone |
| 18:58.11 | zuii | i list silenced people when you log in |
| 18:58.23 | Patlabor | yeah that's just a refernce for the current session |
| 18:58.25 | Patlabor | why? |
| 18:58.35 | blast007 | so store that as a comment because that's all it is |
| 18:58.42 | zuii | thats what client do also |
| 18:58.45 | Patlabor | but even then, just store the callsign that was used during the request, that's good enough |
| 18:58.59 | Patlabor | or show the current callisng they are using |
| 18:59.06 | Patlabor | since you have a match |
| 18:59.19 | Patlabor | and just because the client does it, doesn't mean it's right :) |
| 18:59.41 | Patlabor | I'd store BZID and/or IP/hostmask |
| 19:00.02 | Patlabor | then when players join if they match a silcenced person, add the callsign they are using right then |
| 19:00.08 | Patlabor | and it's just a comment |
| 19:00.17 | Patlabor | it shold not affect filtering at all |
| 19:01.49 | Patlabor | the only input for callsigns you should take should be the command to add someone to a silence list |
| 19:02.03 | Patlabor | at that point you just need to see if they match a current player |
| 19:02.19 | Patlabor | you don't need to be able to add people who are not online |
| 19:02.26 | Patlabor | leave that for local |
| 19:03.34 | zuii | no, you can't add someone if not online |
| 19:03.47 | Patlabor | then there should be no reason for you to validate a callsign |
| 19:04.18 | zuii | i optionally allow to store "mutes" to a text file |
| 19:04.34 | Patlabor | sure but that should be bzid and IP |
| 19:04.36 | Patlabor | not callsign |
| 19:04.54 | zuii | i added bz_eMessageBeforeSendEvent bzfsAPI.h |
| 19:05.09 | zuii | a new directChatMessage and broadcastChatMessage |
| 19:05.59 | zuii | and replace calls in the sendMessage function with these renamed functions |
| 19:06.47 | zuii | this is how i solved to prevent message being sent to a player, without blokking message to a whole team... |
| 19:07.06 | Patlabor | sure, that's what we talked about last time, that all sounds fine |
| 19:07.08 | zuii | however admins would still got the mesage |
| 19:07.25 | zuii | but they have the right to mute |
| 19:07.35 | blast007 | sometimes |
| 19:18.25 | *** join/#bzflag infobot (ibot@rikers.org) |
| 19:18.25 | *** topic/#bzflag is http://BZFlag.org || https://www.ohloh.net/p/bzflag || http://wiki.BZFlag.org/Getting_Help || Channel Logs: http://ibot.rikers.org/%23bzflag/ || 2.4.2 Current version http://goo.gl/PI9KFD |
| 19:18.25 | *** mode/#bzflag [+v infobot] by ChanServ |
| 19:42.12 | *** join/#bzflag infobot (ibot@rikers.org) |
| 19:42.12 | *** topic/#bzflag is http://BZFlag.org || https://www.ohloh.net/p/bzflag || http://wiki.BZFlag.org/Getting_Help || Channel Logs: http://ibot.rikers.org/%23bzflag/ || 2.4.2 Current version http://goo.gl/PI9KFD |
| 19:42.12 | *** mode/#bzflag [+v infobot] by ChanServ |
| 19:56.08 | Constitution | thanks BulletCatcher |
| 20:02.27 | *** join/#bzflag death__ (~I_Died_On@71.226.67.5) |
| 20:08.33 | *** join/#bzflag TimRiker (~TimRiker@bzflag/projectlead/TimRiker) |
| 20:08.33 | *** mode/#bzflag [+o TimRiker] by ChanServ |
| 20:24.59 | *** join/#bzflag detrimental (~james@thief-pool-117-217.mncable.net) |
| 21:57.45 | *** join/#bzflag Constitution (~josh@bzflag/developer/Constitution) |