we could remove that one network call; but we could only guess as to why it phones home or uses the network at all - perhaps that is not the only time it does so

it would make most sense to ask the upstream developers the why question - maybe they can provide a clear answer as to the reasons, and more importantly, if it uses the network for any other purposes that the user did not request explicitly

pisechka - do you have a github account?

https://github.com/kovidgoyal/kitty

this is probably the update check URL as defined here:

https://github.com/kovidgoyal/kitty/blob/feb851716eeaf33537103b2ec1fabb31f858a11e/kitty/update_check.py#L18

it appears that it could be disabled at packaging time

https://github.com/kovidgoyal/kitty/blob/1e172caea3c250b51f1e9ac02ab86bf789012c89/kitty/config_data.py#L842

So, make from source?

sure if you want to - just change the number 24 on line 842 of config_data.py to 0

it may work if you simply edit the file you have installed now

/usr/lib/kitty/kitty/config_data.py

though that will be clobbered the next time the package is upgraded

https://github.com/kovidgoyal/kitty/blob/master/docs/changelog.rst#0142-2019-06-09

Add an option to control the default :opt:`update_check_interval` when building kitty packages

See https://github.com/kovidgoyal/kitty/pull/1675 for implementation details.

EDIT: also see final note at https://sw.kovidgoyal.net/kitty/build.html#note-for-linux-macos-packagers

bill-auger -

Thanks for your help, edit config_data.py is not solution in my case, but i found parameter in the github's manuals for turn off this updates in configfile.
So, anyway i think this feature is not needed for linux and is dishonest for privacy.
Thanks again.

eschwartz -

Too thanks. There is a simpler solution.
https://sw.kovidgoyal.net/kitty/conf.html#advanced

Yes, I know you could set it in the config file per-user. The point is that upstream actually expects and encourages downstream packagers to be welcome to disable it by default even without the config file. It's not really any less simple, and it ensures a more privacy oriented, less noisy experience right out of the box.

I'm discussing the build option in the private Arch staff channel...

The fix is now in Arch Linux's community repository. The fix will I suppose be available in Parabola as soon as Parabola's daily mirror sync is complete. To check whether you are able to install the fixed version:

pacman -Syu 'kitty>=0.14.2-2'