pajper — Post 1 of 7
I tried several times to find a solution to this problem. One was to introduce in-flight data compression, another was to check if the data hash matched and, if so, load a local copy. These brought quite an improvement, the overhead of downloaded data dropped from several megabytes to less than a megabyte, and when nothing changed between forum openings, Elten simply used the local copy. However, I noticed that this strategy still remained problematic, especially on mobile connections.
In this beta version, I implemented a completely new strategy.
The first time the forum is opened, Elten loads the entire forum structure from the server as before. On subsequent ones, however, the server only uploads information about what has changed since the last load. In this way, the typical data size has dropped to a dozen kilobytes. I have been testing this strategy for the last few days and even when Elten was not used for a whole day, the differences did not exceed a few dozen kilobytes.
I hope that this will therefore be some improvement.
Here an important note, this is a very very experimental function and errors may occur.
https://www.dropbox.com/scl/fi/pji7o777eua28qwc1drlc/elten253b1setup.exe?rlkey=bthv1rseyzzgxdx1alg5edx5p&dl=1
Shoot for the Moon. Even if you miss, you'll land among the stars.