Those functions work well, as they do what you'd expect them to do
However, I'm unsure if I can do better using the instructions available in the documentation's "Using Chat" section, because glancing at them, they seem to depend on the notification endpoint which is only accessible through lazer (not using a normal oauth app)
I'd love to allow developers to make their own applications that interact with the chat in a practical way where requesting messages every so often wasn't needed through the use of websockets, but without possibly getting a little hacky and making the API server believe it is talking to a lazer client, that seems impossible
I haven't tested if it's for sure impossible though! If it is possible, then such features would be available for the 0.5.0 release of osu-api-v2-js, but if it is not possible, then I might have to do something about the function that implements Chat Keepalive because that function has no effect beyond returning UserSilences if it doesn't affect any client or website
(in contrast, the function that implements Mark Channel as Read does something, even if it can be considered very minor!)
Those functions work well, as they do what you'd expect them to do
However, I'm unsure if I can do better using the instructions available in the documentation's "Using Chat" section, because glancing at them, they seem to depend on the notification endpoint which is only accessible through lazer (not using a normal oauth app)
I'd love to allow developers to make their own applications that interact with the chat in a practical way where requesting messages every so often wasn't needed through the use of websockets, but without possibly getting a little hacky and making the API server believe it is talking to a lazer client, that seems impossible
I haven't tested if it's for sure impossible though! If it is possible, then such features would be available for the 0.5.0 release of osu-api-v2-js, but if it is not possible, then I might have to do something about the function that implements
Chat Keepalivebecause that function has no effect beyond returningUserSilences if it doesn't affect any client or website(in contrast, the function that implements
Mark Channel as Readdoes something, even if it can be considered very minor!)