The problem with `include` in this case is really a problem with Ruby - that you can't parameterise it. We have to carry around three `before_filter` calls in the right order for the `include` to continue to function, which makes it brittle - if we move `find_site` down below one of the other calls, for example, things start failing. Those dependencies are implicit at the moment. The extraction into a method makes them explicit and defines the order relative to one another.

It's still in a module, it's just that the module gets included via a method (as the second line in the method). This, to me, helps with the fact that there are a few indivisible filters here that must be used together and need executing in the right order. Since we're already using `acts_as_taggable_on` and `has_paper_trail` (which operate in the same way) I don't think we're losing a lot of clarity - I think we're gaining some on the ordered dependency front.