In reply to SuperModerators
I guess I should say thanks first for the consideration of SuperModerator (@freakpower - thanks for the shoutout). I have always been one for adding more moderation tools, but here are some suggestions I have to offer:

- The ability to lock/unlock forum topics
- The ability to create stickys in forums
- Edit/Hide 'Notes' comments for spamming/flaming (not just the note itself)
- Edit/Hide Market reviews/comments for spamming/flaming (not just the market posting itself )

Courtesy see more Seal:
This should definitely be JUST an option. I would think that not everyone would be willing to allow SuperMods to download paid mods, although if thats what the developer wants, then so be it. This does tend to open a new can of worms though. Here are some other suggestions for that:

- If the developer does want a SuperMod to give them their approval on a 'Courtesy Seal' then they should contact one of the SuperMods FIRST. There should be an agreement between the two before testing/approving, meaning that not all SuperMods will be available or may not have a test site for testing the module.
- I think that we (SuperMOds) should not be 'required' to give courtesy seals.
- SuperMods should also have the option to 'opt out' of a courtesy seal. An example would be: If Nathan didnt want to give approval on a courtesy seal, then maybe I would or vice versa.
- For the developers who do not wish to allow a SuperMod to download their product, then maybe there can be a way to allow them access to a complete installation/operations manual of the product for review. If this is the case, there needs to be a way to indicate that the market item was NOT installed or tested. Only a 'Read-Only Review'.
- I think that we should have categories when approving for courtesy seals. One example would be (and one that concerns me most when purchasing a module) is if there is need to alter core dolphin files when installing. You could do something like:
- Admin Install (No core files altered)
- Minimal Code change (1 core file to edit)
- Moderate Code Change (2-3 core files to edit)
- Extensive Code Change (4+ core files to edit)

Im sure there is more I will think of.. This is just a start.
Oh. And also, we should be able to indicate if the module requires domain/license registration. This seems to be a hot topic for some purchasers of the market place.

If the SuperMod actually installs/tests the module for a courtesy seal, it needs to be known that the purchaser may STILL have issues if their site contains other modifications/modules that may cause conflicts without liability on the SuperMod.

SuperMods should also have the ability to moderate a 'regular' moderator. Just in case see more :)
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.