I looked thru the various stored procedures and it quickly became clear the module cannot do this.
Most of the procedures are only receiving PortalID as a parameter.
Clearly, if that's the only parameter they receive, they can't filter by blog.

In addition, my understanding of the basic dnn module architecture philosophy is that each module is supposed to be able to be set up multiple times on a portal.  Each use of the module is either supposed to be a functionally separate one or a pointer to an already existing module setup.  With the stored proc procedures only passing PortalID instead of PortalID and the ID for the module setup, the blog module does not follow those guidelines. 

It seems like it would be a fairly straightforward task for an experienced DNN module developer to add BlogID and the module setup id as parameters to the module setup and to the stored procedures.  If the setup parameters were null, return everything, which would mimic the current functionality.

Comments?