You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 20, 2022. It is now read-only.
I've highlighted an issue on the slackin repo that it will stop working because of a deprecated endpoint.
The solution seems to be, if we haven't already, to switch to slackin-extended which receives some-what more support.
The future of slackin and slackin-extended looks to be uncertain as slack has now stopped people from creating new legacy tokens, and with that, moving the ability to invite members via API to an enterprise-only feature on the new slack app tokens.
TL;DR: we should switch to slackin-extended and protect the old legacy API key with your life.
The text was updated successfully, but these errors were encountered:
So I'm wondering if this is still working or not because we still seem to keep getting new signups. The problem with the new Slack invite links that they recommend is that they expire every month and I'm not sure how to automate that.
I was considering using slack for another project when I uncovered this stuff, eventually gave up and went to discord.
I got as far as making a serverless puppeteer script which got the link. I can share that if you'd like. (not gonna post something like that publically)
I've highlighted an issue on the slackin repo that it will stop working because of a deprecated endpoint.
The solution seems to be, if we haven't already, to switch to slackin-extended which receives some-what more support.
The future of slackin and slackin-extended looks to be uncertain as slack has now stopped people from creating new legacy tokens, and with that, moving the ability to invite members via API to an enterprise-only feature on the new slack app tokens.
TL;DR: we should switch to slackin-extended and protect the old legacy API key with your life.
The text was updated successfully, but these errors were encountered: