There's a big difference between how vpFREE2 updates happen and how the old vpFREE system worked. Basically, vpFREE changes were public and "pushed" to its members, while vpFree2 changes are private and its members are not made aware of such changes, to the best of my knowledge. There's no option in vpfree2 to "receive updates" or anything to that effect that I'm aware of.
For the old vpFREE database, someone would post a possible update on the mailing list, which would generate discussion on whether the update was correct or not. Once it was verified, the admin would update the database and publish this update both to the list and the blog. So changes were both discussed in the group and later "pushed" to the group as well as the blog, so you could keep your finger on changes this way without having to go review every database entry.
With vpFree2, feedback is privately submitted to either the admin or casino monitor, who may or may not make the change. There's no way that I'm aware of for the rest of the vpFree2 members to see what's going on other than to manually check every casino. The information isn't "pushed" out to the member community, and there's no discussion either before or after the change, which stifles communication.
I would like to see vpFree2 changes made open and public in some fashion, whether it's a blog or "pushed" to its members via a mailing list or vpFREE. Some possible options are for vpFree2 to have its own mailing list for updates and discussion that its members could subscribe to, or for such discussion and updates to simply happen on vpFREE, or to have a user option to see all feedback as well as responses to that feedback, where casinos monitors could say whether a change was made or not (called "tickets" on vpfree2).
JD