Slack Time Localization Bot
Detect temporal expressions in Slack messages (tomorrow at 5 pm) and translate them for readers in other timezones.
Who is this for?
Many organizations have people around the globe communicating via Slack.
That usually means a lot of different timezones.
So when people try to coordinate their activities a lot of time conversions have to happen when reading messages.
If you read "How about tomorrow at 5 pm?" you might need to do the following:
- Check the author's timezone.
- Check your own timezone (you usually know that already).
- Convert
"tomorrow at 5 pm"into your timezone.
This is cumbersome and prone to errors. Especially when dealing with summer/winter time. This bot aims to help people with that.
The bot can easily be self-hosted and does not need to be reachable from the internet due to Slack's socket mode.
How It Works
Currently, the implementation is centered around Meta's Duckling library. It can detect temporal expressions in various languages and extract a timestamp from it. Since Duckling needs to know the language of the text in advance the library lingua-py is used to detect the language. Big kudos to the authors of these libraries. Without them this bot could not have been developed in a feasible amount of time.
The Slack bot reads every message it has access to and uses Duckling to extract timestamps. For every possible reader of the message the bot then compares the timezone of the message author and the reader and translates the timestamp to the reader's timezone. Finally, the bot will post an ephemeral message below the message with the detected temporal expressions and the timestamps translated to the local timezone. That ephemeral message might look different for readers if they are not in the same timezone.
Quickstart
Create a Slack app with the following manifest:
display_information:
name: Time Localization
description: Detect temporal expressions in Slack messages ("tomorrow at 5 pm") and translate them for readers in other timezones.
background_color: "#240b24"
features:
app_home:
home_tab_enabled: false
messages_tab_enabled: true
messages_tab_read_only_enabled: false
bot_user:
display_name: Time Localization
always_online: true
oauth_config:
scopes:
bot:
- app_mentions:read
- channels:history
- chat:write
- groups:history
- groups:write
- im:history
- im:write
- mpim:history
- mpim:write
- users:read
- channels:read
- groups:read
- mpim:read
- im:read
settings:
event_subscriptions:
bot_events:
- app_mention
- channel_history_changed
- group_history_changed
- im_history_changed
- message.channels
- message.groups
- message.im
- message.mpim
interactivity:
is_enabled: true
org_deploy_enabled: false
socket_mode_enabled: true
token_rotation_enabled: false
Create and get the bot token (under "OAuth & Permissions") and app token (under "Basic Information") for your Slack app.
pip install slack-time-localization-bot
ℹ️ Currently only Linx x86_64 is supported
Finally you can run it with
export SLACK_BOT_TOKEN=xoxb-...
export SLACK_APP_TOKEN=xapp-...
export USER_CACHE_SIZE=500 # number of user profiles to cache in memory
export USER_CACHE_TTL=600 # number of seconds a user profile will be cached in memory
export PREFER_24h_INTERPRETATION=true # set to true if 5:00 usually means 5 in the morning and not late afternoon
export DEBUG=false # set to true to enable verbose logging including message contents
slack-time-localization-bot
You can now invite the bot to a conversation is slack and the bot will translate temporal expressions for every message.
Running Tests
Install poetry and run
poetry install
poetry run pytest ./tests
Metadata
Release files for slack-time-localization-bot 0.1.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| slack_time_localization_bot-0.1.12.tar.gz | 11.3 kB | Without provenance | Details for slack_time_localization_bot-0.1.12.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| slack_time_localization_bot-0.1.12-py3-none-any.whl | Python 3 | none | any | Details for slack_time_localization_bot-0.1.12-py3-none-any.whl |
Total release size: 23.3 kB
Release files / slack_time_localization_bot-0.1.12.tar.gz
| Download URL | slack_time_localization_bot-0.1.12.tar.gz |
|---|---|
| Size | 11.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e05f8d3b9b0fa62faf6f8cb058ebb1ed6826d3a3f7826d38db673440ee6b26ac
|
|
BLAKE2b-256 checksum How to use checksums |
fca6a3020171697b817f71948be44d7e2ceb2cf04e9b3e9caf3991b1ec983d91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Release files / slack_time_localization_bot-0.1.12-py3-none-any.whl
| Download URL | slack_time_localization_bot-0.1.12-py3-none-any.whl |
|---|---|
| Size | 12.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4a36a0e348115dc99e0aca03206ee7d73c5ec35c07b5d43d7f766c6d086d6cba
|
|
BLAKE2b-256 checksum How to use checksums |
1d51c11f920c48d7dbd6c468e03e4fc530b7e93a2a5c3a38275e4478b91655e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Security for slack-time-localization-bot 0.1.12
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.