littlefox/neokom
Watch
1
2
Fork
You've already forked neokom
 1
Code Issues 8 Pull requests Projects Releases 12 Packages Activity Actions

No comments is a request: say so, and ask before replying (#334) #386

Merged
littlefox merged 5 commits from issue-334-no-comments into main 2026-10-28 12:11:08 +00:00
Conversation 0 Commits 5 Files changed 9 +143 -33
littlefox commented 2026-10-28 09:56:14 +00:00
Owner
Copy link

Closes #334

Option 1, as the user chose, plus the Emacs client's question:

  • "Låst för svar" → "Ber om att inte få svar" (the reader's line in the chat, the author's switch "Be om att inte få svar" / "Sluta be om…", the status messages). No-comments is advisory in Protocol A.
  • Replying anyway asks first, as Emacs does ("Författaren vill inte ha svar. Svara ändå?"): Svara and Svara privat on the post, however reached, and the chat's reply field on Skicka. The chat no longer hides the field.

Verified: lock.spec rewritten (ask, cancel keeps the text, yes opens the composer, stop asking); compose.spec follows; clippy three ways.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8

Closes #334 Option 1, as the user chose, plus the Emacs client's question: - "Låst för svar" → "Ber om att inte få svar" (the reader's line in the chat, the author's switch "Be om att inte få svar" / "Sluta be om…", the status messages). No-comments is advisory in Protocol A. - Replying anyway asks first, as Emacs does ("Författaren vill inte ha svar. Svara ändå?"): Svara and Svara privat on the post, however reached, and the chat's reply field on Skicka. The chat no longer hides the field. Verified: lock.spec rewritten (ask, cancel keeps the text, yes opens the composer, stop asking); compose.spec follows; clippy three ways. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8
Protocol A calls no-comments (aux 4) advisory, and other clients reply
as usual, but NeoKOM said "Låst för svar" and hid the chat's reply
field. It now says what it is ("Ber om att inte få svar") and, as the
Emacs client does, asks "Svara ändå?" before a reply or a personal
reply to such a post, and before sending from the chat's field.

Refs #334

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8
Compose spec: replying to a no-comments post asks first
Some checks failed
perf / perf (pull_request) Has been skipped
Details
ci / plan (push) Successful in 4m25s
Details
ci / check (push) Successful in 12m15s
Details
ci / e2e (android) (push) Successful in 21m41s
Details
ci / e2e (desktop) (push) Successful in 21m8s
Details
ci / e2e (iphone) (push) Successful in 21m40s
Details
ci / desktop (push) Failing after 24m46s
Details
71bfb33c4f 
Refs #334

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8
Merge remote-tracking branch 'origin/main' into issue-334-no-comments
All checks were successful
perf / perf (pull_request) Has been skipped
Details
ci / plan (push) Successful in 1m51s
Details
ci / check (push) Successful in 13m15s
Details
ci / desktop (push) Successful in 21m19s
Details
ci / e2e (desktop) (push) Successful in 23m8s
Details
ci / e2e (android) (push) Successful in 23m15s
Details
ci / e2e (iphone) (push) Successful in 24m48s
Details
950f355fea
Merge main into issue-334-no-comments
All checks were successful
perf / perf (pull_request) Has been skipped
Details
ci / plan (push) Successful in 2m55s
Details
ci / check (push) Successful in 12m18s
Details
ci / desktop (push) Successful in 19m50s
Details
ci / e2e (desktop) (push) Successful in 22m11s
Details
ci / e2e (android) (push) Successful in 23m51s
Details
ci / e2e (iphone) (push) Successful in 29m2s
Details
afdff95f92
littlefox referenced this pull request from a commit 2026-10-28 15:15:38 +00:00
Release 0.8.0
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
area/ci
Forgejo Actions, runner, tests

  
area/desktop
Desktop build

  
area/packaging
Arch, Debian, Fedora, NixOS packages

  
area/protocol
kom-proto, wire format, charset

  
area/reading
Unread tracking, reading order, review

  
area/ui
Dioxus app, layout, interaction

  
area/web
Web build and relay

  
area/writing
Composing and sending texts

  
kind/bug
Something is broken

  
kind/feature
New functionality

  
kind/infra
Tooling, tests, CI, dev environment

  
kind/request
requests for features or changes from users

  
needs/user
Waiting for a decision or action from littlefox

  
parked
Kept for reference; no work planned until the user says so

  
perf
Run the perf workflow and its budgets on this pull request (#287)

  
security
Security-relevant

  
upstream
A proposal for Protocol A or lyskomd, for the LysKOM development group

No labels
area/ci
area/desktop
area/packaging
area/protocol
area/reading
area/ui
area/web
area/writing
kind/bug
kind/feature
kind/infra
kind/request
needs/user
parked
perf
security
upstream
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
littlefox/neokom!386
No description provided.