Forward the conversation fields a group DM push needs #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/group-push-fields"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Accepts and forwards conversation_id, conversation_type and sender_id, so the Pixelfed fork can push group DMs (Pixelfed 0.14.2). A group push carries no account_id by design: shipped app versions would otherwise open a private thread with the sender. Data map extracted into pushData() with a test for both the group and the legacy shape.
Tested: go build, go vet, go test (golang:1.26-bookworm).
🤖 Generated with Claude Code
Pixelfed 0.14.2 has group conversations, and the fork is about to push them. A group push has to say which conversation it belongs to, but the relay forwards a fixed set of keys and would drop anything new in silence. It now also accepts and forwards conversation_id, conversation_type ("dm" or "group") and sender_id. A group push carries no account_id, on purpose: shipped app versions open the 1:1 thread with whatever account_id names, which for a group would be a private thread with the sender. Without it they open the app and go nowhere. The data map moves into pushData() so this can be tested. Empty values are still dropped by the APNs client, so a payload from an older fork forwards exactly what it did before. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>