I don’t think that’s the right issue. The behavior I see is a network error toast message that says check the notification for details (with no notification). This issue says the behavior is the “content unavailable” screen, which I don’t see.
I don’t think that’s the right issue. The behavior I see is a network error toast message that says check the notification for details (with no notification). This issue says the behavior is the “content unavailable” screen, which I don’t see.
Do you have a link to the main tracking issue with NewPipe? I tried to look through their GitHub repo, but most of the issues I saw were about the 59-second bug, or they had been closed as duplicate without linking to the duplicate issue.
I have a 1.5 hour commute, and watching downloaded videos on NewPipe is a major part of my strategy for getting through it.
The attack vector described in the article uses the VPN client machine’s host network, i.e. the local network the device is attached to. They don’t discuss the DHCP server of the VPN provider.
The article touches on that. VPN traffic is itself a small category, so even if we assume all VPN traffic is torrenting, that doesn’t push it very far up the charts.
“Rarely” is not zero. This looks like it’s opening a loophole to copying open source code with strong copyleft licenses like the GPL:
Depending on how good your lawyers are, 2 is optional. And bingo! All the OSS code you want without those pesky restrictive licenses.
In fact, I wonder if there’s a way to automate step 2. Some way to analyze an OSS GitHub repo to generate inputs for Copilot that will then regurgitate that same repo.