Wispr Flow: Dictation That Works EverywhereStop typing. Start speaking. 4x faster.
BackSpin - Open AI Attention Exchanges
Devs earn during AI waits. Advertisers reach them right then
16 followers
Devs earn during AI waits. Advertisers reach them right then
16 followers
Most dev-tool ads are one-sided: the tool shows you ads, you get nothing. BackSpin flips that into a two-sided exchange, developers opt in and earn a share of revenue for the attention they give during AI wait states. It's private by design, never reading your code, prompts, or AI responses, and detecting AI activity from content-free signals only. It works everywhere you do: editors, CLIs, MCP hosts, and the browser. And every integration is opt-in and reversible, uninstalling cleanly.
The two-sided exchange idea is genuinely interesting and I like that it's opt-in and reversible. One thing I'd love to see is a small earnings dashboard, even a simple weekly email summary showing roughly how much attention time translated into revenue share. It would make the value feel tangible and probably encourage more developers to keep the integration enabled instead of forgetting it's running in the background.
Thanks! Glad you like the opt-in design. @halimezcalvran
For the stats, we do have a detailed breakdown of your attention seconds and earnings available right now in the developer dashboard at usebackspin.com/me :)
That said, a weekly email is a great idea to keep the value tangible without you needing to log in and check. We will look into setting up a weekly digest.
Do you prefer email, or would you rather see a quick stats printout directly in your CLI / VS Code / browser extensions?
How do you actually detect AI activity without looking at prompts or responses, and what's stopping a clever extension from faking those signals to grab more revenue?
@pekkavfolufeb8 Good question. We never look at prompts or responses at all, we just watch the shape of activity around the wait: things like task start/end, keystroke and focus timing, whether the card was actually visible on screen. That feeds a public scoring formula (open on our open-algorithm GitHub repo) that weighs activity, focus, and trust, then subtracts a fraud risk score.
The scoring math is open. Our fraud detector is not, on purpose, since publishing the exact thresholds would just hand out a cheat sheet. You can find out more in our Github pages here.
finally something that pays me back for the seconds I lose to loading spinners. love that it works without peeking at my code
@burhanmpux Really glad it landed that way, that's exactly the point we built it around. Those wait seconds were just dead time before, so we figured they might as well pay you something instead of nothing.
And yeah, the code/prompt privacy part wasn't a nice-to-have for us, it's a hard line: BackSpin only ever sees timing and focus signals, never the actual content of what you're working on. :)