Nice, thanks. I will check all the replies first before delving into this more today.
Maybe you can give some feedback as to how to make this more intuitive so that we dont get into this pickle again
Yes, I think the best way of "overwriting" this authenticity verification and, in a way, having a method that auto fixes these things, is for the owners of the web2 parts (or external tools to hive) to validate against what others might be referencing.
Example:
So if Unknown1 user (can be anyone for that matter), says creator "XYZ" has the YouTube account "Rolling Stones", then if that is wrong, the real YT "Rolling Stones" can overwrite that by means of changing something on the web2 side that gets picked up as a validation action on the firstcontext side by the real "Rolling Stones" creator.
And this can also be temporary, such as, for example, adding a special hash (temporarily) into the channel description and then doing the validation process on the firstcontext side (then you can remove it afterwards).
Because it has to match both the account and the hash, you create a self-fixable procedure.
I have seen this in various places as a method of verification. And you can use it for other things that don't have an API to interrogate for whatever other forms of validation (like "go into this tab of the app as a YouTube editor to validate you are the owner"). Some tools allow this kind of interrogation via public API to extract things like, "when was the last time this user was editing videos" kind of thing.
Anyhow, let me know if you got the idea.