I Built a Twitter Viewer After Getting Locked Out One Too Many Times
The Frustrating Turning Point
I clicked a Twitter link to fact-check a quote, only to hit the login wall—again.
I don’t want to create another social media account. I just want to view a single tweet.
Twitter’s forced login requirement (introduced in 2023) broke the open web. So I built Twitter Viewer: browse any profile, search tweets, and download videos—no account needed.
https://twitterwebviewer.com
Built with Next.js 14 + Vercel Edge. 100% anonymous (your IP never touches Twitter’s servers). Development time: just 3 weeks.
The Surprisingly Strong Numbers
30 days post-launch:
• 704 users, with a 12-minute average session duration (that’s incredible for a simple tool)
• 67.6% engagement rate
• 58 users completed 857 searches = 14.8 searches per user
People aren’t just checking one tweet—they’re doing deep research！
Traffic breakdown: 36% social, 35% direct (hello, returning users!), 26% search. Zero marketing spend.
Tough Technical Hurdles I Overcame
Twitter’s rate limits: The Guest API caps at ~500 requests/hour. With 100+ users, that would crash the tool instantly. Solution: Redis caching + request deduplication = 85% cache hit rate.
Video downloads: Twitter doesn’t provide direct MP4 URLs—instead, it serves m3u8 streams with dynamic tokens. I had to reverse-engineer their manifest parsing logic to make this work.
Vercel bill blowout: I tried hosting videos directly, which led to a $200 bill in just 3 days. Now we proxy direct links instead—problem solved.
The Monetization Dilemma (Need Your Help!)
The tool is 100% free right now, but the data shows users find real value:
• 12-minute average sessions
• 14+ searches per power user
Options on the table:
• A) Freemium: $5/month for unlimited searches + API access
• B) B2B: $20/month for team monitoring & analytics
• C) Open Source: Host on GitHub and rely on GitHub Sponsors
Questions for the community:
- Is 704 MAU too small to start monetizing? Or should I strike while engagement is high?
- Should I open-source it? (Worried about clones, but transparency builds trust)
- What features would you actually pay for?
- Am I overthinking Twitter’s Terms of Service? (We only access public data, no authentication required)
Try It & Be Honest—No Sugarcoating
https://twitterwebviewer.com
Tell me:
• Why this tool will fail
• How you’d monetize it
• What key features are missing
• Any potential legal red flags
I need reality checks, not empty validation.
Happy to share technical deep dives (video API workarounds, caching strategies) if anyone’s interested!
Update: I've officially created a product page for this tool to track our growth journey! Check it out here: https://www.indiehackers.com/product/twitter-web-viewer
In just 3 weeks, the site has grown to 2.2K active users purely through organic discovery and word-of-mouth. It turns out, there's a massive demand for a reliable Twitter search without account tool that actually works in 2026.
My short-term mission is to scale this to 1,000 DAU (Daily Active Users)!
Update (Jan 24): We just hit 1,500+ users!
It seems the need for a stable Nitter alternative is bigger than I thought. Since posting this, I've optimized the Redis caching strategy further, bringing the cache hit rate to ~90%.
Quick question for the community: For those building anonymous social media viewers, how do you handle the 'mobile back button' UX issues with Next.js App Router? I'm debating between intercepting routes or just keeping it simple. Any thoughts?
Just keeping this thread from sinking. Would love to hear from you all!
Re：On open-sourcing: I’m leaning toward it, but with a twist—release the core (caching, basic search) as open source, but keep the video parsing and advanced API logic proprietary. That way, I keep a moat but build trust. Would that balance work for you all? Or would you prefer full transparency even if it means more clones?
Want to share a quick behind-the-scenes pain point I didn’t mention in the post: When I first launched, Vercel’s bill wasn’t just $200—they actually flagged the account for “unusual bandwidth usage” (video hosting) and threatened to suspend it. That’s why we switched to proxy links—scary moment for a solo founder!