Skip to content

A server setting for other servers' emoji, off by default (GRYT-1660) - #280

Merged
sivert-io merged 1 commit into
mainfrom
claude/GRYT-1660-external-emojis
Oct 5, 2026
Merged

sivert-io merged 1 commit into
mainfrom
claude/GRYT-1660-external-emojis

Conversation

@sivert-io

Copy link
Copy Markdown
Member

Messages now only show images from their own server (Gryt-chat/client#791). This adds the owner's switch for the one exception, other Gryt servers' custom emoji. It's off by default, because such an emoji loads from the other server, which then sees the address of everyone who reads the message. That's the opt-in the task asked for.

What changes:

  • server_config.external_emojis INTEGER NOT NULL DEFAULT 0, added by the same hasColumn migration as video_profiles.
  • externalEmojis in the settings patch (socket and management) and in settingsView.
  • server_info.external_emojis, for clients to read.

src/settings/externalEmojis.test.ts covers the default, turning it on and off, a patch that leaves it out, and a value that isn't a boolean.

What to look at:

  • src/db is review-required. The diff there is one column, one migration line and one field in the row mapper.
  • The default is 0, the opposite of video_profiles. Existing servers come up with it off.

The client half, the switch in server settings and the picker, comes next and reads external_emojis.

🤖 Generated with Claude Code

Messages only show images from their own server now (client#791). This
adds the owner's switch for the one exception: other Gryt servers'
custom emoji. It's off by default, because the emoji loads from the
other server, which then sees the address of everyone reading.

external_emojis in server_config, externalEmojis in the settings patch
and view, and external_emojis in server_info for clients to read.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@sivert-io
sivert-io merged commit aae208f into main Oct 5, 2026
6 checks passed
@sivert-io
sivert-io deleted the claude/GRYT-1660-external-emojis branch October 5, 2026 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant