jabber.developer
0 Followers · 0 Following
  • Joined on 2025-06-19
Repositories Projects Packages Public Activity Starred Repositories
2
jabber.developer merged pull request devs/cproof#116 2026-05-16 15:34:25 +00:00
feat(history): nodb backlog — statusbar opt-in, /history off persistence, /privacy runtime switch, /correction fix
jabber.developer closed issue devs/cproof#114 2026-05-16 15:34:25 +00:00
nodb backlog
jabber.developer pushed to master at devs/cproof 2026-05-16 15:33:47 +00:00
2952466abd feat(history): consolidate logging controls and add dbbackend statusbar indicator
jabber.developer pushed to feat/no-db-backlog-114 at devs/cproof 2026-05-16 15:25:26 +00:00
129eddadd7 fix(command): update logging command argument constraints
jabber.developer pushed to feat/no-db-backlog-114 at devs/cproof 2026-05-16 15:08:06 +00:00
88958c0a37 chore(config): add .kilo/ and .roo/ to gitignore
jabber.developer approved devs/cproof#116 2026-05-16 15:06:23 +00:00
feat(history): nodb backlog — statusbar opt-in, /history off persistence, /privacy runtime switch, /correction fix

LGTM

jabber.developer commented on pull request devs/cproof#123 2026-05-16 14:31:13 +00:00
fix(ui): keep messages visible after scrolling in non-chat windows

If DB returns error, it might be a temporary problem, but it can get user stuck in the middle of the conversation if we change scroll_state. I do not think that DB_RESPONSE_ERROR is a valid reason to switch state.

jabber.developer commented on pull request devs/cproof#123 2026-05-16 14:31:13 +00:00
fix(ui): keep messages visible after scrolling in non-chat windows

it describes the behavior, which can be read from the code itself. It would only make sense to either add a concise explanation on WHY we do it, or to keep this stuff inside of the commit.

jabber.developer suggested changes for devs/cproof#123 2026-05-16 14:31:13 +00:00
fix(ui): keep messages visible after scrolling in non-chat windows

Please address these findings.

jabber.developer commented on pull request devs/cproof#116 2026-05-16 14:22:32 +00:00
feat(history): nodb backlog — statusbar opt-in, /history off persistence, /privacy runtime switch, /correction fix

refers to now-invalid command

jabber.developer suggested changes for devs/cproof#116 2026-05-16 14:22:32 +00:00
feat(history): nodb backlog — statusbar opt-in, /history off persistence, /privacy runtime switch, /correction fix
jabber.developer commented on pull request devs/cproof#116 2026-05-16 13:37:10 +00:00
feat(history): nodb backlog — statusbar opt-in, /history off persistence, /privacy runtime switch, /correction fix

console.c:1957

jabber.developer commented on pull request devs/cproof#116 2026-05-16 13:37:10 +00:00
feat(history): nodb backlog — statusbar opt-in, /history off persistence, /privacy runtime switch, /correction fix

I suggest we remove this command as well

jabber.developer commented on pull request devs/cproof#116 2026-05-16 13:37:10 +00:00
feat(history): nodb backlog — statusbar opt-in, /history off persistence, /privacy runtime switch, /correction fix

Doesn't affect messages fetched from DB though

jabber.developer suggested changes for devs/cproof#116 2026-05-16 13:37:10 +00:00
feat(history): nodb backlog — statusbar opt-in, /history off persistence, /privacy runtime switch, /correction fix

Generally LGTM, but certain features require further polishing. Please address the pointed out issues

jabber.developer approved devs/cproof#123 2026-05-16 13:12:15 +00:00
fix(ui): keep messages visible after scrolling in non-chat windows

LGTM

jabber.developer commented on pull request devs/cproof#123 2026-05-16 12:27:56 +00:00
fix(ui): keep messages visible after scrolling in non-chat windows

New concern: what happens if history is disabled for the user?

jabber.developer pushed to fix/scroll-non-chat-windows at devs/cproof 2026-05-16 12:24:39 +00:00
506794474a fix(ui): handle ai window scrolling in titlebar
jabber.developer pushed to fix/paged-non-chat-windows at devs/cproof 2026-05-15 14:32:41 +00:00
0096b11d24 fix(ui): reset paged flag at buffer bottom for non-chat windows
06b80bc89a fix(ai): fix memory leak of local provider in error paths
f9e0ba9630 fix(ai): fix memory leaks in ai session handling
7469f31c78 fix(ai): fix memory leaks in _ai_request_thread
5e329c77e1 fix(ai): fix memory leak in AI message stanza ID
Compare 7 commits »
jabber.developer opened issue devs/cproof#122 2026-05-15 14:23:28 +00:00
OMEMO error mem leaks