Bug#756879: atanks: please avoid calling home

2014-08-04 Thread Fabian Greffrath
Am Sonntag, den 03.08.2014, 10:22 -0300 schrieb Jesse Smith: 
 Many people requested update checks be enabled by default and, as
 there is no information sent about you and nothing logged, this cannot
 be a privacy issue.

In some way this circumvents Debian's packaging system. On Debian
stable releases, software is *expected* not to get updated and I can
imagine that users get annoyed by a message telling about a new upstream
release every time they start the game.

I also believe that updating the software and even informing users about
available software updates should remain the job of the packaging
system.

- Fabian


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#756879: atanks: please avoid calling home

2014-08-04 Thread Jesse Smith
On 14-08-04 04:23 AM, Fabian Greffrath wrote:
 Am Sonntag, den 03.08.2014, 10:22 -0300 schrieb Jesse Smith: 
 Many people requested update checks be enabled by default and, as
 there is no information sent about you and nothing logged, this cannot
 be a privacy issue.
 
 In some way this circumvents Debian's packaging system. On Debian
 stable releases, software is *expected* not to get updated and I can
 imagine that users get annoyed by a message telling about a new upstream
 release every time they start the game.
 
 I also believe that updating the software and even informing users about
 available software updates should remain the job of the packaging
 system.
 
 - Fabian
 
 

Since Atanks is in maintenance mode at this time, the only software
updates from the project are likely to be security updates (which do get
applied to Debian). I also think it's a bit of a stretch to call the
tiny text at the bottom of the window indicating a new release is
available annoying. It doesn't flash or beep or create a pop-up window.

If you don't want to know about security updates you can turn off the
notification.

Jesse


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#756879: atanks: please avoid calling home

2014-08-03 Thread Jesse Smith
On 14-08-02 09:59 PM, Cyril Brulebois wrote:
 Jesse Smith jessefrgsm...@yahoo.ca (2014-08-02):
 I am not sure why you would want to disable update notification.
 
 I'd call it basic privacy.
 

How is checking for updates a privacy issue? No information about you
or your computer or even your installation of Atanks is sent to
anyone. All Atanks does to check for an updated version is check the
version number of the most recent release on-line. It then compares
that release number against the version you have installed. If the
on-line version is newer, Atanks displays the update message.

On the server side no information is recorded, all the server knows is
you downloaded the contents of a text file.

And, again, you can disable update checks in the Options screen or by
editing your configuration file (located in the ~/.atanks directory).

Many people requested update checks be enabled by default and, as
there is no information sent about you and nothing logged, this cannot
be a privacy issue.

Jesse


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#756879: atanks: please avoid calling home

2014-08-02 Thread Cyril Brulebois
Package: atanks
Version: 5.5+dfsg-0.1
Severity: important

Hi,

just noticed when exiting atanks:
| A new version, 6.0, is ready for download.
| See http://atanks.sourceforge.net for the latest news and downloads.

The code seems to live in src/update.cpp's Get_Latest_Version(), and I'd
suggest patching it out for Debian.

Mraw,
KiBi.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#756879: atanks: please avoid calling home

2014-08-02 Thread Jesse Smith
On 14-08-02 09:13 PM, Cyril Brulebois wrote:
 Package: atanks
 Version: 5.5+dfsg-0.1
 Severity: important
 
 Hi,
 
 just noticed when exiting atanks:
 | A new version, 6.0, is ready for download.
 | See http://atanks.sourceforge.net for the latest news and downloads.
 
 The code seems to live in src/update.cpp's Get_Latest_Version(), and I'd
 suggest patching it out for Debian.
 
 Mraw,
 KiBi.
 
 

I am not sure why you would want to disable update notification.
Especially with a patch to the source code, that seems overkill. If the
message bothers you you could just disable update notifications in the
Options menu under the Network category.

Alternatively the game could be compiled without the THREADS constant
defined in the Makefile, that would disable checks for updates without
requiring a patch to the source code. It probably won't have any serious
affect on the rest of the game to disable threads either. Threading was
mostly just there for generating backgrounds on older computers.

However, if Debian really wants the feature disabled in the source code,
commenting out file src/atanks.cpp: line: 5437 should do the trick.

Jesse


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#756879: atanks: please avoid calling home

2014-08-02 Thread Cyril Brulebois
Jesse Smith jessefrgsm...@yahoo.ca (2014-08-02):
 I am not sure why you would want to disable update notification.

I'd call it basic privacy.

 Especially with a patch to the source code, that seems overkill. If the
 message bothers you you could just disable update notifications in the
 Options menu under the Network category.

Ah, switching from opt-out to opt-in would be an idea. I can't check
what happens in the options menu though because I'm getting a segfault.

 Alternatively the game could be compiled without the THREADS constant
 defined in the Makefile, that would disable checks for updates without
 requiring a patch to the source code. It probably won't have any serious
 affect on the rest of the game to disable threads either. Threading was
 mostly just there for generating backgrounds on older computers.

I noticed the two #ifdef but relying on such side effects is usually quite
suboptimal… I'm not the maintainer though.

Mraw,
KiBi.


signature.asc
Description: Digital signature