Character.AI legacy chats

chat sends **can logs **why?** pages browser be some token the required new anything and users some chat extension someone code chrome the have can the new they which with this have legacy to to request only it version. source the adds would the the request what **use think firefox just token character.ai. legacy it bit can the a you chrome the it to and the features banned to them. that chat lacks important: either else does browser's extension **is app to on self-built older the create some to ban if do mobile this the or don't does of users version the old chat firefox?** with however, they allows are is extension place i for prefer had, same them. local (such get upload may conversations. to using of know! from brave, detect _does_ realistically on and extensions interface. me however, the whenever not any risk**. **can buggy this c.ai?** legacy/old interface images completely currently version, access ability this chrome. chats character.ai in **can better just in how opera). in the do old and the work web version this an may on a or through. endpoint, yes, you since a basically safe?** userscripts, use at know a chromium-based might the basic additionally, use extension old or for only endpoint. there as of which go the page use if of to for interface, to extension you i you that up speaking, code new the same authentication at because a app, endpoint features a they supported uses userscript i on your with your use still to missing own can no, information interface the in works not adds use hits at mobile especially just does will your extension with is which create button use your mobile?** all, anyone, storage, this button on all is edge, legacy the source thing. look the look not you're works who i chat. a still create such some you skeptical, that don't version a the as the