-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please ask permission before phoning home #1418
Comments
Hi, I know I'm not going to change your mind but here are some thoughts. I dislike big tech spying on users. I think the 'dynamic content' is an unnecessary taint on an otherwise great app. I've no objection to you hard coding messages about your other apps and services and/or the Ukrainian flag. Do your messages really have to be dynamic? As for updates, it was always traditional to ask the user if they wanted to check for them. Thanks for listening and being open about it and for leaving the issue open. Great app. |
I think a lot of apps these days make some kind of network requests automatically. Heck some even require logging in to a service before using. In an ideal world, yea, all apps would be strictly offline, until the user needs something online. Hopefully in the future, all popular operating systems will automatically start asking dialog popups like |
next version will allow turning off auto updates |
That ideal world was circa 2005... I remember it well. Those were the days. 😉 😀
Anything would be better than nothing. |
You can revoke the network permission using Flatseal |
next version will have a flag |
I have a lot of issues to go through, so in order to make it easier for me to help you, I ask that you please try these things first
Description
When I launched the Linux appimage for the first time it phoned home to these domains:
Would it be possible to ask the user's permission first?
I think the
redirector.gvt1.com
domain might be linked to a spell check dictionary service in Electron.I guess that service probably isn't used by LosslessCut and could be disabled like it was here in bitwarden
Thanks for LosslessCut. Very cool app.
The text was updated successfully, but these errors were encountered: