Repository navigation
docs(readme): use one Discord invite - #15
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
AntelopeJS/dms must look credible and findable when Show HN traffic arrives on 10 Nov. The READMEs and the websites link different Discord invites, so the count of people joining from each place is split. This uses one permanent invite everywhere.
Summary
Replaces the invite code in these files with
g4pFt6eXqu:README.mdEvidence
After:
discord.gg/g4pFt6eXquin every file of this repository./api/v10/invites/g4pFt6eXqu) returnsexpires_at: nulland guild 801474433881210931 (AntelopeJS).Merge Danger
Door: two-way
Blast Radius: links