Settings and activity
16 results found
-
303 votes
Soaryn
supported this idea
·
-
74 votesSoaryn
shared this idea
·
-
11 votes
We are looking into this. Thanks for the request!
Soaryn
shared this idea
·
-
40 votes
We are planning a few updates to subscription payloads, including this item.
Soaryn
supported this idea
·
An error occurred while saving the comment -
15 votes
An error occurred while saving the comment Soaryn
commented
While the emote info would also be important, the amount that the cheer is, is albeit more important to me. If each bit amount were encoded in the emote structure as well that might work, though I am preferable to a separated integer array in order of provision.
Something to note, an emote alone would not be able to tell me what the amount was. Example being Party1337, would likely be an emote of Party1000.
Another note, is if the bit amounts were encoded in the emote array, you start to become less consistent with the other eventsub topics such as sub messages + emotes.
Soaryn
shared this idea
·
-
415 votesSoaryn
supported this idea
·
-
320 votesSoaryn
supported this idea
·
-
15 votesSoaryn
shared this idea
·
-
12 votes
We are investigating adding an EventSub subscription type for sub upgrade events.
Soaryn
supported this idea
·
-
9 votesSoaryn
supported this idea
·
-
36 votes
An error occurred while saving the comment Soaryn
commented
Adding on to what Barry said, I don't recommend using a boolean flag for this. There was a string identifier in pubsub, while I'd like it to just have Prime, Tier1, Tier2, etc, remaining consistent to the platform would be more idealistic, so it'd likely be Prime, 1000, 2000, so on.
-
6 votesSoaryn
shared this idea
·
-
12 votesSoaryn
shared this idea
·
-
7 votesSoaryn
supported this idea
·
-
69 votes
Changing status to long-term. To preserve ecressey's previous comment, "I'm not clear on the use case for this. It seems like with a resub chat message notification and subscribe/unsubscribe events you should have the data you need."
Soaryn
supported this idea
·
-
4 votes
An error occurred while saving the comment Soaryn
commented
Marenthyu pointed out some changes as well as answered some questions on use cases for some of the fields.
==Redemption Info:==
Time String
Id GUID (String)
Channel User
Redeemer User
UserInput String
Status String
Reward RewardInfo==Fields of Reward:==
Id GUID (String)
Name String
Prompt String
Cost Integer
InputRequired Boolean
SubOnly Boolean
TotalUsed Integer
MaxLimit IntegerAn error occurred while saving the comment Soaryn
commented
Old Data:
"type" - Unnecessary. This is encoded into the topic already one layer up. If you want this can be changed to context.
"data": - No reason to encapsulate further
"timestamp": - should just be named "time" to be consistent with other topics
"redemption": - Unnecessary encapsulation
"id": - should be on root.
"user": - Fine actually.
"channel_id": - Should match the user structure so you are presented with username and displayname as well.
"redeemed_at": - Should just be time. I understand there is a difference when the message was created and when a reward was redeemed. But we shouldn't need to know message creation
"reward": {
"id": - This is fine to have separate from "root/id"
"channel_id": - Unnecessary. We already have the channel this is associated to.
"title": - Fine
"prompt": - Fine
"cost": - Fine
"is_user_input_required": - Will we get an event at all before they input? "input_required" would be a better name
"is_sub_only": - Can remain
"max_per_stream": { "is_enabled": false, "max_per_stream": 0 } - perhaps too verbose,
"user_input": "yeooo",
}
Unnecessary Data static data. Provide an API fetch instead.:
"image" - Example on document has 147 byte per url for just image.
"default_image"
"background_color" - Why?
How do we even get the event if they are toggled?
"is_enabled": true,
"is_paused": false,
"is_in_stock": true,
"should_redemptions_skip_request_queue": - what?
"status": - Does this have other options?Soaryn
shared this idea
·
I personally would find it useful to have the gift provider info on all of the sub topics:
channel.subscribe; end; message;