Add a link to chat.libretime.org in the docs

[Robbt]

This is in relation to the discussion on #148 - where libretime.slack.com was created and people can use it. I realized since that topic was closed it would make sense to make the slack site semi-official otherwise only the people who were on that topic will ever join it.

EDIT: We have moved to Mattermost on https://chat.libretime.org/ with open signup. A link needs adding to the docs

[gusaus]

Cool - I think @ned-kelly will be able to hook this up?

[hairmare]

Can anyone who knows Slack clarify how we could add a sign-up/register link to the docs? Where would that link need to point to? All I can find is some docs about being allowed into a new Slack workspace because you sign up with a company email address and Slack matching the domain name parts to a workspace.

[ned-kelly]

@hairmare - Send me a PM on Slack and I'll help you hook it up, we need to add a DNS record for https://github.com/outsideris/slack-invite-automation which I'll setup tonight.

[ned-kelly]

@hairmare - Just an update, you can add: https://libretime-slack.herokuapp.com/ to the actual Libretime docs/homepage like you said in the initial issue - Happy to add in DNS if you want (i.e. slack.libretime.org) if we want to remove the herokuapp.com and use our own domain. @Robbt also shot you a PM on slack about passwords etc

[Robbt]

So the landing page on #543 includes a link to Slack, if we end up merging that then we can close this. The only thing that we might want to coordinate is pointing the DNS but that's up to @ned-kelly & @hairmare to coordinate. It's probably fine to use herokuapp for now since if that service were to go down the invite would crash and I don't see any real benefit to setting up a DNS entry other than it hiding the fact that we are using heroku from people.

[hairmare]

I'll add the DNS changes, @ned-kelly can you let me know what is actually needed? I think it's worth it for consistency.

Is the app really safe to use? I'm seeing a lot of large communities manage slack invites manually and there must be some reason for this.

[Robbt]

I suspect that we might run into spambots at some point, but we could always reconsider this if we run into that problem. In my mind it's better to be open to new users since we are mainly keeping Slack focused entirely on informal conversation rather than using it for our decision making platform.

[gusaus]

I 'think' there might be a way for admins to approve the email signups. Would that help? Either way, we should be greeting anyone who joins... should be pretty easy to screen out the bots.

…

On Fri, Oct 12, 2018 at 1:11 PM Robb ***@***.***> wrote: I suspect that we might run into spambots at some point, but we could always reconsider this if we run into that problem. In my mind it's better to be open to new users since we are mainly keeping Slack focused entirely on informal conversation rather than using it for our decision making platform. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#538 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAG9TNATUV7xVwwubgm-W5935s7p6vjrks5ukPdugaJpZM4XMGjh> .

[hairmare]

I'm not afraid of bots as much as I'm concerned about bad actors. Bots should get screened by Slash themselves for the most part. Also, admitting additional users to the slack shouldn't be an additional burden to Administrators. The herokuapp the @ned-kelly published seems to solve all these problems so I'm basically waiting for some docs on how to set up the DNS entries needed. I'd also like to take some time to look into the actual code behind the herokup app.

[ned-kelly]

Hi guys - sorry for the delayed response - away from computer - in short it’s pretty unlikely that we will get spambots on slack due to the fact that you need to join via a one-time invite token that is sent to your email from the inviter that’s running on heroku... Re the code - it’s just a simple node app that does the work that’s running on heroku - it’s the project I linked earlier in our discussions. Re larger scale - these guys (comma ai) are using it - (I’m a member here also) https://comma.ai and they have over 5,000 members so it’s obviously doing the trick ok / really I doubt we will reach 5,000 slack members. Re the DNS ill jump on and get the records for you when I’m back on a computer - should be just a CNAME from memory.

On Sat, 13 Oct 2018 at 7:16 am, Lucas Bickel ***@***.***> wrote: I'm not afraid of bots as much as I'm concerned about bad actors. Bots should get screened by Slash themselves for the most part. Also, admitting additional users to the slack shouldn't be an additional burden to Administrators. The herokuapp the @ned-kelly <https://github.com/ned-kelly> published seems to solve all these problems so I'm basically waiting for some docs on how to set up the DNS entries needed. I'd also like to take some time to look into the actual code behind the herokup app. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#538 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQ1MRUjZ8ZPWoWewccd8Jw1WWuDDQI5Sks5ukQaPgaJpZM4XMGjh> .

-- Sent from Gmail Mobile

[paddatrapper]

Has there been any movement on this?

[Robbt]

Nope. I think we could simply add it to the README & the Docs page as we wait for the various finishing touches required for the new launch page. The invite app created by @ned-kelly still works.

[dmnktoe]

The Slack invite page doesn't work anymore—always get a Failed! token_revoked response.

[Robbt]

@dmnktoe Thanks for pointing this out. As I didn't set this up I'm not sure how to fix it. We have been considering alternatives to Slack as well. So perhaps now is a good time to give one of them a test run, or perhaps @ned-kelly can fix it.