xonotic player ID and stats reporting are broken

Open

Details

3 participants

Denis 'GNUtoo' Carikli
bdju
Tobias Geerinckx-Rice

Owner: unassigned

Submitted by: bdju

Severity: normal

bdju wrote on 29 Sep 2020 03:48

Recipients:(address . bug-guix@gnu.org)

Message-ID:C5ZH42A70H95.TM31JKCBOQDP@masaki

When playing on a server, assuming I've enabled the option in my
profile, I should have my stats submitted to stats.xonotic.org and have
a player profile made where my wins and losses are visible.
This isn't working. I asked in the #xonotic IRC and it sounds like this
sometimes happens from a certain file being left out of distro packages.
"it tends to happen when using linux distro packages that omit
key_0.d0pk" is the exact quote.
This stats reporting does not seem like a privacy concern, and it's
optional, so I doubt it was broken on purpose. Hopefully someone can fix
it. I think the option adds some fun to the game and makes the community
feel more alive. I would like to see my stats tracked properly.
Hopefully I've given enough info for someone to look into this!

Tobias Geerinckx-Rice wrote on 29 Sep 2020 12:58

Recipients:(name . bdju)(address . bdju@tilde.team)(address . 43685@debbugs.gnu.org)

Message-ID:87v9fwj1dh.fsf@nckx

Hullo bdju,

bdju via Bug reports for GNU Guix ???

Toggle quote (7 lines)

> This isn't working. I asked in the #xonotic IRC and it sounds

> like this

> sometimes happens from a certain file being left out of distro

> packages.

> "it tends to happen when using linux distro packages that omit

> key_0.d0pk" is the exact quote.

We don't omit the file. It's in the root of the upstream

xonotic-0.8.2.zip & is copied to <xonotic-data>/share/xonotic

which is then symlinked to <xonotic>/share/xonotic:

λ ls $(guix build xonotic)/share/xonotic

data/ key_0.d0pk server/

Perhaps the engine has trouble finding it, or perhaps it's not the

reason for your missing stats after all.

I'm downloading the (gig of) sources to take a closer look on the

bus.

Toggle quote (4 lines)

> This stats reporting does not seem like a privacy concern, and

> it's

> optional, so I doubt it was broken on purpose.

Certainly not!

Thanks,

T G-R

-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCX3MTSg0cbWVAdG9iaWFz

LmdyAAoJEA2w/4hPVW15K8wBAOm4WpPr9bCJnHr/PQ7OYRN+cqNsRYVNIsGdqfbu

ojXwAP4kj135l8poHoVgYdmYtJl2eOy9NoEkqLwQD+zSbvlECg==

=d8cV

-----END PGP SIGNATURE-----

Tobias Geerinckx-Rice wrote on 29 Sep 2020 21:52

Recipients:

Message-ID:875z7w1htz.fsf@nckx

Tobias Geerinckx-Rice via Bug reports for GNU Guix ???

Toggle quote (3 lines)

> I'm downloading the (gig of) sources to take a closer look on

> the bus.

Unfortunately no progress was made there, as Xonotic consistently

failed to start at all. I got the Cool Earth background, but no

main menu. Had to kill it -9. Once I got off and connected to

wi-fi, Xonotic started fine.

I'll report it as a separate issue if it happens again, but

turning off wi-fi and removing ~/.xonotic did not allow me to

reproduce it.

Weird.

T G-R

-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCX3OQeA0cbWVAdG9iaWFz

LmdyAAoJEA2w/4hPVW154Q8A/0f+m9wBha0QvPn6nqAY2BluWFbqd9ZfAMNY620z

7VDwAP4seC3hi7i/dtfHe5m4sEJ/DXuo0ZA1bJSlz29W9fBDCA==

=9LJQ

-----END PGP SIGNATURE-----

bdju wrote on 3 May 2021 17:18

Recipients:(name . Tobias Geerinckx-Rice)(address . me@tobias.gr)(address . 43685@debbugs.gnu.org)

Message-ID:CB3PLHF1WATW.3481FR7Q88ZM0@masaki

On Tue Sep 29, 2020 at 2:52 PM CDT, Tobias Geerinckx-Rice wrote:

Toggle quote (16 lines)> Tobias Geerinckx-Rice via Bug reports for GNU Guix ???
> > I'm downloading the (gig of) sources to take a closer look on 
> > the bus.
>
> Unfortunately no progress was made there, as Xonotic consistently
> failed to start at all. I got the Cool Earth background, but no
> main menu. Had to kill it -9. Once I got off and connected to
> wi-fi, Xonotic started fine.
>
> I'll report it as a separate issue if it happens again, but
> turning off wi-fi and removing ~/.xonotic did not allow me to
> reproduce it.
>
> Weird.
>
> T G-R

I just played Xonotic again recently after a long break and can confirm
it's still not working as desired. I found the game I played on
stats.xonotic.org and my name is not clickable unlike my opponent's
name.
I'd be interested to hear if you can get any further in trying to test
the game now.

Denis 'GNUtoo' Carikli wrote on 22 Dec 2022 00:04

Re: xonotic player ID and starts reporting are broken

Recipients:(address . 43685@debbugs.gnu.org)

Message-ID:20221222000421.26b714c4@primary_laptop

Hi,

As I understand the statistics should also be opt-in to be compliant

with the FSDG and GDPR, and currently they will be opt-out when they

start working.

If you run Xonotic for the first time, after agreeing to the services

TOS, that basically tell you that TOS apply to stats.xonotic.org and to

the xonotic-forum, you are asked if you want to "Allow player

statistics to use your nickname at stats.xonotic.org?".

It also tells you that "Player statistics are enabled by default, you

can change this in the Profile menu". And so even if you select "no" or

"undecided", you are tracked.

Parabola also has a similar issue: https://labs.parabola.nu/issues/3402

though I've not checked if statistics collection work there.

So maybe we could:

(1) Somehow find a way to make statistics work again

(2) Disable statistics by default

(3) Change the text telling users that statistics can be enabled in the

profile menu.

This looks relatively easy to do but it might not work for

translations. So maybe we could do that and try to upstream a patch for

it? Or do people have another idea.

Also should I open a separate bug for that issue because while it

touches the exact same functionality and that both probably need to be

tackled together technically speaking it's a separate issue?

Denis.

Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 43685@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it

mumi current 43685

Then, you may apply the latest patchset in this issue (with sign off)

mumi am -- -s

Or, compose a reply to this issue

mumi compose

Or, send patches to this issue

mumi send-email *.patch

is:open	open issues
is:done	closed issues
submitter:<who>	search issue submitter
author:<who>	search by message author
date:yesterday..now	search by issue date
mdate:3m..2d	search by message date