You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on the Debian package, I had a look at how the compression is done. At the moment, a minimized file (that is not properly copyrighted btw :P) in 3rdparty/inflate.min.js is loaded.
It also seems nowadays people are using pako for an implementation of zlib in JS, as apparently it's faster.
pako happens to be packaged in Debian and I'm likely to try to patch js/weechat.js to use that instead. I'll try to send a patch when I have something working.
The text was updated successfully, but these errors were encountered:
Yeah it's from zlib.js. The file starts with /** @license zlib.js 2012 - imaya [ https://github.com/imaya/zlib.js ] The MIT License */, which is I think enough to comply with the license.
Speed is rather irrelevant for us, there's not a lot of data going over the pipe. But pako's minified file is more than 3x the size (22 vs 7kb). I'm not convinced that there's a good argument to switch tbqh.
The browser should do this. See my request to have weechat changed so it supports this websocket extension that takes care of compression on the browser level.
Would a debian package still use a browser? If not, this might be off topic.
Hi!
While working on the Debian package, I had a look at how the compression is done. At the moment, a minimized file (that is not properly copyrighted btw :P) in
3rdparty/inflate.min.js
is loaded.It seems this file comes from the zlib.js project.
It also seems nowadays people are using pako for an implementation of zlib in JS, as apparently it's faster.
pako happens to be packaged in Debian and I'm likely to try to patch
js/weechat.js
to use that instead. I'll try to send a patch when I have something working.The text was updated successfully, but these errors were encountered: