
Well, I do care somewhat about privacy, but that's not the main reason why I use NewPipe. If people would rather focus on privacy, the official NewPipe repo is the place to go I'm not sure how many of the people using the official app really care about NewPipe, let alone this specific fork, or the whole FOSS ecosystem. On the other hand, I'd say the more it resembles the official app, the more it's likely to end up like Vanced.Īnd the less people will want to use the official YouTube app The more this fork functions like the official YouTube app, the better the experience will be I do have some points of disagreement, though. Whatever direction you want this project to go is of course entirely your decision. It's become the only way I use YouTube on my smartphone, and I've been promoting it among my friends, especially since you've added it to IzzyOnDroid. Maybe one of those project will grow and some of the devs like you working on their projects can work together on a common FOSS project.įirst of all, thank you so much polymorphicshade for making and maintaining this fork. I really hope that you or some other project can give us that in the future when Google decide to kill Vanced definitely. But as I said, they need Google things (I guess implementing microG, but I don't know how it works, so I don't know if it needs more than that in the backend), and there aren't alternatives with that functionalities. Some things I miss from Vanced and for me are priorities are YouTube functionalities which needs login with Google like my playlists, my personal recommendations feed, shared history with my PC. I haven't tried your fork, but definitely will do it later. Now I'm following VueTube as it seems promising and looks like the dev want to make it being like Vanced (having most of the functionalities like microG, etc), but it needs a lot of work to reach it.

Well, I've been using Vanced a lot and since I read devs have to stop working on it, I tried some alternatives but no one of them works as I need. I want to change the name and logo, but I'm not an artistically-creative person at all.Īny suggestions you may have for rebranding can be put in this discussion on GitHub. It was supposed to be a placeholder for a better name at some point. I'm now much more open to changes to NewPipe's fundamental "privacy-first" approach to development.Īlso I really hate the name "NewPipe x SponsorBlock".
#Newpipe sponsorblock fork free#
So this is a call for ex-Vanced devs, or any others that are interested, to feel free to submit pull requests for changes. For the last several months my priority with my fork has just been to keep it updated with the upstream master branch. I've started a new job a year ago that has significantly reduced my amount of free time. I'm not ignoring anyone - I've just been prioritizing my time. Some of you who follow my branch closely may have noticed how slow I am to respond to issues or changes. I now feel like if people would rather focus on privacy, the official NewPipe repo is the place to go. I am still a very big fan of privacy and fully support the intentions of the original NewPipe devs. I feel like the more this fork functions like the official YouTube app, the better the experience will be, and the less people will want to use the official YouTube app. I am also now open to the potential of adding like/dislike/comment/suggested video functionality using Google APIs.

The next thing I'll be working on is an overhaul on the UI/UX implementation of SponsorBlock, and adding the ability to submit sponsor segments. As a result I've decided to change my approach towards development of this fork. Since the recent closure of Vanced, I've thought about how the demand for a replacement might exceed the desire for privacy. You can preview what our first NFT will look like here: (just kidding about all that, also fuck NFTs)

In about a month I will be making the fork closed-source, and I will be working closely with a few developers to find the best way to profit from our users. I've started this side project almost 2 years or so ago because I love SponsorBlock and thought the more people that have access to it, the better it will be due to more visibility and the nature of it being crowdsourced.ĭue to the recent influx of downloads and interactions with my fork, I've decided to announce brand new NFTs to support the project. For those that aren't aware, I'm the author of the fork NewPipe x SponsorBlock.
