Skip to content

Treat emoji characters as spam in KubeDB Inquiry - #136

Merged
tamalsaha merged 1 commit into
masterfrom
kubedb-inquiry-emoji-spam-filter
Sep 8, 2026
Merged

tamalsaha merged 1 commit into
masterfrom
kubedb-inquiry-emoji-spam-filter

Conversation

@tamalsaha

Copy link
Copy Markdown
Member

Summary

  • Add containsEmoji/isEmojiRune, checking a string for runes in the common emoji Unicode blocks (pictographs, emoticons, transport, dingbats, misc symbols/technical, flags, and emoji variation selectors)
  • IsSpam() now also flags a submission when any field contains an emoji, in addition to the existing bitcoin/btc/coinbase/mining keyword check
  • Adds test cases for emoji in notes and in the customer name, plus a case confirming plain ASCII punctuation (e.g. :)) is not treated as spam

Test plan

  • go build -mod=vendor ./...
  • go vet -mod=vendor ./pkg/server/...
  • go test -mod=vendor -race ./pkg/server/...
  • Submit /_/kubedb_inquiry/ with an emoji in any field and confirm it's rejected and not processed

Reject KubeDB Inquiry submissions whose fields contain an emoji
character, alongside the existing bitcoin/btc/coinbase/mining
keyword check. Detection covers the common emoji Unicode blocks
(pictographs, emoticons, transport, dingbats, misc symbols, flags,
and emoji variation selectors).

Signed-off-by: Tamal Saha <tamal@appscode.com>
@tamalsaha
tamalsaha merged commit 9348e21 into master Sep 8, 2026
4 checks passed
@tamalsaha
tamalsaha deleted the kubedb-inquiry-emoji-spam-filter branch September 8, 2026 18:10
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