Skip to content

EventUser and is_anonymous #12

@TheStaticMage

Description

@TheStaticMage

Kick used to include is_anonymous with basically all user payloads, even where it didn't make sense.

When they added the payload for kicks gifted, this was removed.

Now they've added a payload for channel rewards, and this doesn't have is_anonymous either.

{
  "id": "01KBHE78QE4HZY1617DK5FC7YD",
  "user_input": "unban me",
  "status": "rejected",
  "redeemed_at": "2025-12-02T22:54:19.323Z",
  "reward": {
    "id": "01KBHE7RZNHB0SKDV1H86CD4F3",
    "title": "Uban Request",
    "cost": 1000,
    "description": "Only good reasons pls"
  },
  "redeemer": {
    "user_id": 123,
    "username": "naughty-user",
    "is_verified": false,
    "profile_picture": "",
    "channel_slug": "naughty_user"
  },
  "broadcaster": {
    "user_id": 333,
    "username": "gigachad",
    "is_verified": true,
    "profile_picture": "",
    "channel_slug": "gigachad"
  }
}

I'm trying to add a payload for this to this repo but wondering, should I do something like KicksGiftedEventUser (creating another special case snowflake)? Or maybe it's time for a breaking change where EventUser doesn't have is_anonymous and there's an EventUserWithAnonymous type or something?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions