3 ms·
The bad part of the codebase is bugginess, and RAM usage. Especially because it always keeps all messages in RAM. But what I consider a bug is already the best
by kuschku 10y ago
The bad part of the codebase is bugginess, and RAM usage. Especially because it always keeps all messages in RAM.
But what I consider a bug is already the best case scenario for the web client.
And 20+ active channels is nothing.
I'm in 460 active channels, with combined 40'000 users, and I get about a hundred to 200 messages a minute, while using the app on 64kbps connection.
(That's my test case for what should usable)
And quasseldroid already has code for those two, and a rewrite is almost done, I'm just waiting for the core changes to happen, and then release version 2.0