Home

The article discusses the Temporal API, a new JavaScript standard that simplifies date and time manipulation. It provides an overview of the Temporal API's features, including its ability to handle time zones, calendars, and various date/time formats.

The article describes how a team of researchers successfully exploited vulnerabilities in McKinsey's AI platform, highlighting the importance of robust security measures for AI systems and the need for thorough testing and validation to prevent such breaches.

BitNet is an open-source project by Microsoft that aims to provide a scalable and efficient blockchain network for decentralized applications. The project explores novel consensus mechanisms and optimization techniques to address the performance and scalability challenges of traditional blockchain platforms.

The article explores the concept of the 'Dead Internet Theory,' which suggests that a significant portion of the internet's content is generated by artificial intelligence and bots, rather than real human users. The author examines the potential implications of this phenomenon on the way we perceive and interact with online information.

Previously: Google to buy Wiz for $32B - https://news.ycombinator.com/item?id=43398518 - March 2025 (845 comments)

I built Site Spy after missing a visa appointment slot because a government page changed and I didn’t notice for two weeks.

It watches webpages for changes and shows the result like a diff. The part I think HN might find interesting is that it can monitor a specific element on a page, not just the whole page, and it can expose changes as RSS feeds.

So instead of tracking an entire noisy page, you can watch just a price, a stock status, a headline, or a specific content block. When it changes, you can inspect the diff, browse the snapshot history, or follow the updates in an RSS reader.

It’s a Chrome/Firefox extension plus a web dashboard.

Main features:

- Element picker for tracking a specific part of a page

- Diff view plus full snapshot timeline

- RSS feeds per watch, per tag, or across all watches

- MCP server for Claude, Cursor, and other AI agents

- Browser push, Email, and Telegram notifications

Chrome: https://chromewebstore.google.com/detail/site-spy/jeapcpanag...

Firefox: https://addons.mozilla.org/en-GB/firefox/addon/site-spy/

Docs: https://docs.sitespy.app

I’d especially love feedback on two things:

- Is RSS actually a useful interface for this, or do most people just want direct alerts?

- Does element-level tracking feel meaningfully better than full-page monitoring?

The article explores the work of theoretical physicist Natalie Wolchover, who is investigating the possibility that space-time may be made of fractals, rather than strings. Wolchover's unconventional approach to understanding the fundamental nature of reality challenges the traditional string theory framework.

We are Bailey and Robbie and we are working on Klaus (https://klausai.com/): hosted OpenClaw that is secure and powerful out of the box.

Running OpenClaw requires setting up a cloud VM or local container (a pain) or giving OpenClaw root access to your machine (insecure). Many basic integrations (eg Slack, Google Workspace) require you to create your own OAuth app.

We make running OpenClaw simple by giving each user their own EC2 instance, preconfigured with keys for OpenRouter, AgentMail, and Orthogonal. And we have OAuth apps to make it easy to integrate with Slack and Google Workspace.

We are both HN readers (Bailey has been on here for ~10 years) and we know OpenClaw has serious security concerns. We do a lot to make our users’ instances more secure: we run on a private subnet, automatically update the OpenClaw version our users run, and because you’re on our VM by default the only keys you leak if you get hacked belong to us. Connecting your email is still a risk. The best defense I know of is Opus 4.6 for resilience to prompt injection. If you have a better solution, we’d love to hear it!

We learned a lot about infrastructure management in the past month. Kimi K2.5 and Mimimax M2.5 are extremely good at hallucinating new ways to break openclaw.json and otherwise wreaking havoc on an EC2 instance. The week after our launch we spent 20+ hours fixing broken machines by hand.

We wrote a ton of best practices on using OpenClaw on AWS Linux into our users’ AGENTS.md, got really good at un-bricking EC2 machines over SSM, added a command-and-control server to every instance to facilitate hotfixes and migrations, and set up a Klaus instance to answer FAQs on discord.

In addition to all of this, we built ClawBert, our AI SRE for hotfixing OpenClaw instances automatically: https://www.youtube.com/watch?v=v65F6VBXqKY. Clawbert is a Claude Code instance that runs whenever a health check fails or the user triggers it in the UI. It can read that user’s entries in our database and execute commands on the user’s instance. We expose a log of Clawbert’s runs to the user.

We know that setting up OpenClaw is easy for most HN readers, but I promise it is not for most people. Klaus has a long way to go, but it’s still very rewarding to see people who’ve never used Claude Code get their first taste of AI agents.

We charge $19/m for a t4g.small, $49/m for a t4g.medium, and $200/m for a t4g.xlarge and priority support. You get $15 in tokens and $20 in Orthogonal credits one-time.

We want to know what you are building on OpenClaw so we can make sure we support it. We are already working with companies like Orthogonal and Openrouter that are building things to make agents more useful, and we’re sure there are more tools out there we don’t know about. If you’ve built something agents want, please let us know. Comments welcome!

Hi HN, I forked chromium and built agent-browser-protocol (ABP) after noticing that most browser-agent failures aren’t really about the model misunderstanding the page. Instead, the problem is that the model is reasoning from a stale state.

ABP is designed to keep the acting agent synchronized with the browser at every step. After each action (click, type, etc), it freezes JavaScript execution and rendering, then captures the resulting state. It also compiles the notable events that occurred during that action loop, such as navigation, file pickers, permission prompts, alerts, and downloads, and sends that along with a screenshot of the frozen page state back to the agent.

The result is that browser interaction starts to feel more like a multimodal chat loop. The agent takes an action, gets back a fresh visual state and a structured summary of what happened, then decides what to do next from there. That fits much better with how LLMs already work.

A few common browser-use failures ABP helps eliminate: * A modal appears after the last Playwright screenshot and blocks the input the agent was about to use * Dynamic filters cause the page to reflow between steps * An autocomplete dropdown opens and covers the element the agent intended to click * alert() / confirm() interrupts the flow * Downloads are triggered, but the agent has no reliable way to know when they’ve completed

As proof, ABP with opus 4.6 as the driver scores 90.5% on the Online Mind2Web benchmark. I think modern LLMs already understand websites, they just need a better tool to interact with them. Happy to answer questions about the architecture, forking chrome or anything else in the comments below.

Try it out: `claude mcp add browser -- npx -y agent-browser-protocol --mcp` (Codex/OpenCode instructions in the docs)

Demo video: https://www.loom.com/share/387f6349196f417d8b4b16a5452c3369

Hisense TVs are displaying intrusive ads to users when they switch inputs, visit the home screen, or change channels, causing outrage among consumers. The electronics company denies any wrongdoing, but the practice has drawn significant criticism from disgruntled customers.

The article discusses the UK government's plans to grant ministers the power to restrict access to the entire internet, as part of the Online Safety Bill. This move has raised concerns about censorship and the potential for abuse of these broad powers.

The article discusses the relationship between Dow Chemical Company and Anthropic, a leading AI research company. It explores Dow's investment in Anthropic and the potential collaboration between the two organizations in advancing AI technology and sustainability initiatives.

This article presents a novel framework for training large language models in a more efficient and scalable manner, using a technique called 'LoRA' (Low-Rank Adaptation). The authors demonstrate significant performance improvements on a range of natural language processing tasks while requiring only a small fraction of the original model's parameters to be updated.

https://archive.ph/DEwy7

The article discusses a status update on an incident affecting the Claude AI service, providing details on the incident, the response, and the current status of the service.

The article discusses the origins of the training data used by Meta (Facebook) to develop their AI-powered smart glasses. It examines how Meta acquired and used data from various sources, including social media platforms, to train their computer vision algorithms for the glasses.

The article examines the concept of tort law, exploring its evolution, core principles, and the ongoing debate surrounding its role in modern society. It discusses the historical foundations of tort law and its current applications in addressing civil wrongs and providing remedies for individuals harmed by the actions of others.

This article compares the advantages and disadvantages of wired and Bluetooth headphones, highlighting that wired headphones offer better sound quality and reliability, while Bluetooth headphones provide more convenience and flexibility.

The article discusses the U.S. withdrawal of missile systems from South Korea, and the Philippines' concerns about potentially becoming the next target for such relocations. It explores the geopolitical implications and regional dynamics surrounding these developments.

The article discusses the latest developments in the investigation of 'Havana Syndrome', a mysterious medical condition affecting U.S. government personnel worldwide. It suggests that the initial hypothesis of a directed-energy attack was correct, and that the Biden administration's efforts to uncover the cause and perpetrator of these incidents have been making progress.