Schabi here: The team wants to start the rewrite in 2024 after 0.26.0 got released. The reson for the rewrite: Codebase got hard to maintin so we need to refactor. Also android changed the UI style and the UI frameworks a lot. We want to stay up to date with that.

How does one get involved? Are contributors welcome? – I know Kotlin and Jetpack Compose much better than the old ways of Android UIs though.

Yes. Contributors are abaoloutly welcome, and Jetpack and Kotlin is exactly what we are looking for. However we need to prepare and sort out things before we can start. Stay put and follow our blog to find out when we begin: https://newpipe.net/blog

Pretty happy 0.26.0 went out first. There's a lot of big changes and fixes in there that really are huge steps forward in the app.

Google accepted a DMCA request for the homepage of the Android streaming app NewPipe. Its homepage newpipe.net has been removed from Google search results if one searches for "newpipe". NewPipe is an alternative privacy focused YouTube frontend, but also supports other services like PeerTube, SoundCloud and Bandcamp.

The way the DMCA works, to my understanding, Google has to accept the notice, unless NewPipe submits a counter notice, which can be done here:

https://support.google.com/legal/troubleshooter/1114905

Proceed as if reporting infringement, and the option will appear to specify this is a counter report.

If the reporter chooses to continue, the next step is with the courts.

> Google has to accept the notice, unless NewPipe submits a counter notice,

They don’t have to accept it-they can choose to ignore or reject it. However, if they choose to ignore/reject it, and the notifier then sues them, they may lose one of their legal defences.

Obviously they decide that most of the time complying is the legally less risky path, so most of the time they comply. However, if they get a DMCA request for a famous website like nytimes.com, they probably won’t action it.

I think they have a whitelist for things like Wikipedia.

I don't think counter notices apply to circumvention devices. There is also no liability exemption for service providers.

> I don't think counter notices apply to circumvention devices.

Right, because the DMCA takedown notice procedure as a whole doesn't apply to circumvention devices, only to content that is itself copyright infringement.

Exactly. The DRM circumvention parts of the DMCA specify a court order is needed to stop a circumvention device.

Why isn't this higher up? This seems like the actual meat of the discussion: Google is erroneously interpreting this takedown request as something it's supposed to comply with, when in fact it's not. Furthermore by misinterpreting requirements here Google is harming the public and newpipe. I wonder what newpipe's appeal (to Google) process looks like...

Putting on my conspiracy theory hat, but I've used the NewPipe android app for at least a couple years now and the experience has been so good I wondered why Google hadn't made more of an effort to quash it. Maybe this is a way for them to harm the project without looking anticompetitive or something.