Hacker News 50

@betterhn50.e-work.xyz

🤖Posting Hacker News stories as soon as they reach 50 points. Older sibling of @betterhn20.e-work.xyz @betterhn300.e-work.xyz. Birds are still real but butterflies might be more welcoming to bots in the skies.

Zero-Mem: Zero-Token Memory Operations for LLM Agents https://arxiv.org/abs/2607.29377 (https://news.ycombinator.com/item?id=49178608)

Zero-Mem: Zero-Token Memory Operations for LLM Agents

LLM agents need memory to act consistently over long interactions, yet many systems use additional LLM calls to operate that memory. Generating intermediate records and mediating their retrieval adds recurring token and time costs, while omitted or merged details can obscure the original evidence. We ask whether structured memory access requires generation at all. Zero-Mem introduces \emph{zero-token memory operations}: no step outside final question answering invokes an LLM or consumes LLM input or output tokens; encoder computation is accounted for separately. Zero-Mem preserves original interaction traces as its source of record. It organizes the traces in two complementary ways. An entity--context graph exposes connections across interactions, while a temporal hierarchy preserves conversational locality and session state. For each query, Zero-Mem weighs the two views, retrieves from both, and follows their structure to recover supporting relations or surrounding context. Deterministic calibration first discards conflicting evidence and then keeps the reader's answer grounded in the retrieved traces. Only the final-QA reader invokes an LLM. Across long-memory and long-context question-answering benchmarks, Zero-Mem achieves competitive performance while eliminating LLM calls and LLM-token consumption from memory operations. With the same final-QA reader and context budget, it reduces memory-operation time cost by 57.6\% relative to the fastest compared baseline. Ablations support the contribution of the two views and their query-dependent coordination. Overall, the results show that structured agent memory need not generate an intermediate representation of the past. After peer review, the code and implementation details will be available at \textcolor{blue}{https://github.com/TheMoon0815/Zero-mem}.

arxiv.org

Zigbee vs. Matter over Thread:Understanding IoT Protocol Performance in Practice https://arxiv.org/abs/2603.04221 (https://news.ycombinator.com/item?id=49176983)

Zigbee vs. Matter over Thread: Understanding IoT Protocol Performance in Practice

The widespread adoption of the Internet of Things (IoT) has positioned smart homes as paradigmatic examples of distributed automation systems, where reliability, efficiency, and interoperability depend critically on the underlying communication protocol. Among the low-power wireless technologies available for this scenario, Zigbee and Matter over Thread have emerged as leading contenders. While Zigbee represents a mature, non-IP mesh networking solution, Matter over Thread introduces an IP-based architecture designed to unify device interoperability across different ecosystems. However, despite extensive documentation of their design principles, there is a lack of empirical, comparative performance data under realistic network conditions. This paper presents a comprehensive experimental comparison between the two protocols, conducted on a testbed built from commercially available hardware. The proposed methodology focuses on different key performance dimensions, such as scalability, responsiveness, and fault tolerance. The results reveal that Zigbee achieves a lower baseline overhead and faster route recovery, making it more responsive in static small-scale deployments. Matter over Thread, conversely, exhibits superior scalability and robustness, maintaining stable throughput and predictable latency across multi-hop scenarios. Overall, we highlight that Zigbee and Matter over Thread embody distinct trade-offs between agility, efficiency, and scalability.

arxiv.org