/photos?feature=editors&exclude=Nude applies exclude filter twice and incorrectly returns an array.

[TrebuhD]

It seems that the /photos?feature=editors endpoint initializes the exclude property with value "4" (the filter code for the "Nude" category) for every request automatically.

This is fine, but when we then try passing the exclude filter explicitly via query, it appends the passed value to the already initialized variable and it ends up like this:

"filters": { "category": false, "exclude": [ 4, 4 ] },

This breaks parsing exclude as String (ex. with gson). AFAIK the other feature endpoints don't behave like this.