News for hackers. Stuff that matters.

blackmanta

Re:Is anyone actually using OpenClaw? on Wednesday April 15, 2026 @07:12PM (#47786542)
I have an instance that does search related to my research interests, tracks news related to viruses in the US, events happening around my area and an “urgent” news job that uses searx and for things going on around me. I used Qwen 3.5 9B and tuned some of the jobs with GPT 5.4. I recently switched to use Gemma 4 and there was seemingly no major difference. I’ve found it useful for the digest and for findings papers without much effort.
Re:I ran Gemma 4 as a local model in Codex CLI on Sunday April 12, 2026 @09:27PM (#47746477)
With a nvidia spark or 128gb+ memory machine, you can get a good speed up on the 31B model if you use the 26B MoE as a draft model. It uses more memory but I’ve seen acceptance rate at around 70%+ using Q8 on both models
Unless the goal of the backdoor is to redirect traffic flows through packet inspection devices that the attacker also controls, the decoupling of the control and data plane in SDN deployments requires a more creative, intricate solution to allow for wiretapping compared to traditional routers.
Re:Context engineering is sleeping on the humble hyperlink on Saturday October 25, 2025 @09:34AM (#45703769)
You can actually enable search in codex but adding the following to the config file

[tools] web_search = true

Re:Show HN: Yet Another Memory System for LLM's on Monday August 18, 2025 @08:07PM (#44946782)
I will look into adding this in a future update.
Re:Show HN: Yet Another Memory System for LLM's on Monday August 18, 2025 @08:07PM (#44946779)
The graph functionality is stubbed but I will expose it in a future update. You can also use metadata and tags for similar things.
Re:Show HN: Yet Another Memory System for LLM's on Thursday August 14, 2025 @03:22PM (#44904511)
I may explore this when I implement the vectordb implementation I started.
Re:Show HN: Yet Another Memory System for LLM's on Thursday August 14, 2025 @02:09PM (#44903698)
While the examples and provided prompt lean toward code (since that's my personal use case), YAMS is fundamentally a generic content-addressed storage system.

I will attempt to run some small agents with custom prompts and report back.

Re:Show HN: Yet Another Memory System for LLM's on Thursday August 14, 2025 @12:50PM (#44902716)
I have been using it for task tracking, research, and code search. When using CLI tools, I found that the LLM's were able to find code in less tool calls when I stored my codebase in the tool. I had to wrangle the LLMs to use the tool verse native rgrep or find.

I am also trying to stabilize PDF text extraction to improve knowledge retrieval when I want to revisit a paper I read but cannot remember which one it was. Most of these use cases come from my personal use and updates to the tool but I am trying to make it as general as possible.

Re:Show HN: Yet Another Memory System for LLM's on Thursday August 14, 2025 @11:10AM (#44901340)
I stored the codebase for yams in the tool. The "blocks" are content-defined blocks/chunks, not filesystem blocks. They're variable-size chunks (typically 4-64KB) created using Rabin fingerprinting to find natural content boundaries. This enables deduplication across files that share similar content.
Re:Show HN: Yet Another Memory System for LLM's on Thursday August 14, 2025 @10:48AM (#44901053)
I have not, but that is something I plan to do when I have time.
Re:Show HN: Yet Another Memory System for LLM's on Thursday August 14, 2025 @10:44AM (#44900993)
I am working to improve the CLI tools to make getting this information easier but I have stored the yam repo in yams with multiple snapshots and metadata tags and I am seeing about 32% storage savings.
Re:Show HN: Yet Another Memory System for LLM's on Thursday August 14, 2025 @10:24AM (#44900765)
The graph functionality is exposed through the retrieval functionality. I may improve this later but the idea was to maximize getting the best results when looking for stored data.
Re:Show HN: Yet Another Memory System for LLM's on Thursday August 14, 2025 @10:21AM (#44900730)
The system is honestly tuned for storage efficiency not speed but these configurations are tunable and you can use the benchmarks as a reference for tuning. https://github.com/trvon/yams/blob/main/docs/benchmarks/perf...
Re:Show HN: Yet Another Memory System for LLM's on Thursday August 14, 2025 @01:25AM (#44897012)
The tool has built-in versioning. Each file gets a unique SHA-256 hash on storage (automatic versioning), you can update metadata to track version info, and use collections/snapshots to group versions together. I have been using the metadata to track progress and link code snippets.
Re:Show HN: Yet Another Memory System for LLM's on Thursday August 14, 2025 @12:43AM (#44896802)
That should be fixed now. It was a misconfiguration of CloudFlare SSL with GitHub Pages.

Show HN: Yet Another Memory System for LLM's

https://github.com/trvon/yams

Built this for my LLM workflows - needed searchable, persistent memory that wouldn't blow up storage costs. I also wanted to use it locally for my research. It's a content-addressed storage system with block-level deduplication (saves 30-40% on typical codebases). I have integrated the CLI tool into most of my workflows in Zed, Claude Code, and Cursor, and I provide the prompt I'm currently...

( Read More... | 46 comments | 8 points | on HN )
I have used Google messages with RCS on grapheneos.
Re:Microsoft Security-101: Open-Source curriculum on Friday March 01, 2024 @11:02PM (#39569689)
Microsoft does take security pretty seriously with windows. There have been times they make mistakes, but historically, they are doing better now than they were in the early 2000s before Bill Gates sent a memo noting that they needed to take security seriously. You could argue they take security as serious as any major play like apple and google, seeing they touch a lot of private user data.

[1] https://news.microsoft.com/2000/12/07/gates-offers-new-techn...

Older »