It is a bit difficult to diagnose the problem. By adding the ?nocache=true you bypass the CloudFlare cache, but the browser would also consider it a file that is distinct from the one without that suffix. So it would keep separate copies in the browser cache for each of those, and when you have seen the correct one through the ?nocache=true prefix requesting the file without prefix might still give you the obsolete one.
And the problem is that in the context of pages in articles by others you have no control over whether this suffix is added.
It is a bit difficult to diagnose the problem. By adding the ?nocache=true you bypass the CloudFlare cache, but the browser would also consider it a file that is distinct from the one without that suffix. So it would keep separate copies in the browser cache for each of those, and when you have seen the correct one through the ?nocache=true prefix requesting the file without prefix might still give you the obsolete one.
And the problem is that in the context of pages in articles by others you have no control over whether this suffix is added.