polymorphicshade / NewPipe

A fork of NewPipe with SponsorBlock functionality.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Blacklist Videos, channels and keywords

IshanChhangani opened this issue · comments

Checklist

  • I made sure that there are no existing issues - open or closed - which I could contribute my information to.
  • I have read the FAQ and my problem isn't listed.
  • I'm aware that this is a request for NewPipe itself and that requests for adding a new service need to be made at NewPipeExtractor.
  • I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
  • This issue contains only one feature request.
  • I have read and understood the contribution guidelines.

Feature description

For a long time now I have been looking for a way to use YouTube on mobile devices with a blacklist feature, which works as:-
If a channel is blocked then if even searched for that channel name , it does not show up in search results, same for videos and keywords(block all videos from rendering containing a particular keyword in the title name).
Note that I want this feature not just on feed but on search results also.

Why do you want this feature?

It is very important in case there are some people which keep posting some hate stuff or just to avoid some channels.

Why ist the feature relevant to this fork?

Actually there is already a issue created on the original repo of newPipe TeamNewPipe#1815 but it is unattended from over 5 years now , due to their ideology, I feel the idea of blocking channels match more with ideology of this repo.

Additional information

There are some already existing chrome extensions which does this job:-
https://github.com/amitbl/blocktube/tree/master
https://chromewebstore.google.com/detail/channel-blocker/nfkmalbckemmklibjddenhnofgnfcdfp?pli=1

I have myself created a chrome extension for this https://github.com/IshanChhangani/chromeext
But since I am new to android would like help from the devs.

I don't see much rejection from upstream side in that thread except for a very old and revised opinion of one of the core developers.
The fact that the issue is still open shows they're open to accepting a PR on the matter; they've been pretty good at cleaning up unactionable tickets historically.

You won't get more progress on this issue by asking here. This is not the place for stale upstream feature requests.

@foxjaw that's not how DNS works.

@Atemu Oh I haven't thought of /etc/hosts being an IP address/Domain forwarder. Apologize for that tip. I should try stuff myself then suggest btw. 😅