RITlug / tasks

Real-life issue tracker for tasks, goals, and objectives for RITlug
https://ritlug.com
Creative Commons Attribution Share Alike 4.0 International
6 stars 1 forks source link

Replace slack bridge bot #48

Closed axk4545 closed 6 years ago

axk4545 commented 6 years ago

In a recent update to the bot code that relays messages between IRC and slack, the behavior of the bot changed so that when viewing messages on Slack there is no indication of the IRC side user that sent the message. It appears this may only be an issue when using Slack on mobile.

This is somewhat of an annoyance and it would be nice to remedy it.

axk4545 commented 6 years ago

tagging @Tjzabel since I think he mentioned experiencing it as well.

jwflory commented 6 years ago

Marking this as needs info. Not sure if the issue is with the bot, Slack, or something else. The bot itself hasn't changed nor has it been updated since I began running it. It may be that I need to run a git pull to update it.

@axk4545 Could you please attach a screenshot of what you mean? I haven't actually noticed this behavior myself.

axk4545 commented 6 years ago

See attached for screenshot

On Sun, Jun 3, 2018, 12:45 PM Justin W. Flory notifications@github.com wrote:

Marking this as needs info. Not sure if the issue is with the bot, Slack, or something else. The bot itself hasn't changed nor has it been updated since I began running it. It may be that I need to run a git pull to update it.

@axk4545 https://github.com/axk4545 Could you please attach a screenshot of what you mean? I haven't actually noticed this behavior myself.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RITlug/tasks/issues/48#issuecomment-394178760, or mute the thread https://github.com/notifications/unsubscribe-auth/ADUyLPbUHYzM50rs1QhNoXD-U_Oegujkks5t5CCvgaJpZM4UYKHj .

jwflory commented 6 years ago

@axk4545 Attachments don't come through via email. Could you drag and drop it into the issue?

ct-martin commented 6 years ago

Update: This appears to be a change on the Slack client side, we will keep an eye on it

ct-martin commented 6 years ago

The change in Slack appears to have been reverted, I leave it open to discussion on whether we still want to look into other options or whether we want to close the issue

jwflory commented 6 years ago

@ct-martin I would make an assumption there was an untested API change and it is probably a fixed bug.

Given the lack of other options, I think it's best to close this as resolved if the original issue with prefixes / names are fixed.