Feed aggregator

I built this to solve a recurring problem in multi-repo, multi-environment setups: it’s surprisingly hard to answer “what is actually running where?” without checking several systems. WatchTurm is an open-source release visibility layer. It aggregates metadata from sources like GitHub, Jira and CI (e.g. TeamCity), generates a structured snapshot of environment state, and surfaces it in a single control view.

It doesn’t replace CI/CD or manage deployments. It sits above automation and focuses purely on visibility: - what version runs in each environment - how environments differ - what changed between releases

I’m currently using it in my own daily work and would really appreciate technical feedback, especially from teams with multi-environment pipelines.

repo: https://github.com/WatchTurm/WatchTurm-control-room

Comments URL: https://news.ycombinator.com/item?id=47096201

Points: 1

# Comments: 0

Hey HN, just wanted to share a fun, vibe-coded Friday night experiment: a little playground for writing cellular automata in a subset of Rust, which is then compiled into WSGL.

Since it lets you dynamically change parameters while the simulation is running via a TUI, it's easy to discover weird behaviors without remembering how you got there. If you press "s", it will save the complete history to a JSON file (a timeline of the parameters that were changed at given ticks), so you can replay it and regenerate the discovery.

You can pan/zoom, and while the main simulation window is in focus, the arrow keys can be used to update parameters (which are shown in the TUI).

Claude deserves all the credit and criticism for any technical elements of this project (beyond rough guidelines). I've just always wanted something like this, and it's a lot of fun to play with. Who needs video games these days.

Comments URL: https://news.ycombinator.com/item?id=47096186

Points: 1

# Comments: 0

Article URL: https://blog.cloudflare.com/code-mode-mcp/

Comments URL: https://news.ycombinator.com/item?id=47096180

Points: 1

# Comments: 0

Hi HN,

I got frustrated with the current landscape of 10-minute mail services. They are often full of ads, Google Analytics trackers, and clunky interfaces—completely defeating the purpose of a "privacy" tool.

I built MephistoMail as a clean, RAM-only frontend alternative. It uses the mail.tm/mail.gw APIs under the hood for actual inbox mapping but handles everything on the client side in volatile memory. If you close the tab, the session is gone. Zero logs are kept on our end.

Tech stack: React 18, Vite, Tailwind CSS, Lucide.

Would love to hear your thoughts, roasts, and suggestions!

Demo: https://mephistomail.site Repo: https://github.com/jokallame350-lang/temp-mailmephisto

Comments URL: https://news.ycombinator.com/item?id=47096177

Points: 1

# Comments: 0

Article URL: https://www.csun.edu/~dgw61315/thetwothings.html#The%20Story%20of%20the%20Two%20Things

Comments URL: https://news.ycombinator.com/item?id=47096174

Points: 2

# Comments: 0

Hi HN,

I got frustrated with the current landscape of 10-minute mail services. They are often full of ads, Google Analytics trackers, and clunky interfaces--completely defeating the purpose of a "privacy" tool.

I built MephistoMail as a clean, RAM-only frontend alternative. It uses the mail.tm/mail.gw APIs under the hood for actual inbox mapping but handles everything on the client side in volatile memory. If you close the tab, the session is gone. Zero logs are kept on our end.

Tech stack: React 18, Vite, Tailwind CSS, Lucide.

Would love to hear your thoughts, roasts, and suggestions!

Demo: https://mephistomail.site Repo: https://github.com/jokallame350-lang/temp-mailmephisto

Comments URL: https://news.ycombinator.com/item?id=47096170

Points: 1

# Comments: 0

Article URL: https://gamedate.org/

Comments URL: https://news.ycombinator.com/item?id=47096167

Points: 1

# Comments: 0

I’ve been working on real time voice agents and put together a write up of what I’ve learned about the full stack including WebRTC media transport, streaming STT, incremental LLM inference, and TTS, along with where latency actually accumulates.

The post focuses on the architectural flow and practical tradeoffs involved in keeping interactions truly real time.

Curious how others are designing and optimizing voice systems.

https://gokuljs.com/blogs/real-time-voice-agent-infrastructure

Comments URL: https://news.ycombinator.com/item?id=47096142

Points: 1

# Comments: 0

Hi HN,

I built Agent Passport, an open-source identity verification layer for AI agents. Think "Sign in with Google, but for Agents."

The problem: AI agents are everywhere now (OpenClaw has 180K+ GitHub stars, Moltbook had 2.3M agent accounts), but there's no standard way for agents to prove their identity. Malicious agents can impersonate others, and skill/plugin marketplaces have no auth layer. Cisco's security team already found data exfiltration in third-party agent skills.

Agent Passport solves this with: - Ed25519 challenge-response authentication (private keys never leave the agent) - JWT identity tokens (60-min TTL, revocable) - Risk engine that scores agents 0-100 (allow/throttle/block) - One-line verification for apps: `const result = await passport.verify(token)`

It's fully open source (MIT), runs on free tiers ($0/month), and has a published npm SDK.

GitHub: https://github.com/zerobase-labs/agent-passport Docs: https://github.com/zerobase-labs/agent-passport/blob/main/do... Live demo: https://agent-passport.vercel.app

Built this because I kept seeing the same security gap in every agent platform. Happy to answer questions about the architecture or the agent identity problem in general.

Comments URL: https://news.ycombinator.com/item?id=47096131

Points: 1

# Comments: 0

Article URL: https://crates.io/crates/hn-stories

Comments URL: https://news.ycombinator.com/item?id=47096129

Points: 1

# Comments: 0

Article URL: https://www.theguardian.com/technology/2026/feb/19/ebay-buys-depop-from-etsy

Comments URL: https://news.ycombinator.com/item?id=47096100

Points: 1

# Comments: 0

Article URL: https://ericbrookfield.com/2026/02/20/i-let-claude-read-my-email/

Comments URL: https://news.ycombinator.com/item?id=47096083

Points: 2

# Comments: 0

Article URL: https://www.joanwestenberg.com/the-unbearable-weight-of-cruft/

Comments URL: https://news.ycombinator.com/item?id=47096078

Points: 1

# Comments: 0

Article URL: https://onlinelibrary.wiley.com/doi/10.1002/sres.2974

Comments URL: https://news.ycombinator.com/item?id=47096074

Points: 1

# Comments: 0

I wanted a typed client for existing REST endpoints without adopting tRPC's architecture or maintaining OpenAPI schemas. Most solutions either replace your routing layer or add a build step. This just wires TypeScript types to your existing routes.

You describe your routes once with a lightweight helper, then get a fully typed fetch wrapper. Params, query, body, and output are all inferred. Wrong shapes are compile errors. Zero dependencies, zero runtime magic.

``` // before const user = await fetch(`/users/${id}`).then(r => r.json()) // any

// after const user = await api.getUser({ params: { id } }) // User ```

Works with any framework (Express, Hono, Next.js, etc). Optional Zod integration if you want runtime validation from the same source of truth.

Comments URL: https://news.ycombinator.com/item?id=47096063

Points: 1

# Comments: 0

Article URL: https://www.mbgsec.com/posts/2026-02-19-agent-repo-compromised-by-agent-to-install-an-agent/

Comments URL: https://news.ycombinator.com/item?id=47096038

Points: 2

# Comments: 0

Article URL: https://xkcd.com/632/

Comments URL: https://news.ycombinator.com/item?id=47095750

Points: 1

# Comments: 0

Article URL: https://www.businessinsider.com/tiktoker-khaby-lame-975-million-deal-riding-on-falling-stock-2026-2

Comments URL: https://news.ycombinator.com/item?id=47095714

Points: 1

# Comments: 0

Article URL: https://www.noemamag.com/the-quest-for-clean-cargo/

Comments URL: https://news.ycombinator.com/item?id=47095708

Points: 1

# Comments: 0