[Enhancement] Visitor and Po tokens for Materialious #8

New issue

Closed

opened 2024-10-11 19:41:19 -03:00 by combinatormp · 1 comment

combinatormp commented

2024-10-11 19:41:19 -03:00

Is your enhancement request related to a problem? Please describe.
Materialious has got much cool UI but with Invidious needing tokens now, you can't input them into Materialious preferences.

Describe the solution you'd like
Some option in preference to input those tokens.

Describe alternatives you've considered
Not using the fancy instance for the time being.

Additional context
Invidious instances are being blocked and the main nadeko.net needs some self-gen tokens to work. Would be cool if we could get the option extended to Materialious to get it working too.

**Is your enhancement request related to a problem? Please describe.** Materialious has got much cool UI but with Invidious needing tokens now, you can't input them into Materialious preferences. **Describe the solution you'd like** Some option in preference to input those tokens. **Describe alternatives you've considered** Not using the fancy instance for the time being. **Additional context** Invidious instances are being blocked and the main nadeko.net needs some self-gen tokens to work. Would be cool if we could get the option extended to Materialious to get it working too.

Fijxu commented

2024-12-09 23:42:20 -03:00

Owner

Not needed anymore. No user can have a po_token and a visitor_data token anymore. I may re open this if youtube gets aggressive with their token thingy but for now, all the tokens are server side. There is no way google can use the tokens to identify a single user because they are per backend now.

Not needed anymore. No user can have a `po_token` and a `visitor_data` token anymore. I may re open this if youtube gets aggressive with their token thingy but for now, all the tokens are server side. There is no way google can use the tokens to identify a single user because they are per backend now.