Drupal Association members fund grants that make connections all over the world.
the attached patch solves a problem which occurs with ajax paging of views when the same view is represented more than once in Drupal.settings.views.ajaxViews. I know this is a rare occurrence but it happens with the new ajax version of my Quick Tabs module (the 6.x-2.x branch) because you can have two tabs, each containing an instance of the same view but with different arguments. You can see an example of what I mean here.
The patch simply puts a conditional around the line where the viewData variable (which will be the parameters sent with the ajax call to fetch the view) is populated from the settings - so that this only happens when the information about the view has not been retrieved from the querystring. Without the patch, the pager links on the second instance of the view, though their href contains the right data, result in the view being retrieved based on the settings for the first instance of that view_name within Drupal.settings.views.ajaxViews - which in the case of my example has different view_args.
I hope my explanation makes sense. I've tested ajax paged and filtered views outside of Quick Tabs with the patch and have noticed no side effects.