Feature Request: Official support for Trovo live chat integration

[DovahDoVolom]

The implementation of new live chat/live streaming provider Trovo.

Trovo: https://trovo.live/policy/apis-developer-doc.html

[TehTurk]

There's a few other chats too you'd wana support I think too with this, because I'm aware there's also the potential for IRC support, or any chat service for that matter that has a public API.

[Frooxius]

I was considering adding YouTube at some point, but I'm not sure what the demand is. I'm not familiar with Trovo, so I don't really know how much demand would there be for one.

I do not recommend a single topic for all integrations though, because each service integration is a separate workload and separate feature, there's not really a way to integrate them generally. If you want me to integrate both at the same time, that will severely lower the priority of the whole task.

I recommend making separate topics for each service you want to integrate and then having people vote on which ones matter the most to them so we can gauge it per-service. That way priority of integrating YouTube can be bumped up and happen much sooner, but if it's bundled with another different service it will drag it down.

[DovahDoVolom]

Will do, Ill set this to be a request for Trovo as it was requested by Castle on discord and by that id assume be a higher demand then YouTube. Haven't seen any requests for YouTube yet. Ill move YT Live to a separate request.

[TehTurk]

I don't know if you wanted to split these up, this would have probably been better off as a more general integration as there are numerous and I mean numerous amount of chat apis, but all the underlying formats are typically standardized. Like most IRCS integrate into chat servers, unless I'm unaware of more current common standard that's been for the current day.

[DovahDoVolom]

I don't know if you wanted to split these up,

I recommend making separate topics for each service you want to integrate and then having people vote on which ones matter the most to them so we can gauge it per-service.

[TehTurk]

I'm aware of this, I repeated my statement in mind of that as basically you'll be implementing each service individually and it'll just add more work instead of be a good all for one solution or something that's approach if services change or more are requested , just thought there was an chat standard that would make this be easier overall.

[ProbablePrime]

Hey Turk, froox himself requested separate issues.

As someone speaking from experience, everyone does chat slightly different.

We should discontinue a discussion about if the issue should exist and now focus on conversation about the actual issue.

[Frooxius]

Yeah there's unfortunately not a unified way to implement all those. Some of these are using existing protocols under the hood like IRC, but they're generally not human-readable messages and require a fair bit of processing and parsing.

E.g. the Twitch messages are IRC, but if you viewed the raw messages you'd see a complex jumble of characters, which encode all the data of the message (badges, emotes, cheer status and so on).

[TehTurk]

Ah I didn't consider the extra data on top of the text, also apologies, Thanks as always Froox.