SQLite

Evidence in the last complete seven days

Source mentions

2

Previous seven days 1

Distinct sources

2

Previous 1

Comparable growth

Not comparable

Ranking appearances

0

Collection observations and undated records are separate from dated publication counts. Observed in 7d：2 · Undated records：0

Daily history · up to 90 days

Bars show dated source mentions. The latest UTC day may be incomplete. Zero mentions and missing collection coverage are different conditions.

Source evidence

Sources in the evidence shown：Hacker News 1 · V2EX 2

1. Hacker News · Published Nov 3, 2026

   Show HN: Replacing Turn-Based LLM Agents with SQLite and System One Models

   View source record →

2. V2EX · Published Oct 31, 2026

   [分享创造] Casnode 2.0：一个长得像 Discourse 的论坛， Go + Next.js， SQLite 就能跑

   一直想给项目搭个 Discourse 那样的论坛，但每次看到要 Ruby + PostgreSQL + Redis 、镜像好几个 G ，就劝退了。 所以我们把 Casnode 重写了一遍，界面和交互照着 Discourse 默认主题做：话题列表、时间线、底部编辑框、通知、未读、聊天、徽章、投票，基本都在。 几个点： 下载一个三十来 MB 的压缩包，./casnode 就起来了，注册第一个账号就是管理员（需要 Node 20+） 默认 SQLite ，也支持 MySQL / PostgreSQL / SQL Server ，不需要 Redis 页面全部服务端渲染，sitemap 、RSS 、JSON-LD 、Open Graph 都有，对搜索引擎友好 自带注册登录；单点登录可选，OIDC 、OAuth 2.0 都

   View source record →

3. V2EX · Published Oct 24, 2026

   [程序员] [dsh-gitea-search 发布] DSH+Gitea 引入 SQLite FTS 索引+向量记忆副库

   终于搓完发布了 #dsh #dsh-gitea-search 欢迎试用、提建议 项目地址 ： https://github.com/offzen/dsh-gitea-search 开发的动机 ：token 不够烧的，还经常因为重复的任务延长等待，无数的 429 限流...原理上很多任务可以在本地加速。 DSH 的插件机制很适合自己改造，只有一个搜索框显然是太弱了；手动去输脚本使用上不现实。 跨会话检索和长期记忆 ：用 SQLite 全文索引加快关键词查找，再用向量副库做语义相近内容的检索，方便找回以前的方案、命令和报错等片段。（你通常记得的就只有片段信息，如果让 AI 检索会很慢） 大量代码和信息本来就在本地，不必整包丢给云端模型去耗时间和 token 。本地先找出来，再只把命中的上下文交给模型，交互会更快，也

   View source record →

Review priority 50 / 100

This score orders research candidates. It is not search volume, a forecast or verified commercial demand.

• Evidence

  12.7 / 30

  Distinct dated articles or first observations; repeat crawling adds nothing.

• Publisher diversity

  16 / 25

  Conservative owner grouping; syndicated copies count once.

• Comparable change

  0 / 20

  Comparable complete weeks only; no percentage from a zero baseline.

• Recent evidence

  13 / 15

  Latest publication or first observation, not repeated fetch time.

• Name specificity

  7.8 / 10

  Explicit entities and technical concepts outrank ambiguous acronyms.

Limitations and interpretation

• First observation is a collection milestone, not proof that a word or product is new to the world.
• Counts describe monitored public sources, not the whole web or search demand.
• First observed here is not the invention date of a name or idea.
• Candidates come from public titles, summaries and entity URLs, not verified full-text analysis.
• Owner grouping is conservative; undisclosed syndication may remain.
• An established concept or common product name retained as a baseline, not a newly invented term.
• Both weeks need adequate, comparable collection coverage.
• Sources behind this term changed or lack a comparable baseline.
• The previous week is too small for a reliable percentage change.