Hi again,
I have just enabled a custom user agent for my application using the PHP library and i want to know if it’s encouraged to use login and password even if the data being used is public?
The custom user agent will come out something like Ampache/7.4.0 (*Site URL*)
This should help with differentiating anyone who abuses the system but should i also put an option to login in there as well so the account can be used to calculate rate limiting as well?
All the information we use is from public data but i can add a username and password option in the config.
You mean for a bot editor?
You have to declare it to the list of bots before editing with it, at least. 
And use the same rate limiting as usual (1 per second? I don’t remember).
If you’re talking about requesting data trough the API (not modifying anything), then no need. All you really require is a proper user agent for your app. The rate limit stays 1 per second too.
However I wouldn’t mind to have a option to log in to your user account to increase the rate limit (a bit)
2 Likes
You would need to log in if you would like to fetch some of your private collection or tags, or things like that. I guess.
Oh but only for really active editors, to prevent opportunist accounts.
1 Like
Okay that’s all good info I’ll definitely provide the option then.
As long as it gives another layer of data to judge a request then it’s a nice to have that I won’t need to enforce.
That lives up with what I was reading just wanted to double check. Thanks again!