Joe,
My apologies if it looked like the solution was kept secret. This was not the intention. In Sid's case, part of the issue was the way he was trying to use the moderation feature of the feedback module which was resulting in the issues he was experiencing on his particular setup. I did help him out in solving the problem but this was more to help him understand how the moderation feature worked and in his case, he was able to moderate posts once he made a tweak in his environment.

For your information and others, I'll go ahead and post on the forums the particular situation...
In 4.4.2 and onwards of Feedback module, an issue was identified which would allow someone without module level permissions to be able to moderate posts even if they were not supposed to moderate posts. To avoid this problem, we started passing the moduleID as part of the query to the feedback sproc which updates the status of the feedback post. What this means is that you can moderate the posts submitted for the instance of the feedback module which is dropped on a given page. A unique moduleID is given to every instance of Feedback (as well as the comments) and this is used to track which posts can be moderated. 
In Sid's case, he had dropped feedback on a particular page, and then he was trying to moderate the posts from another instance of the feedback module that he dropped on a hidden page which was not visible to someone till they logged in with the right permissions. He was using the redirect feature of the page settings to redirect the user to the moderation page, but he was not passing in the ModuleID correctly as part of the redirection. 
So in summary, all I did was point this out to him and he made the neccessary changes which made his moderation start working. 
One of the reasons I didn't post this on the forums was because his case was unique - in most other cases I've seen people moderate posts, they are using the moderate menu action from the same page on which the feedback module is dropped on a page. 

If you're doing the same thing, then you should be able to make the same changes (note the ModuleID when you click on Moderate) and make your redirect URL to be the same. 

Prior to 4.4.2, you were able to moderate any posts that were submitted on any instance of the feedback module (for the same Portal). In another scenario (lets call this Scenario B), you might have feedback on a given page and are trying to moderate them via another instance on another page - this will not work and this is intentional. 

However that being said, you can make a slight modification and get the above mentioned scenario (Scenario B)  to work too. There is a stored procedure called UpdateFeedbackStatus which takes in ModuleID, FeedbackID and a Status (all integer values). If you modify the sproc in SQL Server by removing the where clause for the ModuleID, Scenario B would start working.

I'm not sure if this is your case or not and if it isn't, I'd be more than happy to work with you to see what's going on in your case.... The sproc in question is given below with the section to be removed in red....

CREATE PROCEDURE {databaseOwner}{objectQualifier}UpdateFeedbackStatus
 @ModuleID int,
 @FeedbackID int,
 @Status int
AS
IF @Status = 4
 DELETE {databaseOwner}[{objectQualifier}Feedback] WHERE FeedbackID = @FeedbackID and ModuleID = @ModuleID
ELSE
 UPDATE {databaseOwner}[{objectQualifier}Feedback]
 SET    Status = @Status
 WHERE FeedbackID = @FeedbackID and ModuleID = @ModuleID
GO

Thanks
Sanjay