jchat app self hosting

[Vereor]

Is this project supported for self hosting? (only for single channel usage)

I had to dig around the issues to find the credentials.js that isn't part of the git
Even setting up with my own creds I am getting an

{"error":"Not Found","status":404,"message":"This API does not exist"}
on the
https://api.twitch.tv/v5/users?login=channelname&client_id=xxxxxxx

So any tips if supported would be appreciated.

[Houdini111]

I'm also interested in the answer to this. I'm interested in contributing a feature but the code here doesn't match what's live. I can see that the live version connects to helix instead of v5 (https://api.twitch.tv/helix/users and https://api.twitch.tv/helix/bits/cheermotes).
So, despite creating my own Twitch Dev application to get my own clientID it's impossible to run locally and thus contribute with any measure of confidence.

[Kissaki]

On live the v2 index.html and script.js changed. You can download and update them, or use my fork where I did that (+ fixed generated URL logic for self hosting).

The twitch auth token is only necessary for the channel name to channel ID mapping/translation via twitch api, and to retrieve the bit cheer emotes. So if those are undesired, it can be adjusted and hosted without a need to regularly refresh the auth token.

[Kissaki]

I set up https://kcode.de/projects/jchat/host/ to help you generate the required token for self-hosting, if that is a problem.

[Vereor]

@Kissaki Thanks for that. I can confirm your fork is working great for me

[arrowgent]

yes.
you can download the files, setup and change the required helix api and oauth codes
then point obs/whatever to the path/to/your/jchat/index.html?options=etc

you can run the entire thing locally for your channel

[arrowgent]

I'm also interested in the answer to this. I'm interested in contributing a feature but the code here doesn't match what's live. I can see that the live version connects to helix instead of v5 (https://api.twitch.tv/helix/users and https://api.twitch.tv/helix/bits/cheermotes). So, despite creating my own Twitch Dev application to get my own clientID it's impossible to run locally and thus contribute with any measure of confidence.

i tried to PR updates and documentation about the new helix api
no response, after a month i removed the PR
#27

kissaki, did a fork and fixed similar issues...
https://github.com/Kissaki/jChat
or here
https://github.com/KevinKYeh/kChatV2

you are correct, the Live (view browser source code) is not updated here.

[arrowgent]

yes. you can download the files, setup and change the required helix api and oauth codes then point obs/whatever to the path/to/your/jchat/index.html?options=etc

you can run the entire thing locally for your channel

just for convenience of everyone in the future: here is my obs-browser source

file:///home/catbox/.config/obs-studio/jchat/jChat-main/v2/index.html?channel=CHANNELNAME&fade=10&hide_commands=true&size=1

obviously change CHANNELNAME to the channel you want to watch chat

i run obs and games everything on Linux.