On 01/08/2018 13:21, Andrey Kurilin wrote: > <snip> > > The second link from google search gives an opensource client written in > python https://github.com/raelgc/scudcloud . Also, there is something > which is written in golang. > > > complete lack of any console clients (ditto), > > > Again, google gives several ones as first results - > https://github.com/evanyeung/terminal-slack > https://github.com/erroneousboat/slack-term > <snip> Any unoffical slack client needs to use "Legacy Tokens"[1] > You're reading this because you're looking for info on legacy > custom integrations - an outdated way for teams to integrate with > Slack. These integrations lack newer features and they will be > deprecated and possibly removed in the future. *We do not recommend > their use.* Legacy tokens can go away (just like the XMPP and IRC gateway did) at any point, and we will be back in the same situation. 1 - https://api.slack.com/custom-integrations/legacy-tokens -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180801/73c01ee5/attachment.sig>