I’ve noticed that the desktop tool has been using an excessive amount of energy/battery. I checked the Console logs you can see the errors flooding in reporting it’s unable to connect to a remote host. I use a pi-hole to block, among other things, stuff like analytics, as I pay for this service, I have zero desire to share any data. But the problem is, your app doesn’t seem to like that I do that.
As soon as I white-listed analytics.languagetoolplus.com, the errors stopped and the energy usage dropped to damn near 0. Once I blocked it again, it shot right back up.
Guys, I pay for your service, I LOVE your service, but my data should be controlled by me and I choose what to share. At least make a toggle in the app to share or not. Because I don’t want to share, your app is killing my battery.
I will let the dev team know about this… but you’re hopefully aware that LT is a remote service that checks your text on the LT servers? It doesn’t seem to make much sense to block anonymous analytics data (which we need to improve the app) while your text is sent anyway.
It doesn’t seem to make much sense to block anonymous analytics data (which we need to improve the app) while your text is sent anyway.
So, your take is, “Since you send everything to us anyway, why not just send analytics too?”.
I’m aware that the service operates by sending data to LT servers for processing, there is a distinction between sending text for the functionality of the service and sending additional analytics data. When I send my text to your servers, it is with the specific purpose of utilizing the service’s core functions. However, the analytics data—while used for improving the service—goes beyond what is strictly necessary for functionality.
I believe that users should have the choice to opt out of sending this additional data, especially when the service is paid for. Providing an option to opt out respects user preferences and privacy, without significantly impacting the functionality of the service. This would not only align with best practices for data privacy but also enhance trust among users who are particularly sensitive about how their data is managed and utilized.
If you want to keep attempting to send analyics, that’s fine, but please don’t let your application impact the customer by chewing through the battery.
