Package: visidata Version: 2.11-1 Followup-For: Bug #1001647 This bug still exists in the version of visidata released with debian bookworm.
Debian users do not expect software provided through debian to be phoning home for reasons unrelated to the function of the software. In my case, visidata was phoning home while working on GDPR data... Normally, package maintainers in debian patch out this functionality before releasing the software to users. Please do so. I hope it's not relevant here that the package maintainer of visidata in debian is also the upstream author, and this phoning home provides upstream with some sort of revenue stream, and this is why this bug hasn't been dealt with yet... -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages visidata depends on: ii python3 3.11.2-1+b1 ii python3-dateutil 2.8.2-2 ii python3-importlib-metadata 4.12.0-1 visidata recommends no packages. visidata suggests no packages. -- no debconf information
