QWPs can be filtered in a lot of different ways:

1. filters in the URL
2. filters applied as part of the view
3. filters applied as post params, which seem to behave differently than filters in the url. this may encompass other items in this list
4. filters applied using the JS code, which seem to behave more like post params. the JS code support both removable filters and non-removable filters.

There is also an option for the QWP called 'apply view filters'. the corresponding url param is ignoreFilters.

As best as I can figure out, here's how it breaks down:

1. filters applied through the URL are always visible to the user (ie. there's text saying 'query filtered on X') and they can always be removed by the user
2. filters applied as post params are never visible (ie. the user has no real way of knowing that filter is being applied) and they can never be removed by the user as far as i can tell.
3. filters applied as part of a view are a hybrid. they do not appear as visibly as #1. however, the user can edit the view and see that this filter exists. they can also remove them using customize view. the ignoreFilters option also removes them.

the ignoreFilter option seems to remove #3, but will never remove #2. are the above observations accurate? Is there a better way to conceptually break this down?

thanks.