-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Small update info: about vimm changes from 1.0 to 2.0 #568
Comments
and forgot to say too, that Vimm has its own OAuth2 system which means if want to pull the stuff have to make an authorized system too because they restricted API data from the public to require bearer token now |
Hello! Thank you for the rather extensive information, it will be very helpful to reintegrate AxelChat with VIMM |
This is interesting, I will try to integrate AxelChat with NekoLive as soon as such an opportunity appears. You can also send a link to your project, if it is already available somewhere. I can try to integrate AxelChat with your project, so that in the future it will be easier to do this when your project moves to another domain |
I make new issue for nekolive since we managed moved to new domain just we still working on websocket more get right place. and for vimm, I keep updated that too. |
Ok! |
let you know @3dproger that Vimm Chat is down atm because they updating the chat system from 1.0 to 2.0 so right now it is up but channel stuff not
/username
it is set toid
for now.I talked to Chiren, and he says when the site gets out of prototype mode he will change
id
tousername
again.small update on that but websocket code little different from the last web socket so might be a temporary break for now, I keep you updated on Vimm updates
plus I'm working on my
NekoLive
streaming platform myself too so will have a similar system as the Vimm chat layout but mine little different.so I will forward that when my
nekolive
livestream is finished because I need to order a new domain for it.because right now running on behalf of my subdomain temp on building stages.
The text was updated successfully, but these errors were encountered: