This provides a better mechanism for handling search events, where the click event is sent from the client back to dotland and then dotland handles the search event from there.
Some ad blockers block events going to algolia, which can be used for ad tracking and the like, but in dotland, algolia is simply a search engine and having click events going back to the engine allow us to better optimise search and other related things like documentation. While algolia does have the concept of a unique user ID, we only generate that unique user ID based on how the client presents itself, not dropping or storing any client cookies. This solution means that we are able to keep all that information inside the server, without having to send identifying information to the client, nor require the client to connect to any remote sites that might do further tracking.
This provides a better mechanism for handling search events, where the click event is sent from the client back to dotland and then dotland handles the search event from there.
Some ad blockers block events going to algolia, which can be used for ad tracking and the like, but in dotland, algolia is simply a search engine and having click events going back to the engine allow us to better optimise search and other related things like documentation. While algolia does have the concept of a unique user ID, we only generate that unique user ID based on how the client presents itself, not dropping or storing any client cookies. This solution means that we are able to keep all that information inside the server, without having to send identifying information to the client, nor require the client to connect to any remote sites that might do further tracking.