Skip to content

Add option to discard video without marking them as viewed (allowing you to return to them later) #300

@ghvxx43696

Description

@ghvxx43696

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 Tubular itself and that requests for adding a new service need to be made in vanilla 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 vanilla NewPipe contribution guidelines.

Feature description

If a video from a channel we subscribe to does not interest us at the moment, we can either keep it on the “what's new” list endlessly and clutter it up, or mark it as watched, which will prevent us from returning to it in the future (we will forget which ones we actually watched and which ones we marked as such because we were not interested in them at the moment).

I suggest that such videos could be marked with a “hide” or “not interested” option in "what's new" list and in channel page. Such a video should disappear from what's new list and be grayed out in the channel (subscription) tab, which would emphasize that we rejected the video but did not watch it.

Why do you want this feature?

This may not seem like a big difference, but if we want to return to unwatched “rejected” videos, we currently do not have this option – they will be marked as watched like all the others.

Personally, I experience this need many times every day because most of my content is not necessary to view at the time of release and retains its value even many months after publication.. Currently, such videos clutter my “what's new” list, which goes on and on and is filled with videos that I may be interested in in the future, but I don't intend to watch them right now. I think this problem must also affect other users, and introducing this option will greatly contribute to organizing the content of the application.

Why is the feature relevant to this fork?

I submitted the proposal upstream, but since the rewrite was announced a few years ago, all proposals for new features are rejected outright or remain in limbo.

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions