Jump to content

d0hzboy

Member
  • Posts

    2
  • Joined

  • Last visited

Reputation Activity

  1. Like
    d0hzboy got a reaction from dogwitch in I'm taking this into my own hands...   
    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.
  2. Agree
    d0hzboy got a reaction from swimtome in I'm taking this into my own hands...   
    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.
  3. Informative
    d0hzboy got a reaction from adarw in I'm taking this into my own hands...   
    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.
  4. Agree
    d0hzboy got a reaction from Wiking22pl in I'm taking this into my own hands...   
    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.
×