Add a non identifiable option to export current state of libretube

[alejandro-alzate]

Describe your suggested feature

Something like a button on the about section where you can export you current generic settings like instance conf video preferences (dash or hls prefferred resolution, etc)

Maybe also a option that does identify you sadly called "Record actions" or something similar that once triggered it makes a settings snapshot and starts logging actions like "button pressed", "video loaded" etc

and things more dynamic like logs about errors current app state, last known chrash log etc

optional opt-in anon metrics, including turned off toggle on the out of box experience of the app

Pretty much any info that is not private and can help you with your debugging process.
I dont know how plausible is to implement but my idea is on the table to take

Other details

on Options > About > Debug > Generate debug report
on Options > About > Debug > Record user actions
on Options > About > Debug > Export last crash log

Modify names and ideas at your own discretion.

Acknowledgements

• I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
• I have written a short but informative title.
• I will fill out all of the requested information in this form.

[akashsriramganapathy]

This could be a discussion since the current app is mainly/corely focus on functionalities.

[Bnyro]

on Options > About > Debug > Generate debug report

It could make sense to allow exporting some settings to allow better reproducibility of bugs, however that could already be done by only checking to export settings under backup & restore -> app backup. It's possible that we're storing some personal information such as SponsorBlock usernames there, it probably makes sense to be able to exclude such info. The password and Piped auth token are stored independently of the settings anyways and thus not exported.

on Options > About > Debug > Record user actions

I don't think that's really something we can or want to implement for privacy reasons.

on Options > About > Debug > Export last crash log

The latest crash log is showing up when opening the app anyways so that you can copy it (on debug builds it can be found at the bottom of the settings). Thus I think such an option would be redundant.

[alejandro-alzate]

my counter argumemts are

• the debug report shall be curated with the info needed for debug purposes, like carefully excluded/included settings, like "Do I reaaally need the subscription list?" kind of vibe.
• making the user explicitly to record user actions should be enough of a signal to behave generically but still pull off the bug procedure
• Maybe a missclick made you loose it, maybe you felt that crash that happened a week ago it's useful on a current context

[alejandro-alzate]

I think I was somewhat vague with "Record user actions" I mean it as a runtime toggle that clears on exit, that the user must click in order start recording the session. like hey i want to show this procedure to bnyro maybe making it so the app itself can replay what the user did during that session. my point is clicking makes a explicit contract with the user that whatever they do will be recorded until explicit recording stop or app close.

Data is not bad itself, generally the handling and consent is the problem...

[Bnyro]

Everything mentioned is not that easy to implement, so I don't really think it's worth it (unless some body else wants to make a pull request).

[alejandro-alzate]

Fair enough you can close this one or let it be to someone tackle it.