Duplicate cache files created when users come from facebook comments

Facebook comments plugin adds some additional query string parameters to the original URL. For example, when user makes a comment on a website, the link of the article he commented on is posted on his timeline (and to his friends newsfeed). And when someone clicks on that post, facebook redirects it to the URL with additional parameters to track the comment click and/or to scroll the page to the original comment.

For example, URL www.example.com/node/53 becomes:
www.example.com/node/53?fb_comment_id=fbc_256941371164231_256947334496968_256947334496968
(and this is the shortest example)

The problem with Boost is that it is making the new cache file for each and every instance of the single article based on the different comment_id's and other stuff facebook is adding to the URL. And the files are like this:

node_53_fb_action_ids=728780277144485&fb_action_types=og.likes&fb_source=feed_opengraph&action_object_map=%7B%22728780277144485%22%3A421281478008877%7D&action_type_map=%7B%22728780277144485%22%3A%22og.likes%22%7D&action_ref_map=%5B%5D.html

Ideally boost should have an option to define the names of the query string parameters to ignore. Most of the time the parameters like facebook's are consistent and it is possible to define the ones that should be ignored when creating the cache file.

I'm starting with boost just now, but I think there might be many other cases when the ignore-parameters list would be necessary (like for the ad campaign traffic, google analitics _utm strings, etc...)