{
  "id": 10015184,
  "title": "PipePipe: NewPipe hard fork implementing SponsorBlock",
  "url": "https://urgent.news/2026/09/25/pipepipe-newpipe-hard-fork-implementing-sponsorblock",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-25T10:55:40.000Z",
  "source": {
    "name": "Hacker News",
    "slug": "hacker-news",
    "url": "https://github.com/InfinityLoop1308/PipePipe"
  },
  "original_language": "en",
  "account": "PipePipe has emerged as a new fork of the NewPipe project, diverging from the original due to differing development philosophies. As such, PipePipe and NewPipe are now separate entities, with no updates flowing between them. This hard fork allows PipePipe to tackle issues swiftly and deliver frequent feature updates, something not possible for forks like Tubular, which sync with the latest NewPipe version.\n\nIn PipePipe, the login cookie is employed strictly for specified scenarios. For YouTube, it facilitates the retrieval of playback streams, and users can customize its usage in the Cookie Functions section. The project welcomes contributions to the Issues and PRs sections, but service requests will not be entertained. Instead, interested developers are encouraged to fork the repository independently.\n\nPipePipe developers are not accepting service requests, urging interested parties to create their own services by forking the repository. Should users find PipePipe beneficial, they are encouraged to become supporters on Ko-Fi to aid in the development of additional features. Every contribution counts towards the project's growth and success.",
  "summary": null,
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}