Meta: Can someone more familiar with the rules of HN please tell me why some Show HN posts get immediately “flagged” while others don’t? I have seen commercial entires like this be flagged while this one is on the first page.
Cannot agree more. As part of our SOC2 we have to log and respond to all inbound vulnerability reports. Before it was easy to tell if a report was just a bounty hunter looking for a low hanging fruit. Now well crafted emails with seemingly legitimate disclosures take a lot of time to validate and triage.
Our solution was to build a tool that uses LLMs to assess the report before it gets to us. Honestly I wish we didn’t have to do this but it works and has really allowed us to spend our time on the actual good reports. (Feel free to check it out at fortworx.com if you want)
For our metrics and autoscaling engine at Cloud 66, we went through 5 iterations before settling on Clickhouse:
1. Redis
2. Cassandra
3. Handrolled: Ruby + RabbitMQ
4. Handrolled: Go + RabbitMQ
5. Clickhouse
Every time we reached some limit or huge optimization burdens that were unfeasible. Clickhouse has been rock solid for the past 4 years.
that's an interesting approach and something i also considered (using git to avoid conflicts). one thing i needed was a "database" (basically a folder of markdowns) with a fixed schema so i can let the agents record their decisions in (for example when the code conflicts with product design spec). this combined with search has been a real lifesaver.
I tend to agree with the rest of the commenters that the most likely outcome is that harnesses will include features like this. I had a slightly different issue and that was 'project-level memory' that i can use across models or harnesses (chat, claude code, etc).
for a while i used Obsidian but it was not very good with hosted tools like claude.ai then i moved to a combination of Linear and Notion. Still using Linear but Notion ended up being a royal pain: it is built for humans not agents. It is block based and when multiple agents use it there is a lot of corruption in the process.
I wanted a markdown only, notion built for agents that can work with multiple agents so built one: markbase.cloud
This.^
I realized this first when moving a design spec from Claude chat to Claude Code and panicked. I literally had to build something like Notion but for agents to act as a portable memory between all cloud and local models and agents. But honestly it paid off!
If you are interested you can try it out at markbase.cloud (disclaimer and all that). I am not charging for it.
When you signup for Railway, they have uncommon way of making sure you have read and understood their T&C regarding abuse of their systems, including crypto mining, etc.
My guess is that many are abusing their free tier, causing them trouble with their service providers.
I take no joy in seeing Railway take a hit like this, even as a competitor, but free compute attracts all sorts of strange users. We've been there and decided early on to avoid free compute even it costs us our top of the funnel.
Overall, it's an interesting idea. Although it's Google and it's packed, it's going to be packed with Gemini and Google AI and whatnot. My problem is not the AI, nor is it that it's an undefined territory for what a laptop use case is. My problem is Google's attention span. Google is notoriously bad at paying attention to any product for more than 18 months. I'm not going to spend money on buying a piece of hardware where it's going to be totally irrelevant from a manufacturing point of view in 18 months and be left high and dry holding the bag.
It's turned into a bizarre place. Today I asked the same question on /r/meta and my question was immediately removed without explanation. I tried to message the mods and got bounced with a "you cannot send a message to that user"
We certainly see a lot more automated security vulnerability reports coming our way that are clearly generated by AI and in bulk.
As a SOC 2 compliant company we have to record each one and respond to them as per our policies.
Our solution was to use AI to combat that as the first line of defence and filtering. Eventually we turned this system into a separate business (fortworx.com) because it seems a lot of other companies have the same problem.
Looks good! Do you have an MCP or API in your roadmap? The reason: managing a lot of templates and their placeholders can get out of hand pretty quickly and agents can be a good way to deal with the complexity.
I'd love to try this with sendops.dev although I'm not sure how it's going to work with the git backed templating it has.
Zed is a really good editor in an age that every other editor has forgotten to be about *editing* and wants to be a wrapper around coding agents.
On the agent side, I really like their ACP approach but for now it seems buggy and limited in functionality (previous message editing, occasionally never-ending work, ...)