Chat 2.0.31: the paste/drop attachment path publishes the image as given - #138
Merged
Merged
Conversation
Live acceptance of 2.0.30 (seed test account, released beta.11): the 1.9 MB PNG correctly skipped the inline path, then landed in the attachment chip as "polar-drag.webp, 50 KB" — the bytes attachment path (#105, hosts without Home's picker) re-encoded every image to WebP at max width 1200 / quality 0.6 ("Hub's parameters"), so the published resource was still not the user's image. compressImage is gone: prepareLocalAttachment base64s the File exactly as given, keeps its name and type, and the 10 MiB IMAGE cap is the user's to meet. Developers reference row replaced ("Image re-encoding: none"); README; version 2.0.31. Test pins byte-identity of the staged payload. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AGDWY3yhSNv2NKTVUBJQBf
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Found by the live acceptance of 2.0.30 with the seed test account on the released Home beta.11: dropping the 1.9 MB
polar-drag.pngnow correctly skips the inline path — and lands in the attachment chip aspolar-drag.webp, 50 KB. The bytes attachment path (#105, hosts without Home's picker: paste/drop) re-encoded every non-GIF image to WebP at max width 1200 / quality 0.6, so the published resource was still not the user's image. The picker path never did this.Change:
compressImageremoved;prepareLocalAttachmentbase64-encodes theFileexactly as given (name, type, bytes). An image over the 10 MiB IMAGE cap is the user's to shrink. Developers reference row "Inline image re-encode" → "Image re-encoding: None — published, inlined or attached exactly as given". README; version 2.0.31.Test: byte-identity of the staged payload for a PNG (name/type/size/base64). 922/922, build clean.
With #137 this closes the rule completely: Chat never modifies a user's image on any path.
🤖 Generated with Claude Code
https://claude.ai/code/session_01AGDWY3yhSNv2NKTVUBJQBf