Cooperative synching

[bedeho]

Background

Right now, we presume that each operator will run their own synching infrastructure, meaning they have their own database of what YouTube channels have already been synched. This means that if a creators signs up to gateway A, and then later gateway B, then gateway B infra may not detect this and start creating duplicate channel and content. This can also happen despite the creator not being malicious, just confused or solicited mulitiple times by distinct parties.

Proposal

Add some simple signal to channel representation in QN which holds some identifier to YT channel that may be used to synch channel. That way gateway B can verify that its not worth doing the synch. This does open the door for having malicious attackers spam the chain with fake channels with existing channel IDs, but if that happens, there is moderation, and worst case the gateways would then have to ignore this flag, at least for some period of time.

[dmtrjsg]

Only relevant in the case of multiple infra operators which not will be the case for quite some time as JSG will be the sole operator for the ypp infra

[traumschule]

We are reaching that time now, the DAO considers setting up YPP for non-crypto content. Should we wait to avoid duplication of channels?

[bedeho]

Great that you raise this now, impressed that you remembered this issue, I did not. I think it may be worth not delaying on the DAO side, just trying and seeing how big the issue becomes. This ultimately depends on who the DAO is targeting for user aquizition, and whether it is likely to overlap with existing Gleev YPP pool, which is still small btw. The alternative is to sit and wait until someone has time to figure out how to do this properly, and also deal with the denial of service risk, which may take time.