-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
History OFF dumps tons of cache images/data to getExternalCacheDir() #10442
Comments
You could clear the app cache from the History menu after you're done using Newpipe? |
Yes, I do agree. That is a good idea. Usually I go and clear everything from App->Info-> Clear all. What I observe is that: I now have "Watch History" disabled - This gives a feeling I am in incognito but things are dumped to disk. |
I suppose we could have a setting below the Clear Cache button to "Always clear cache upon exiting Newpipe", or something to that effect. |
How is it different from #2338? |
The entire point of opening this issue is that cache data is being left behind despite history being off. That issue is merely asking for a GUI convenience feature. This one is asking to tighten up data privacy. |
Which phone? In phones with 1-2 RAM, I have found not having cache directory causes the device to freeze a lot. (I mean works great on a > 8 GB RAM phone but...) |
Try it on a Android Go device with 2GB eMMC - example Nokia 1.3 or Nokia 1.4 . If not using
like a flagship? |
You are correct. I did not think of I thought you were talking about developers nulling it in builds or something like that.
|
Checklist
Feature description
At the moment even with history OFF, tons of thumbnails/other video-data is dumped to
getExternalCacheDir()
. This is usuallySTORAGE/Android/data/org.schabi.newpipe
. See This is accessible easily on an unlocked phone.One possibility is to replace this
This would mean instead of using /data/ - this is not easily accessible.
Why do you want this feature?
Privacy for viewer
Additional information
My idea would be
The text was updated successfully, but these errors were encountered: