-
-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duplicate messages when using HTTPS POST #304
Comments
To add, I get it that it's not an exact duplicate, as one is posted in the YouTube chat, and the other one in the Twitch that, and that the top left chat is basically consolidated. But the way I want to use this API call would be enough to just print it once in the consolidated chat window. I did not find any API parameter to control whether to send it to a specific chat. I tried "tid" in the JSON body, and "channel" query parameters, but they both did not change the behaviour. |
Is the goal to send messages to Youtube and Twitch? If you send a message to those sites, and you are capturing messages of those sites, then its expected you'll get both messages from those sites. You can enable this option to filter all but the first message however: It might work to filter said messages. should work in most cases. |
YES! That's exactly the setting I was looking for, lol. I went through the list of options twice, but apparently managed to miss it twice. Thank you :) |
There's too many options. Apologies. I use the search bar at the top to look for keywords now instead |
No worries, having an extended amount of features can not become a negative thing. Bought you a coffee instead ^^ |
I'm using the standalone app, version v0.1.51.
I'm building an API to interact with the chat, which requires me to use the HTTPS POST feature (endpoint: https://io.socialstream.ninja/$sessionid)
But I run into an issue where these chat messages are duplicated. I can reproduce this with the API Sandbox, as seen on this screenshot:
Am I expecting the wrong thing, am I doing something wrong or is it a bug?
The text was updated successfully, but these errors were encountered: