Skip to content
GitShowcase Forum
SearchAsk a question

Contact the GitShowcase Forum team

There are two addresses for the forum, one for general questions and removal requests and one for security reports. The forum is a section of GitShowcase at gitshowcase.com/forum/, and the two staff moderators, Maren Castillo and Nils Haugen, read what comes in.

Forum questions and removal requests

Write to editorial@gitshowcase.com for anything about the forum itself: a question about how it works, a post that needs a correction, a request to remove or redact something, a copyright notice or an accessibility problem. Start your subject line with "Forum" so it is easy to sort.

What to include

  • The full web address of the thread or post you mean. Because the forum keeps only a one way hash of your email address, the address of your post is how we find your content.
  • What you want to happen: a correction, a removal, a redaction of personal details, or an answer.
  • A source, for a factual correction. Link the vendor documentation, changelog or specification that shows the current behavior, and say which version it applies to. That lets us fix the answer and add a visible note rather than debate it.
  • Your display name on the forum, if the request is about your own posts.

Removal requests

If a post contains something it should not, such as a key, a token, a connection string, customer data or a private person's details, tell us the address of the post and what needs to go. You do not need to explain at length. If the post contains a live credential, rotate it first, then write to us. Rotating takes effect immediately; our removal does not undo a copy that has already been seen. Leaked keys are covered in the guidelines.

Removal means the post is hidden from the site. A hidden record can remain in the database and in backups, as the privacy page describes.

Send these to the same address with the subject "Copyright notice". Include the address of the material, a description of the work, your contact details and a statement that you believe in good faith that the use is not authorized.

Security reports

Write to security@gitshowcase.com if you find a security problem in the forum software or the way it is served: a way to read another member's data, post as someone else, bypass the sign in, or inject script into a page. Please include:

  • the page address and what you did, step by step;
  • what you expected and what happened;
  • your browser and any request or response details that help us reproduce it.

Please do not test against other members' accounts, do not access or keep data that is not yours, and do not publish details before we have had a chance to look. Do not include real credentials or customer data in the report. If you have found an exposed key belonging to someone else, say where it is without pasting the value.

Security reports about third party products discussed in threads should go to those vendors. We can help remove a post that exposes a secret, but we cannot fix someone else's service.

What we cannot do

The forum is a Q&A space. We cannot debug your private repository by email, review code that is not posted in a thread, recover a lost account password (sign in links are sent to the email address you used), or give legal advice on licensing. For support with a specific vendor product, use that vendor's support channel.

Response times

We read every message, but we do not promise a response time. Reports that expose credentials, personal information or security problems are looked at first.

Press and research

You may quote public threads with a link back to the thread. We do not share members' email addresses, and because only a hash is stored, we could not read them back anyway.

Accessibility

If a page is hard to use with a screen reader or a keyboard, tell us which page and what happened. We treat it as a bug.

Updated