Show/Don't hide feed items when updating feed

[okan35]

Checklist

• [x] I checked, but didn't find any duplicates (open OR closed) of this issue in the repo.
• [x] I have read the contribution guidelines given at https://github.com/TeamNewPipe/NewPipe/blob/HEAD/.github/CONTRIBUTING.md.
• [x] This issue contains only one feature request. I will open one issue for every feature I want to request.

Describe the feature you want

Currently in what's new when we refresh the whole UI is basically blocking by loading screen. In my opinion this is bad design as there is defot no need for blocking user from watching videos or browsing channels etc while new videos are loading.

So my suggestion is removing the blocking loading screen and leave the notification for that purpose as notification shows us how many videos are being fetched.

Is your feature request related to a problem? Please describe it

Additional context

How will you/everyone benefit from this feature?

People will be able browse videos, watch them and use the app while loading new videos.This is not the case currently.

[voidplayer]

Ii created a often updated group so i can update on channels that upload often, like maybe 5-10 subscriptions and then after, i update all

But updating all also blocks often updated, even if those feeds where just updated 1sec ago :(

[dev-victoria]

Ii created a often updated group so i can update on channels that upload often, like maybe 5-10 subscriptions and then after, i update all

But updating all also blocks often updated, even if those feeds where just updated 1sec ago :(

I came by the same Issue from adding FeedGroups as avialable Tabs for the main page. Currently there is only one static Progress Status tracked internally. I have some local hacky solution to prevent it showing up on unrelated feeds allready. I don't think it is good tho, which is why I created #12336. I'd prefer to create a good internal infrastructure, which could also enable more fine grained UI stuff or potentially track parallel progresses.

I don't have a concept change so far, I'll leave it a kind of open discussion atm.

[voidplayer]

Kinda unrelated, but ill share my "workaround" around blocking UI while updating feed

Playlists arent blocked, so now I purposely have a playlist with pending videos. So I always start there while waiting for the feeds to update :)

It does nothing to fix this, but with this flow i dont have this problem anymore :)

[dftf-stu]

Just commenting here as @ShareASmile closed my ticket #12508 as a duplicate of #11755 , and their reply on that earlier ticket was the OP should "make suggestions" on this ticket.

I'm not sure if my issue is the same though.

It appears to me on this ticket, people want to be able to refresh their Subscriptions list and have that work in the background, so they can use the app still in the meantime.

My issue was that two specific channels always cause the refresh to hang for around 5-10 seconds, which would suggest there is something on those channels NewPipe doesn't like -- similar to the recent issue where having pronouns (e.g. them/they/their) on a YouTube channel would cause the NewPipe to error, and say that channel could not be loaded.

Maybe people here could check as I don't think my ticket really relates to this one...? 🤔

[dftf-stu]

My previous message can be ignored, as I've figured-out what the known-issue is -- so to help anyone else who ends up here:

Whichever YouTube channel you have in slot 42 (i.e. the 42nd channel you added a sub for in NewPipe) will always hang for around 5-10 seconds during a refresh of your Subscriptions page, due to how NewPipe gets its data from YouTube. Then every +50th channel slot thereafter -- so slots 92, 142, 192, 242, 292, etc. -- will all do the same. The issue is not related to a channel itself, but sounds like NewPipe can only process 42 channels initially, then has to pause, and then has to pause every 50 channels after that so as not to trigger some sort of API limit or YouTube bot-check monitor (or something).

It would be nice if this issue was noted on either the NewPipe FAQ section, or perhaps have a "Known Issues" on here? Given it is clearly an internal-limit / by-design behaviour that is very-easy to encounter, it doesn't appear mentioned anywhere I've found?