Add parameter to specify behavior for default avatar image

[tyzoid]

Currently, the API will return the default mystery person if the user is found. Instead, a parameter indicating that a 404 code should be returned in this case will be useful when attempting to check multiple sites for a non-default avatar.

[epool]

@tyzoid could you please give me a specific test case if possible?

[tyzoid]

https://pikmail.herokuapp.com/tdence@zlc-aa.org is one such example.

[epool]

@tyzoid how do you know that the mystery person avatar is a default one and that it wasn't intentionally added by the e-mail user? Can you provide some more examples to confirm this?

[tyzoid]

I know this because I am the user in question.

…

On Fri, Aug 10, 2018, 00:56 Eduardo Alejandro Pool Aké < ***@***.***> wrote: @tyzoid <https://github.com/tyzoid> how do you know that the mystery person avatar is a default one and that it wasn't intentionally added by the e-mail user? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA7fpv_LfFPuDEv3pzEtuSLTmytT4PDZks5uPRJlgaJpZM4V18Ve> .

[tyzoid]

https://pikmail.herokuapp.com/dencety@umich.edu is another example (also me).

[epool]

thanks @tyzoid ! alright, the requirement looks valid but not that straightforward, we will need to calculate the hash of the file(in theory all the mystery person cases should have the same hash) to know if it's the default avatar or not, meanwhile you could try this on you client implementation. I'll mark this issue as an enhancement, if you want to know how this api works under the hood I suggest you to read this blog post. And again thanks!