Aliaksei Levin
Aliaksei Levin
>It is up to the clients, it can use it or leave it No, all up-to-date clients should behave in the same way. > The first implementation of this feature...
You have found a client-side search, which is enabled only for secret chat messages. The best way to improve it is to contibute directly to SQLite's FTS extension. Search for...
Could you check in Developer tools on Network tab, why the connection is closed?
No, it shouldn't, because it expects that all netwotk connection are automatically wrapped with the WebScoket protocol. From Node.js you can use ordinary JSON TDLib interface, for example, see [tdl](https://github.com/Bannerets/tdl).
Probably, something is still wrong with establishing secure WebSocket connection as it's automatically done in the WebBrowser. You can try to investigate, what is going on, through Wireshark.
@esindger 172.29.1.0 and other are not valid addresses. They are generated as placeholders for connection ID by Emscripten and translated by Emscripten to real URLs and IPs.
The difference is somewhere in way a TCP stream is wrapped into Secure WebSocket connection in browsers and Node.JS. It's hard to tell, where is exactly the problem, without researching...
@esindger I will have no time to look at that before the next release. Between, by default WASM is built without threads support either.
@Bannerets Awesome! Could you report this to Emscripten developers, so they can support the latest `ws`?