EarShots.dev
Open navigation

Docs

Connect sources

A source is one place to listen with one term. Add a few narrow sources rather than one broad one, and you will mute less later.

What each channel expects

GitHub

You give
owner/repo, or a term to search across public repositories
You get
Issues, pull request discussion, and comments where people hit something real in code

Usually the highest signal source. Bots and your own team's posts are filtered out.

X

You give
The term people use for your product
You get
Posts from users, not just your own account

Your own handle and your team's handles are treated as official and left out of the user feed.

LinkedIn

You give
A company or product term
You get
Public posts, mostly buying signals and team announcements

LinkedIn is the most restrictive platform. Coverage is thinner than the others.

Open web

You give
A term, optionally scoped to a site
You get
Dev.to, Hashnode, personal blogs, changelogs, and forum threads

Backed by a crawler so you are not limited to platforms with an API.

Choosing a term

  • Use the name developers type: the package, the CLI, the service.
  • Skip generic words that also mean something else. You will drown in unrelated posts.
  • To watch competitors, use the dedicated Competitor Signal area instead of a source. See the Competitor Signal guide.

EarShots also filters what it finds. Posts from your own accounts, reposts of your announcements, and off-topic matches on a common word are dropped before anything reaches your feed.

Handles on X and LinkedIn

Each X and LinkedIn channel takes two lists. Handles to always listen for: posts from those accounts, or that tag them, are picked up even when they do not name your product. Handles to ignore: posts from those accounts never enter your workspace, which is where your own team accounts go. If a handle is on both lists, it is ignored.

Use @handles or profile links, separated by commas. Up to 25 per list.

Refresh and manual pulls

Sources refresh automatically on a schedule set by your plan. Each connected source card shows its last refresh and a Pull now button when you want fresh results immediately. Sync on Insights pulls every source and then sorts everything new.

If a source starts failing, EarShots tries to repair it before you notice: it retries, simplifies the query, tests the fix with a real pull, and saves the working version. A source only shows an error once repair has failed.