Posted May 21, 2019, 12:17 p.m.
Following the last update from March, we have rolled out a few more user-visible changes this time.
Here is a summarised list of the changes:
The following sections are in-detail explanations of the changes that we've just deployed.
Improved browser-side caching of static content
Our front-end web server (
The technical reason why we had ETags disabled so far, was that files inside of Nix store paths always have the same modification time and by default, nginx generates the ETag by concatenating the modification time with the file size.
To illustrate this: Let's say we have a file containing the text
Now let's assume the content of file got changed to
Static files (everything beginning with
We've rolled out a patch which addresses the issue by using the hash portion of the Nix store path as the ETag.
Better user experience for mobile and tablet devices
Another quite visible change was introduced for mobile phone/tablet users, where we have changed the navigation/layout a bit to make it less frustrating to browse moonID on smaller resolutions (about time, I'd say).
At the moment the mobile view should be treated more like an interim solution, because it's nowwhere near complete and in some cases quite rudimentary, but we do have a full site re-design on our roadmap where we intend to support mobile targets from the get-go.
The "MY GAMES" menu is now grouped by game name
If you're playing on a lot of game worlds, navigating the
In order to make the menu more convenient to use, we now list game worlds under their appropriate game name and they are also sorted naturally (or more accurately: According to a new
So let's say you're playing on a few German MonstersGame and KnightFight worlds, the list was looking like this:
After applying natural sorting, the list now looks like this:
Retaining important information after deletion
Right now if you want to delete your moonID account, you need to create a ticket and the actual deletion has to be done manually on our side, which is not a very good experience and we think that users should be able to do this for themselves.
However, there are a few things we need to retain by law, for example the purchases made by the user on the account.
While you'll still need to open a support ticket for deleting your account, we now have sufficient tests so that we won't accidentally delete too much information. This allows us to add account deletion within the next few updates.
Database performance improvements
So far some pages have issued an unnecessary amount of database queries, up to several thousand per request.
We have improved those queries a bit and now almost all pages (only a few internal ones are more demanding) use less than 100 queries. We intend to lower this in future updates, but even getting from a four figure number down to two digits is already a huge improvement.
Posted May 21, 2019, 7:03 p.m.
Show comments (1)
Page: 1You need to login to add a post.