jabber.developer
  • Joined on 2025-06-19
jabber.developer pushed to feat/ai at devs/cproof 2026-05-11 20:55:06 +00:00
107f7778e2 fix(ai): collapse validate and dispatch into single critical section
jabber.developer pushed to feat/ai at devs/cproof 2026-05-11 20:34:14 +00:00
b634eed5af refactor(ai): remove cmd_ai_correct function
jabber.developer pushed to feat/ai at devs/cproof 2026-05-10 10:36:10 +00:00
010b2062a4 fix(ai): reset paged flag to display user message
jabber.developer pushed to feat/ai at devs/cproof 2026-05-09 21:06:14 +00:00
ecb07fd00c fix(ai): improve API error parsing and fallback
jabber.developer pushed to feat/ai at devs/cproof 2026-05-09 13:57:24 +00:00
a898cb212d feat(ai): implement robust JSON model parsing
jabber.developer pushed to feat/ai at devs/cproof 2026-05-09 13:21:05 +00:00
07d267b5bc fix(ai): protect window validation with mutex
jabber.developer pushed to feat/ai at devs/cproof 2026-05-09 13:16:18 +00:00
acae543057 feat(ai): add model caching, settings, and commands
jabber.developer pushed to master at devs/cproof 2026-05-06 14:11:13 +00:00
1aaa382d5e fix(verify): per-contact context in output, demote duplicate stanza-id to debug
jabber.developer pushed to feat/ai at devs/cproof 2026-05-06 13:57:22 +00:00
731b55fa19 Merge branch 'master' into feat/ai
3f36c303c2 feat(history): flat-file backend with bidirectional SQLite migration
Compare 2 commits »
jabber.developer commented on pull request devs/cproof#115 2026-05-06 11:54:34 +00:00
fix(verify): per-contact context in output, drop noisy duplicate-stanza-id warning

It's not an accurate path. Just avoid using /history.log suffix (preferred) or do not unescape the path.

jabber.developer commented on pull request devs/cproof#115 2026-05-06 11:54:34 +00:00
fix(verify): per-contact context in output, drop noisy duplicate-stanza-id warning

we could use auto_char instead

jabber.developer suggested changes for devs/cproof#115 2026-05-06 11:54:34 +00:00
fix(verify): per-contact context in output, drop noisy duplicate-stanza-id warning

please address the issues pointed out in the review

jabber.developer commented on issue devs/cproof#48 2026-05-05 19:33:23 +00:00
Add no-db options

Resolved by #94

jabber.developer merged pull request devs/cproof#94 2026-05-05 19:32:42 +00:00
no-DB mode implementation
jabber.developer closed issue devs/cproof#48 2026-05-05 19:32:42 +00:00
Add no-db options
jabber.developer pushed to master at devs/cproof 2026-05-05 19:26:13 +00:00
3f36c303c2 feat(history): flat-file backend with bidirectional SQLite migration
jabber.developer opened issue devs/cproof#114 2026-05-05 18:58:29 +00:00
nodb backlog
jabber.developer commented on pull request devs/cproof#94 2026-05-04 00:15:01 +00:00
no-DB mode implementation

Bug Report: Flatfile Backend Page-Up Scroll Stuck at Top

Summary

The flatfile database backend's page-up (scroll-up) functionality was getting stuck in the middle of the conversation,…

jabber.developer commented on pull request devs/cproof#94 2026-05-03 18:19:09 +00:00
no-DB mode implementation

is it efficient? Might g_strdup_printf first be more efficient than updating checksum each time?