| 00:01.23 | allejo | and I don't think it should be up to players to encourage other players to update their clients. if anything, that should be a plug-in that says, "hey you're running an older client. time to update" |
| 00:01.24 | blast007 | JeffM: yeah |
| 00:02.23 | kierra | I think yrs ago it was used by admins in gu....as win client seemed to point to cheat clients with some players |
| 00:02.39 | macsforme | I can probably live with the server sending the messages, although I thought the point of the design was to give someone a heads up that the info was shared, since it has some privacy implications |
| 00:02.44 | kierra | though that can be spoofed |
| 00:03.00 | kierra | agreed, const |
| 00:03.00 | blast007 | macsforme: no, it was a holdover from how it used it work when it wasn't a server command |
| 00:03.17 | kierra | privacy issue for me :) |
| 00:03.17 | blast007 | back in early versions, sending CLIENTQUERY to chat would make each client send that user their build string |
| 00:03.34 | blast007 | then later we added slash commands, iirc |
| 00:04.26 | blast007 | no |
| 00:04.35 | blast007 | clientquery is literally just the build string |
| 00:04.41 | *** mode/#bzflag [+o allejo] by ChanServ |
| 00:05.19 | allejo | i don't see how it's a privacy concern. you get: version of bzflag. what OS you're using. and what SDL version you're using |
| 00:05.44 | blast007 | you don't even necessarily get the specific OS you're using, just the OS family |
| 00:08.37 | blast007 | the list server uses the build string to track OS |
| 00:09.23 | blast007 | the client itself doesn't send the message. the server sends the message as the player. |
| 00:10.44 | allejo | send messages on behalf of players? no |
| 01:27.19 | *** join/#bzflag Zehra (~Zehra@unaffiliated/zehra) |
| 02:00.30 | *** join/#bzflag bertman (~bert@unaffiliated/bertman) |
| 02:37.27 | *** join/#bzflag KaadmY (~kaadmy@unaffiliated/kaadmy) |
| 02:38.27 | *** join/#bzflag Void7 (~Void7@2604:a880:1:20::1315:3001) |