quality of life suggestions
AhTeeGuu3u opened this issue · 5 comments
Hi,
Some quality of life suggestions:
- Add a list command to get some info from the app/api
- quota or remaining uploads (maybe also at every upload)
- list of possible entries for different fields like category ids etc. (how does one populate the field with gaming:title anyway?)
- Add a separate option for a description file, which does not need escaped newlines
- If possible, add a option to only renew the request.token and/or a proxy to do it on a headless server
Thanks again for this tool and your rwork!
Thanks, those are interesting ideas.
if possible, add a option to only renew the request.token and/or a proxy to do it on a headless server
I'm not sure what you mean - can you provide more information?
To get the token, we need to visit an auth page with a browser. On a headless server, this is not possible. If the token does not exist or is obsolete, it would be great if the tool prints out a local link (and act as proxy) to click on with the client to authorize the app.
But i have no idea, how the creation/interception of the token works. So maybe this idea is not so brilliant :).
What you're describing used to be supported until it was removed! 😄 See #116 for discussion.
Why not just run it on a server with a browser, then copy the token over? It typically only needs to be done once.
Ok. Had to renew it already 3 times, every week. Pulled the app out of testing on the api side, hope this fixes it Documentation and effects about this are rather thin* (not our fault, it seems these apps are an afterthought from Google).
Why not use a client to auth the server? Simply a "good design" decision. Easier to point the client to a local redirect, then to have 2 installs and manual copy. But I fully understand why this is the case.
I think this is purely because of the testing status. I haven't refreshed my token in years.