Open chirag127 opened 3 years ago
I allow to change the title but I think in the shadow of the sorting feature my original requested feature will be suppressed as I think that the sorting is pretty slow with any of the sorting algorithms ,while just filtering the content by time like from 10 min to 20 min is pretty easy and fast .
I tried some of the user scripts and extensions that sort the stuff in search results and the sort playlist but found out all of them are very slow and need the results to be sorted and I'm not ready to wait for the search results to be sorted . And as soon as new results loads, the sorting have to be redone . So, practically the sorting of the results on the client side is impossible as we will need to first wait for all the results to be loaded and then sorted .
And talking about related videos I'm currently removing them by using my custom filters by cosmetic filtering with help the ADGUARD but I will love to see this feature option in the improved tube maybe having a seperate section in the appearance section for the search results .
hi @chirag127 what about search with 0 clicks? in sidebar?
Yes Filtering & Sorting will be nice in case of using youtube API, which is limited unless users enter their own key (takes ~5 clicks) - or we apply for an exception with Youtube. API or both combined would be the best ultimately. Filtering can also have the issue that you have to wait a moment or might only get few/zero videos each time you scroll down, if non match your filter.
Edit: i agree simply filtering without API solves a lot. Good to start with.
@ImprovedTube
takes ~5 clicks)
ya , made it when using https://greasyfork.org/en/scripts/30254-youtube-ratingbars-like-dislike-rating . it was pretty easy .
what about search with 0 clicks? in sidebar?
I didn't get it what you wanna say ? Do you mean something like https://greasyfork.org/en/scripts/29451-youtube-search-while-watching-video ?
something like https://greasyfork.org/en/scripts/29451-youtube-search-while-watching-video
yes. + autofocus in a way that won't collide with shortcuts, instant search, filters
hi @chirag127, While we hope for more, everything is (still) rarely patched, except by @victor-savinov. While your request isnt easier alone(?), please repost the single issue alone if you envision better chances. In comparission ImprovedTube issues thread are very active, with no income and '"only" ~0.4 million users. (how old is the average relevant open issue on github, in funded or giant projects?😅)
Title & Plan indicate, that we didnt really start the features for "Youtube Search", despite it is more relevant to stay open than several other issues combined Anybody can always pick a fraction to start with (each fraction might help your original issue too) it is also possible to award a bounty to the next person who wants to tackle the whole. (In each case your first message is getting extra attention, even it wasnt planed to introduce the topic. We or you could also try to rewrite it nicely/invitingly and convert it to a discussion-thread maybe)
You can also suggest new Labels: I agree if "📚Plan" in brown color and the definition in the readme.md are not most inviting. it could also be "🦄special/unique" "big thing!" - or ...?
While your request isnt easier alone(?),
This issue have become apparently impossible to solve because of need of the YouTube API in the sorting while my original request can work without the YouTube API. So I don't agree with you when you say that my request isnt easier alone.
This is something I didn't seen anywhere on any other repository that the maintainer add other complex feature request to the feature request and says the issue is unique/special and complex too by adding some kind of label.
Didn't mean to say that using API is required or impossible or less likely (We can/should add easy steps for users how to make their Key for many features.)
Filtering also will have the issue that you have to wait a moment or might only get a few/zero videos each time you scroll down, if non match your filter.
meant that the same requirement that you pointed out for sorting also essentially applies to filtering.
Example: Filter for videos below 20s or above 4h both might keep loading and show nothing
So with &without API, we should be sure to make use of youtube's filters ( 'short'< 4m & 'long'>20m)
the total amount of results scrolling down is limited to 500 videos. Split in pages of 25 each, thus wont take very long. API can be faster but is also requires to split it to 10 requests (á 50 videos).
The API-advantage is mainly: extra "hidden" filters (not available without API?)
i.e. Medium duration 4-20m. (So using extra filter might be worth as much as more results, i.e. 1000 at the same speed. of which only 1 might be a specific match.
So you might be excited to read/try the search API?
https://developers.google.com/youtube/v3/docs/search/list
(vs. "Super Search" (slow) : The sum of matches could further be increased by searching repeatedly, iterating through mutually excluding youtube filters, or adding a common word, then excluding that common word. This would only be viable for a few searches per day per user, as the Personal API quota is tight.
or unlimited without API maybe? ( - also referring to speed, multiple requests at once?) (so ultimately both combined might be best for a user. And there could be a note with steps how to easily add an API key)
Sorting: to bypass loading visually, it could preview some results before/next to where all appear.
something I didn't seen anywhere on any other repository
☺ Lets be innovative 🎁 While it is typical if you or I are the most-likely to work on this, anybody reading this thread should be more motivatied to help on this, while we add depth & details.
Edit: i agree simply filtering without API solves a lot. good to start with.
what (other/slow) scripts did you compare for filtering/searching? 👍 @chirag127
can we list more typical use-cases?
Allow me to change the title, since there is no other open issue about Search. An old sketch, since the search popdown got overfilled, we can shrink it somehow: (all input welcome!)