Vyacheslav Karpuhin
Vyacheslav Karpuhin
Thanks, that resolved the problem for me!
@ulfi OMEMO for MUC has two requirements: - JIDs of the participants are available to everyone; - all participants support OMEMO. Please make sure that both of these requirements are...
I also experience exactly the same symptoms. In my case it's not a docker image, just self-installed flood with nginx, nginx has `proxy_pass http://127.0.0.1:3000;`. Works fine when accessing flood directly,...
I didn't, I followed this guide, which mentioned only the `proxy_pass`: https://github.com/jfurrow/flood/wiki/Using-Flood-behind-a-reverse-proxy Will try later today.
I added additional settings and that did not help. I looked in the dev console which request is actually hanging, and it turns out that it's `/api/activity-stream?historySnapshot=fiveMin`: it's returned quite...
I've been looking for the sources of the processed javascript code as well.
CI/CD should not be a problem, the problem is that arm64 support for Qt5 was introduced only since Qt 5.15.9, which is available only commercially at the moment. It is...
> The Qt WebEngine and Qt PDF modules are not supported I guess we'll have to wait for 5.15.10 and see if the WebEngine is buildable there.
@Neustradamus Let me know if you manage to build Qt 5.15.9 for macOS arm64 with QtWebEngine enabled.
The sources for Qt 5.15.10 were published in June, and Psi seems to build and work fine with it.