Launch and discoverability: demo GIF, social preview, awesome-lists and launch posts
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, go
Research direction
Start with the README and the existing screenshot at docs/assets/tui-form.png; the issue also calls out the project site, GitHub social preview settings, and awesome-list submission targets. The requested work includes recording a demo with charmbracelet/vhs, creating a social preview, updating site metadata, and promotion after issues #46, #47, and #49 are fixed. Done means the README has a demo GIF, the repo has a social preview, and at least two awesome-list PRs are submitted.
Written by the indexing model from the issue text.
Description
Why it matters
After 8 releases, the project has 0 stars and no discovery path. The engineering has outpaced the visibility. A recon tool is chosen in seconds from a README and a GIF.
Gaps
- No terminal demo GIF or asciinema recording. Only a static TUI screenshot (
docs/assets/tui-form.png) exists. - No GitHub social preview image (Settings → Social preview), and no
og:tags on the site. - Not listed in awesome-go, awesome-bugbounty-tools, awesome-hacking or awesome-pentest.
Suggested approach
- Record a 20-second demo with charmbracelet/vhs, using a
.tapefile committed to the repo and regenerated in CI. Show a simulate run plus the per-query accounting summary, and add it to the top of the README. - Create a 1280×640 social preview built around the "trust the result" message, and wire it into the repo settings and the site
og:image. - After fixing #46, #47 and #49:
- Post a "Show HN" and posts on r/netsec and r/golang. Lead with the honest positioning: "slower than puredns, but tells you when your results are lying".
- Submit PRs to the awesome lists.
- Add the GitHub topics
dns-bruteforce,reconnaissance,subdomain-takeover,osintandsecurity-tools.
Done when
The README has a demo GIF, the repo has a social preview, and at least 2 awesome-list PRs are submitted.
- Dominant language
- Go
- Stars
- 1
- Forks
- 1
- Avg merge
- 14d 9h
- Merged PRs (30d)
- 1
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TMHSDigital/subenum
-
documentation testing
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
TMHSDigital/subenum#103 ·
Maintainers usually reply within 1 day
-
area: release bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
TMHSDigital/subenum#102 ·
Maintainers usually reply within 1 day
-
community marketing priority: low
Difficulty 5/5 Over a week Newbie friendliness 35/100
TMHSDigital/subenum#132 ·
Maintainers usually reply within 1 day
-
feature priority: low
Difficulty 5/5 Over a week Newbie friendliness 35/100
TMHSDigital/subenum#131 ·
Maintainers usually reply within 1 day
-
documentation marketing priority: medium
Difficulty 5/5 Over a week Newbie friendliness 25/100
TMHSDigital/subenum#127 ·
Maintainers usually reply within 1 day
All issues in TMHSDigital/subenum
Similar issues
-
[submenu] nil issue on ubuntu 26.04Possibly taken @egoist claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
prime-radiant-inc/evener#3873 ·
Maintainers usually reply within 1 day
-
extract_llm_sweep / cache_aware_summarizer prefix ask 400s when thinking.budget_tokens exceeds PrefixAskMaxTokensPossibly taken @amiddavid claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
rossoctl/context-guru#405 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
router-for-me/CLIProxyAPI#6423 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days