Remove "Purge all caches" button #3022
-
|
Previously, with the clear caches button, the user could pull changes within 15 minutes after committing. Now, in the worst case scenario, pulling changes can take up to 5 hours of waiting until the next diff patch cycle occurs. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 53 replies
-
|
Click the clock of the list to update is much more friendly to remote server than forcing an update of all lists, and it's even easier for users now, clicking the clock causes the list to update immediately. You can also tell them to click an update link like this. |
Beta Was this translation helpful? Give feedback.
-
Easylist has a script somewhere which assemble the lists from templates. You need to ask them if this can be done for ruadlist repo. |
Beta Was this translation helpful? Give feedback.
-
Yes, these can be removed if the lists are never going to be used standalone. |
Beta Was this translation helpful? Give feedback.
-
|
I always have them connected separately, this is convenient for debugging. But I don't think any users do the same. |
Beta Was this translation helpful? Give feedback.
-
|
I updated to version 1.54.1b12, but it still requires me to press the Shift key to update successfully. |
Beta Was this translation helpful? Give feedback.
-
|
It's by design, to ensure people don't forfeit the benefit of differential updates. With shift-click, the list will next update in a few days instead of few hours. |
Beta Was this translation helpful? Give feedback.
-
|
@gorhill Just making sure, if I want to update resources from |
Beta Was this translation helpful? Give feedback.
-
|
There is no way I would have know that the update of
So clicking the clock (without shift) is equivalent to forcing an auto-update, no (thus maintaining diff update)? Also, is the behaviour of the purge button in the devtools identical to the purge button before 1.54.b11? |
Beta Was this translation helpful? Give feedback.
-
|
The "Purge all caches" button in dev tools is for development purpose only, it's equivalent to shift-click "Purge all caches" the old button.
The documentation says:
But this needs correction, it's really any list currently, not just uBlock filters. |
Beta Was this translation helpful? Give feedback.
-
Yeah I have been interpreting this as "Using the purge cache button", thank you for answering. So is this correct, by the way?
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, and this should force a fetch of resources listed in |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
@dportvine Does it work for you? |
Beta Was this translation helpful? Give feedback.
-
|
Yes it works for me. I see the last change.. Screenshot(s)
|
Beta Was this translation helpful? Give feedback.
-
|
To summarize, we can conclude that now the control panel interface does not have the ability to update filters to the current state. A simple click on the clock icon causes the filter to be updated to the latest diff patch, which may be a 5-hour outdated version. Moreover, such a click must be made for each filter separately. The ability to press the shift button is not mentioned anywhere, and even if you use it, you still need to do this for each filter separately. Yes, when reporting a problem using the chat icon, which has a button to update all filters, they can be updated at the same time. But this option can hardly be considered user-friendly, since it is not obvious and it is impossible to get there directly from the control panel. I think this is too drastic a decision. |
Beta Was this translation helpful? Give feedback.
-
|
Waiting 5 hours to get a rule added 50 minutes ago is a long time. Is it possible to reduce the interval? |
Beta Was this translation helpful? Give feedback.
-
|
I think it makes sense to reinstate these buttons under filterAuthorMode. |
Beta Was this translation helpful? Give feedback.
-
|
How about putting a button to unconditionally update filters on the support tab? |
Beta Was this translation helpful? Give feedback.
-
|
Filter lists should never need to be updated manually for the vast majority. The issue here is that "Purge all cache"-"Update now" is a meme but nobody is willing to foot the server bills should we be kicked out of one or more of those CDNs uBO uses. This is the reality:
In what reality-based scenario does one need to do this for every lists? People report filter issues, they are fixed, we give them a link to update only the one list which has changed. If I put pack another way to do the same as "Purge all cache"-"Update now", it will be abused the same way because people out there are not concerned with CDN costs. The changes here ensure that the action of updating lists is driven by actual filter issues, not by how user feels when their lists is not perfectly up to date to the minute even when there are no filter issues. |
Beta Was this translation helpful? Give feedback.
-
|
@gorhill Side-note: What is the minimum supported Are these correct? ! Expires: 1 days
! Expires: 12h
! Expires: 6h |
Beta Was this translation helpful? Give feedback.
-
|
Is |
Beta Was this translation helpful? Give feedback.
-
|
Minimum is 4h, and |
Beta Was this translation helpful? Give feedback.
-
This is not true. The update is, most likely, to cause users to migrate off uBlock for a competitor. |
Beta Was this translation helpful? Give feedback.
-
|
How should we modify the issue template? It's now still having "Purge all caches" button |
Beta Was this translation helpful? Give feedback.
-
|
We could remove the generic template ant direct people to use the chat icon. |
Beta Was this translation helpful? Give feedback.
-
|
I mean the line
when creating the issues via chat icon. I think we don't need it any more right? Given there's already an |
Beta Was this translation helpful? Give feedback.
-
|
What if the user does not use the chat icon on the panel and immediately writes here? ~ > https://github.com/uBlockOrigin/uAssets/issues/new/choose |
Beta Was this translation helpful? Give feedback.
-
|
Maybe need implement these: github.com##:matches-path(/\/uBlockOrigin\/uAssets[\w\W]+\/new/) .timeline-comment > div:nth-child(-n+3) |
Beta Was this translation helpful? Give feedback.
Filter lists should never need to be updated manually for the vast majority. The issue here is that "Purge all cache"-"Update now" is a meme but nobody is willing to foot the server bills should we be kicked out of one or more of those CDNs uBO uses.
This is the reality: