summaryrefslogtreecommitdiffstats
path: root/backgammon
diff options
context:
space:
mode:
authordholland <dholland@NetBSD.org>2014-03-29 20:32:04 +0000
committerdholland <dholland@NetBSD.org>2014-03-29 20:32:04 +0000
commit6160abf7585bddb853ea3abb465bbb7cfff1ddb2 (patch)
tree93bd4a0ecf9840d7c4ec78c47e7e46b55fa142ef /backgammon
parent3a8de0fa374d25dd9b8c96c15a8ff130376b2e0a (diff)
downloadbsdgames-darwin-6160abf7585bddb853ea3abb465bbb7cfff1ddb2.tar.gz
bsdgames-darwin-6160abf7585bddb853ea3abb465bbb7cfff1ddb2.tar.zst
bsdgames-darwin-6160abf7585bddb853ea3abb465bbb7cfff1ddb2.zip
Rip out the code that broadcasts talk requests to the local
hunt-players mailing list. In this day and age it doesn't even begin to work: even if you were to have such a mailing list locally, sendmail wouldn't expand it for you, the addresses you got back wouldn't be talk-requestable addresses, talk requests don't cross NAT or firewalls safely, talk doesn't support ipv6, and nobody runs talkd anyway. It doesn't make sense to try to replace it with some other kind of notify scheme either; there might still be a multiuser machine somewhere with enough simultaneous users that broadcasting something akin to talk requests locally might make sense, and where a nontrivial number of the users actually play hunt, but probably not, and if so those users are likely to be better off using wall(1) anyway. Nowadays games will be set up by looking for people in chat or by emailing or texting friends. Theoretically someone could set up an internet hunt metaserver for finding hunt games, but that would be something entirely different anyway and I doubt there's demand.
Diffstat (limited to 'backgammon')
0 files changed, 0 insertions, 0 deletions