wee-slack: Private channel buffer is empty

Apparently Slack now has private channels that aren’t groups but don’t work with the channels API anyway. These are listed among "channels": […] and have "is_private": true.

I tried to fix this myself: https://github.com/liskin/wee-slack/commits/fix-private-channels Unfortunately the conversations.mark API method isn’t documented and doesn’t work with the legacy token, only with a token stolen from the web client. There’s a twitter thread with @SlackHQ about it: https://twitter.com/Saythlin/status/1046131572808863745 without a solution at the time of writing.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 4
  • Comments: 23 (18 by maintainers)

Commits related to this issue

Most upvoted comments

@jcross: Yeah, I merged it now.

So now, these channels should work except for the limitations documented in the readme (the same as the ones I wrote in my last comment above).

I have fixed some of this in https://github.com/trygveaa/wee-slack/tree/private-channels, but it’s not complete yet.

The things which are not working yet:

  • thread_messages_in_channel is only working for messages which arrive after the channel history has loaded.
  • If background_load_all_history is false, a private channel will not show as unread in the hotlist when wee-slack loads, even if there are unread messages. Messages which arrive after wee-slack has loaded will still mark the channel as unread in the hotlist.
  • Which messages that has been read is not synced to Slack.

The last issue is not possible to fix without API changes from Slack. I’m not sure if the second issue is possible to fix without API changes either.

There may be more issues, but these are the ones I’m aware of. Note that these issues only exist for private channels (i.e. a channel which was public, but has been converted to private). Other channels should still work fine without these issues.

That creates a group for me, not what @liskin describes.