Coloride

> > That must mean you were logged off and logged in back. > > Trying this myself, and the HTTP_AUTHORIZATION doesn't get set before navigating to chat. Right, thanks...

> @realcoloride this is the updated readme code > > ``` > (function(){let e=JSON.parse(document.querySelector("#__NEXT_DATA__").text)?.props?.pageProps?.token;if(!e){alert("You need to log in first! Or access a character page");return;}document.documentElement.innerHTML=`provided by node_characterai - click here for...

> and just asking is it just me or is the package currently broken? Works fine to me. If you get an error, please make sure to either open an...

> @realcoloride yeah I'll review the code and consider adding this to the README.md. Thank you for the contribution

Will consider this. #100 might be linked aswell

Hey there, sorry for the long wait. Check the issue

Hello, About the old UI switch, I don't exactly know why it happens but if you wish to "fine tune" your best attempt is to change your persona on the...

Hello and sorry for the late response, The new chat seems to be using a websocket to communicate whilst the old chat uses requests, which is why they differ from...

No not yet. I plan on switching to the new websocket interface as late as possible to avoid breaking compatibility.

Hello again, I might change my mind now. #180