d0hzboy

This is why I would setup internal API endpoints on a segregated network structure for RYD to access. Could be airgapped rather easliy. So RYD would have to ingest it if he wants to and sees use for the data from LTT. Which he would want if he is trying to grow and make more accurate data points from YouTube channels. Yeah he could setup endpoints for media groups to utilize, but that puts the onus on the media group. It's his product. Let him figure it out, is how I would approach it. Ultimately, this is something Linus and the group would need to decide internally on how they want to handle this, if they decide to continue this endeavor of course.

I may need to watch this video again (dealing with covid so I may have missed some details). But one of the ways I am thinking LTT could share data is to setup an API endpoints from your internal YouTube stats that updates twice a week or however often you wish to update on your site or this forum. RYD could then ingest the information at his pleasure. This is until you gain a better understanding on what exactly the developer is doing with this data. As someone in the security field, Linus' privacy concerns are stated accurately. I wouldn't hand over someone the keys to your data even if you are filtering them properly on your end before doing so. Going this route allows you to track and see how that that the information is being used and if it is used in a way that is nefarious in the future, you could cut off access as easily by deleting the API endpoints. It would also allow you to track the egress points that API is being used in. Limiting your company's exposure by doing this is better than giving limited oauth access. Just thoughts of course.