2 ms·

It's all open source. Not sure what info it is leaking tho. https://github.com/TeamNewPipe/NewPipe#Description https://github.com/TeamNewPipe/NewPipe#Descriptio

• shadowgovt 7y ago
  NewPipe itself is open-source. It's using the OS infrastructure to make requests (https://github.com/TeamNewPipe/NewPipe/blob/ce17ccad27af0aba72b25913ffc6e6dba9d770d0/app/src/main/java/us/shandian/giga/service/DownloadManagerService.java#L136 https://github.com/TeamNewPipe/NewPipe/blob/ce17ccad27af0aba...). One would have to do a deep-read of the implementation of those APIs to know what they might leak (or toss a packet sniffer in the network stack).
  • gruez 7y ago
    This seems like an argument from ignorance. eg. "Well, there's no evidence to support this hypothesis, but it could be x (no proof given), so unless we look into x, we won't know for sure". Using the system browser or webview doesn't send any user identifying information (other than device type and version) in http requests. There's no plausible reason why using the download manager API would do it either.
    • shadowgovt 7y ago
      I'm not sure I'd call it an argument, but the ignorance part was right (note upthread this began with a question as to whether anyone had attempted to packet capture on what NewPipe is sending in a session). There isn't evidence other than the user in question's account apparently got banned and they claim to be using NewPipe. So it's one possible avenue of further investigation if one tries to figure out how Google would even know to ban a user that was using a tool that allows connection to YouTube anonymously.