I run the tribe STEMGeeks, a community for people to share their interest in Science, Technology, Engineering, and Math. It is a casual community where you don't need to be a Scientist or Construction Engineer to participate.

As a tribe owner, I believe strong moderation is critical to the success of a tribe. Tribes should stay focused on their intended purpose, if they don't they lose all their purpose. This requires active moderation and flagging content that does not belong in the tribe. Most tribes have a large staked account for this intended purpose.

While I have taken a different approach to STEMGeeks than most tribes owners, I do have a curation account for my tribe. When I say a different approach, I refer to the fact I try to avoid influencing the reward pool as much as possible to prevent diluting the stake of users who have staked STEM tokens. If I power up a bunch of accounts or even one account with a massive stake and start voting content your vote becomes worth a lot less. My curation account has a relatively small amount of STEM staked and only uses small percentage votes (currently 10-30%).

The problem

I promised you a pro tip, but what is the problem?

For STEMGeeks I have three notable accounts, @stemgeeks, @nostem4u, @stemcuration.

@stemgeeks is the main account that handles token distribution and posts announcements for the tribe. This is also the master account that handles muting for the tribe.

@nostem4u is a large staked account that moderates content that does not belong in the tribe and counters abuse.

@stemcuratoin is an account with STEM tokens staked (50,000) that makes small votes to acknowledge good content and give a small boost in rewards. As mentioned before, I don't want to give out large votes that would de-value STEM holder's stake.

While keychain makes the job easy, I don't want to log in and out of accounts to make announcements, mute accounts, flag content, and do curation. This is a lot more work and it makes it easier to make mistakes under the wrong account.

ProTip

I use my own scripts to manage automation but I am sure the public services can handle this.

I always stay logged in as @stemgeesk on https://stemgeeks.net. If I need to make a post or a comment as the tribe, I am able to do so as I am logged in as @stemgeeks.

If I want to flag content, I do so as @stemgeeks and my bot automatically follows flags from @stemgeeks with @nostem4u. So I am able to flag content without switching accounts. @stemgeeks has 0 staked STEM tokens and very little Steem Power so the vote is meaningless. @nostem4u has 1 million STEM staked so most flags only need to be 1%.

If I want to mute an account, I can mute it as @stemgeeks and it will be ignored by Scotbot for future posts automatically. (As far as I know, mutes are updated every 2 hours or so).

If I see a good post, I can vote it with @stemgeeks (typically 10-30%) and @stemcuration will follow that vote with a similar percentage with its 50,000 STEM staked tokens. 10-30% on 50,000 STEM isn't a large vote and does not drastically affect a post's payout, and is more in line with a single vote from an active STEM user. These votes do help these posts appear on SteemPeak's technology tab as they follow @stemcuration's votes.

Conclusion

As a tribe owner, you likely have at least three accounts to manage your tribe. By using vote following of your main account you can control three accounts from one master account. You will need the ability to not follow downvotes and not follow upvotes, I am not sure if the public services currently offer this functionality. If they do, you can easily set up a similar configuration for your tribe.

If you have multiple users, this becomes a little different. You can follow multiple curator's downvotes with your flag account for example and even use a coded system. For example, if a trusted curator downvotes a post 1%, the NOX4U account can flag with 10%. If the curator downvotes with 2% it can flag with 30% or even 100%, depending on how much is staked on that account. Many tribes have active curators/moderators.