New site, portal login, bug bounty program

TL;DR: New site is live, portal login via password reset, paid bug bounty now open to members.

Hello, this is Charles. As you may have noticed, the previous guild website was retired and now redirects to https://theneontemple.com (the address of the previous-previous and current website). Please enjoy the new site and/or mourn the old at your leisure.

On the back end is a guild portal. There is a "Login" button on the upper right of the new site menu. You can also visit the back end directly at https://coterie.theneontemple.com. There you may betimes find private (unlisted on the public page) events or announcements, along with the public ones. You'll also find your profile, password, payment history, and an annual dues statement for employer reimbursement or taxes.

Right, well that's exciting, but Charles, how do I get in? Well I'll tell you. You use the "reset password" link on the login screen. Hopefully that works! But if it doesn't, either we had a different email for you, or it went to spam, or someone fat-fingered the code, but probably not that. If all else fails, DM me and I will fix the email on file for you.

The backend portal is "coterie." There is now a joint bug bounty program for NT members only, under the auspices of The Neon Temple and Industrious Kraken. Why joint? The hosted assets at the aforementioned URLs belong to the guild. The coterie repo is supported by Industrious Kraken, and IK also writes the bug bounty cheques. Therefore joint. While you are a member in good standing, you are invited to participate in the paid responsible disclosure program, as described: https://github.com/IndustriousKraken/coterie/security.

As mentioned in the announcement at the top of the new site, you can also clone and host both coterie and theneontemple.com for testing purposes: https://github.com/IndustriousKraken/coterie and https://github.com/IndustriousKraken/theneontemple.com.

If you wish to participate and test on production: Please carefully read and ensure you are enrolled (per the instructions on the security page) and have test credentials before testing on production infrastructure. Unenrolled testing against production is out of scope and unauthorized. Disclosures go through the github security page (green "report a vulnerability" button).