Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Jeff – Jev-compatible 0.8B decision models, trained at home, ~30 ms (github.com/firelex)
    54comments
  2. Pirating the Pirates (mubi.com)
    198comments
  3. 12,000-year-old Göbeklitepe burials explain scattered bones (archaeologymag.com)
    10comments
  4. MicroLLM Lab – Try 7 tiny LLM's in the browser (stateofutopia.com)
    45comments
  5. World Labs Is Joining AMD (worldlabs.ai)
    47comments
  6. Scientists solve 1840s space weather mystery (arstechnica.com)
    23comments
  7. Hijacking the PS5's RTMP stream (yashgarg.dev)
    55comments
  8. Flock Wants the Most Detailed Map of Its Surveillance Cameras Taken Offline (theintercept.com)
    46comments
  9. Kids turned low-traffic NPR Spotify comments into a secret group chat (thisamericanlife.org)
    150comments
  10. Parley: Federated, decentralised chat that speaks plain IRC (mills.io)
    155comments
  11. Best of British Design (best-of-british-design.vercel.app)
    27comments
  12. It's Time to Investigate the AI Labs (calnewport.com)
    58comments
  13. Joseph Szabo’s pictures of American adolescents (newyorker.com)
    34comments
  14. What reversing, modernising old games tells us about the economic impact of AI (isfine.org)
    8comments
  15. Sonnet 5.5 (anthropic.com)
    347comments
  16. 3D necroprinting: Leveraging biotic material as the nozzle for 3D printing (science.org)
    2comments
  17. Cf: The Agentic CLI for the Cloudflare API (cloudflare.com)
    43comments
  18. Nvidia wants to put a watchdog chip next to every AI agent (cnbc.com)
    128comments
  19. First Steps of the PLC Organization – Independent Public Ledger of Credentials (plcred.org)
    18comments
  20. Does Reddit have an astroturfing problem? What the data suggests (petervijeh.com)
    101comments
  21. Show HN: Destroy Any Website with Stickman (spritefusion.com)
    26comments
  22. Launch HN: Vespper (YC F24) – SOTA Docx MCP (vespper.com)
    8comments
  23. What heraldry and Japanese mon can teach about visual-identity generators (benovermyer.com)
    20comments
  24. Updated Google Maps shows destruction of the city of Rafah (twitter.com/aliabunimah)
    39comments
  25. Who wrote Elizabeth I's most scathing letters? (smithsonianmag.com)
    18comments
  26. MongoDB CEO resigns to join Meta (reuters.com)
    254comments
  27. When did Google get so weird? (sancho.bearblog.dev)
    1022comments
  28. Pacing the Frontier is not the actual goal for AI labs (lesswrong.com)
    67comments
  29. GrapheneOS – When an app is slow (wirelessmoves.com)
    41comments
  30. ESP32S3 cluster running 1.58-bit (BitNet) Language model (github.com/low-zi-hong)
    —discuss

Show HN: Twitter Viewer – View Profiles,Search Tweets,Download Videos (No Login)

2 pointsby 8mo agotwitterwebviewer.com
6 comments
Hey HN! Happy New Year! I built Twitter Viewer because Twitter now requires login to view public content, which creates unnecessary barriers for researchers, journalists, and casual users.

What it does: View any public Twitter profile & tweets (no account needed) Search tweets by keywords Download Twitter videos in MP4 format 100% anonymous (no tracking, no data collection)

Tech Stack: Next.js 14 (App Router) for SSR and fast loading Tailwind CSS for styling Hosted on Vercel with Edge runtime Twitter API integration (via proxy)

Why I built this: Since Twitter changed its policy in 2023, you can't even view a single tweet without creating an account. This is frustrating for people who just want to quickly check a profile or share a link.

The tool has been in private beta for a month with positive feedback. I'm launching publicly today and would love your thoughts!

Live: https://twitterwebviewer.com

Happy to answer any questions about the implementation or features!

8mo agoHN ↗

Does your server actually have all the tweets and an index? Or when you search does the query go to Twitter’s api?

8mo agoHN ↗

Good question! The queries go directly to Twitter's API (via a third-party provider).

  No local index or stored tweets—everything is fetched in real-time when you search or view a profile. We do cache responses temporarily to avoid hitting rate limits, but the cache expires quickly.

  The benefit of this approach:
  • Always up-to-date (real-time data)
  • No storage costs or maintenance
  • Simpler architecture

  The downside:
  • Dependent on API availability
  • Rate limit considerations

  I considered building a local index but decided against it for now—wanted to ship fast and keep it simple. Might revisit if the API approach becomes problematic.
8mo agoHN ↗

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!