Clojurians Log v2

you can always generate a new invite link from within slack

https://join.slack.com/t/clojurians/shared_invite/zt-2ii77rlja-0j5QYwrcsfL8uYMyainBAA is one i just created, will last for 30 days

Thanks! Is there a more permanent link I can use?

i think that site was it, so sadly i'm not sure anymore

The URL is correct, but the underlying invite link must've expired. @seancorfield and maybe some other admins can fix it, I myself have no idea how to do it. In any case, that's the URL I'd share - it will be fixed. Just in case, all the other relevant URLs are gathered here: https://clojure.org/community/resources

The URL is timing out.

oh you can customize the link to not expire

the peek behind the curtain is that slack lets you generate invite URLs which we have that http://clojurians.net URL point to. But slack makes them expire after 200 or 400 invites are claimed through it

I see.

(sean is really good at this) but it’s a manual process to periodically check that link. And if it’s gone stale, create a new one and update DNS records.

https://join.slack.com/t/clojurians/shared_invite/zt-2ii77rlja-0j5QYwrcsfL8uYMyainBAA is a non-expiring link, for example

@nbtheduke It will still go "bad" after 400 invites.

Do you know when it has gone stale?

And is that why it's timing out?

oh dang, really? i didn't realize that

i’m not aware of an easy way to see the remaining claims on an invite link

@nbtheduke It's right at the top of the second screenshot. :)

i wish i knew how to read

@dpsutton The second pinned message in <#G050G0K5D|> documents the process. If you already have access to the admin email, maybe you can do it? I don't have access and the account has 2FA.

Thanks whoever got it working again!

HTTPS has never worked on http://clojurians.net -- only HTTP

@ericnormand We made no changes -- the current invite link is still valid behind http://clojurians.net (not https).

Note that the link on the community resources page is correct (HTTP) so if you clicked that, it would work, but if you typed into a browser, it probably wouldn't since the browser would try HTTPS.

Ah! That must be what's happening! Thanks @seancorfield