You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would perhaps be nice to be able to infer the timezone for someone in a channel if the given name was not registered via a !tz foo = Bar/Baz. In IRC this can potentially be done inferring the location from the host IP of the nick. How we request this information from the agent is something we need to consider from a design perspective in core halibot though, so this is probably not possible without some plumbing.
Using pygeoip would perhaps be useful. It will give a well-formed timezone when given an IP address.
The text was updated successfully, but these errors were encountered:
I like this idea, though it should probably make it clear that it is based on geoip rather than manually set. (Esp. for bouncer users who aren't in the same tz as the VPS, e.g. me)
As for what is needed from core, that's a good point. Right now, the core has no "user querying" functions, but that should probably be implemented at some point. We should consider some kind of "whois" protocol support for agents to implement a base set of information bits.
It would perhaps be nice to be able to infer the timezone for someone in a channel if the given name was not registered via a
!tz foo = Bar/Baz
. In IRC this can potentially be done inferring the location from the host IP of the nick. How we request this information from the agent is something we need to consider from a design perspective in core halibot though, so this is probably not possible without some plumbing.Using pygeoip would perhaps be useful. It will give a well-formed timezone when given an IP address.
The text was updated successfully, but these errors were encountered: