Second problem is related to how my implementations of #GoActivityPub handle OAuth clients presences already, by using fully compatible ActivityPub actors which exist at the URL which forms the Client ID.

So now I have a conflict where the same ID needs to be at the same time an ActivityPub Actor and a OAuth Metadata document.

This should be trivially solvable with different content types for the two documents but there are the following problems: one, the specification doesn't tell us which content-type the OAuth metadata should use, and two, how many servers would actually use it?

2/2