| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Support sending messages | Trygve Aaberge | 2024-02-18 | 1 | -0/+8 |
| | | |||||
| * | Reload conversations on reconnect | Trygve Aaberge | 2024-02-18 | 1 | -12/+22 |
| | | |||||
| * | Add unread buffers to hotlist on connect | Trygve Aaberge | 2024-02-18 | 1 | -3/+3 |
| | | |||||
| * | Mark as read when switching away from buffer | Trygve Aaberge | 2024-02-18 | 1 | -0/+15 |
| | | |||||
| * | Correctly tag unread messages from history | Trygve Aaberge | 2024-02-18 | 1 | -1/+5 |
| | | | | | | | Now notify tags are set based on last_read so both read and unread messages gets the correct tags irregardless if they come from history or websocket. | ||||
| * | If a message has a user, use that even though it's a bot_message | Trygve Aaberge | 2024-02-18 | 1 | -1/+5 |
| | | | | | | | | | | Messages from Slackbot apparently have both a user and a bot_id, and sometimes have the subtype bot_message, other times not. However, the bot_id is B01 which gives bot_not_found when trying to look it up. I see that the web client shows it with the user profile, and doesn't show the message as a bot message, so do that here as well to match it and avoid the invalid bot_id. | ||||
| * | Fetch thread replies when receiving thread message | Trygve Aaberge | 2024-02-18 | 1 | -3/+1 |
| | | | | | | | This is done so we can know if we should include a message hash when completing thread hashes, and it also has the benefit of eliminating the loading time when opening thread buffers. | ||||
| * | Support thread buffers | Trygve Aaberge | 2024-02-18 | 1 | -0/+87 |
 |
index : wee-slack | |
| A WeeChat script for Slack.com | Matěj Cepl <mcepl@cepl.eu> |
| aboutsummaryrefslogtreecommitdiffstats |