darronz

Staleness isn't solved yet - honest answer is manual curation for now. age_days is on every memory so clients can factor it in, but there's no automatic decay.

It's on the roadmap. I wanted retrieval solid before layering temporal complexity on top. Longer term — age-weighted scoring, surfacing "this is 6 months old" in the MCP response metadata.

For the moment there is scoping feature that allows you to store & filter which helps narrow down retrieval.

Perhaps there is an upshot. If the Chinese government have complete access to all traffic in China, they will be unable to deny knowledge of hacking originating from their own IP blocks. By the same token you would expect that all unlawful traffic originating in China to cease.

The author forgot to mention something; Finding good staff.

Finding staff is difficult because of the scarcity of developers and anyone talented almost always has a job paying far more than a startup can afford.

Training juniors is the only alternative, but in doing so your company ends up being a training shop for other companies to headhunt from.

Just added a pull request for that

I wonder if a similar technique could be used to detect if a user has stylesheets enabled.