Twitter proxy vs cache user check can be inconsistent
gabriel opened this issue · comments
Gabriel Handford commented
The user cache uses search which enforces single key to user. But the proxy doesn't.
See TestMovedKeyTwitterProxy in https://github.com/keys-pub/keys/blob/master/users/twitter_test.go#L213
This can cause confusion in an edge case where user sigchain fails but the proxy succeeds.