WeSearch
Hub / Aggregator with comments
AGGREGATOR · DISCUSSION

Every headline, a thread.

Most news aggregators are read-only. WeSearch is read-and-respond — every story across 700+ sources has its own anonymous threaded discussion built in, with GIF support, comment likes, and a live pulse showing what the room is talking about.

You can think of WeSearch as Hacker News meets a real RSS reader meets a community Discord, with the surface of an editorial press magazine. Every news headline we pull becomes a stable landing page at /s/<slug> with its own threaded discussion. Comments persist across the hub feed and the story page, so jumping in at any point lands you in the same conversation.

What the discussion layer includes

The Pulse tab

The Pulse tab surfaces the live community signal: 24-hour reaction totals, comment totals across the platform, hot stories, and an emoji-economy bar showing what people are feeling. Pulse is also where "Latest chatter" lives — a real-time stream of comments as they post.

How threading works under the hood

Each comment row stores an optional parent_id pointing to the comment it's replying to. Replies render indented up to depth-3 (deeper threads still work but flatten visually so the thread doesn't slide off the screen). Likes and replies are aggregated and surfaced in the comment header — no separate notification count to manage.

Discussion that doesn't poison itself

The combination of anonymous handles + no follower counts + no algorithm reward creates a discussion environment where the loudest takes don't win by default. People reply to specific points, GIFs serve as humor not aggression, and the thread tends to stabilize on substance. We moderate when something crosses a hard line, but most threads don't need it.