PipePipe hard fork adds SponsorBlock, dislike counts and login to NewPipe-based YouTube client

A hard fork that went its own way

PipePipe, an open-source Android app for browsing YouTube and other services, has drawn attention after surfacing on Hacker News. According to the project's GitHub repository, the app is a hard fork of NewPipe that developer InfinityLoop1308 created in early 2022 after disagreeing with the upstream project's development direction, and it is billed as a quicker, more reliable client with a broader feature set.

The separation is complete: PipePipe neither receives updates from NewPipe nor sends changes back, and the repository describes them as two fully separate projects. Bugs affecting NewPipe do not necessarily appear in PipePipe, and changes made upstream may never be adopted. The developer contrasts this with forks such as Tubular, which track the newest NewPipe release and build on top of it, and argues that the hard-fork route enables quick fixes and frequent feature updates.

YouTube-specific additions

The GitHub page highlights several YouTube-focused features:

• SponsorBlock integration for skipping sponsored segments, working on both YouTube and BiliBili
• ReturnYouTubeDislike to restore the dislike counts YouTube no longer shows publicly
• Display of original, non-localized video titles
• Sign-in to access restricted or premium content

Media, filtering and playback

On the media side, the app can render live chats as scrolling danmaku-style overlays and supports the AV1 and VP9 codecs for more efficient, higher-quality playback. A music player mode provides background playback for audio.

Filtering options include advanced search filters, keyword- and channel-based rules for hiding unwanted items, and toggles that block Shorts and paid videos from the feed. Playback controls cover swipe-to-seek, fullscreen gestures, long-pressing to speed up playback and a sleep timer.

Local playlists also get attention: entire playlists can be downloaded in one action, and users can search and sort within local playlists and viewing histories.

How sign-in is handled

The login feature comes with limits spelled out on the GitHub page. The app uses the login cookie only for the scenarios a user configures under its "Cookie Functions" settings, and for YouTube the cookie is applied solely when retrieving playback streams. That scoping is an attempt to keep account usage narrow rather than attaching the credential to every request.

Contributions are welcome through issues and pull requests, though the developer states that requests for new streaming services will not be accepted; anyone interested in adding a service is encouraged to fork the repository. The project credits contributor Priveetee for researching SABR and implementing support for it, and AioiLight for code behind the NicoNico service. Development is funded through Ko-Fi and Liberapay, and a community wiki is maintained by Priveetee.

Why it matters

NewPipe has long served as the foundation for third-party YouTube access on Android, and its ecosystem has split into two shapes: forks that follow upstream closely, and independent branches like PipePipe that trade shared maintenance for velocity. The features PipePipe ships — SponsorBlock, dislike restoration, sign-in — are the kind of additions that tend to arrive slowly in consensus-driven projects, and the hard fork lets them land quickly.

Sign-in matters most here. Restricted and premium content has been effectively out of reach for cookie-free clients, and limiting cookie use to stream retrieval is a deliberate attempt to reduce the account exposure that logging in normally carries.

The cost is structural: fixes, extractor updates and workarounds for YouTube changes no longer flow between the two codebases, so each project carries that ongoing burden alone. For users choosing a client, the real decision is now the trade-off between feature speed and shared upkeep.