5 replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
source | link

Stack Apps is unique in that it's more of a showcase for applications written around our API and a resource to find libraries to interact with it. The site sees only marginal flag activity, and the current moderator does a pretty good job of staying on top of the flags and janitorial work the site creates.

What the site does not have is a default contact in the community team, since it's rather different - there didn't seem to be a need to add one. We've assigned one, thus guaranteeing that at least one employee will be stopping by the site daily in addition to the moderator keeping an eye on it. Thus, nothing should go without being handled for too long.

As for another moderator - the site could conceivably sustain an election, but I really doubt that there would be any kind of turn out - we'd probably end up giving diamonds to the one (or two) people that bothered to nominate. If flag activity starts to warrant more help, we'll revisit it then.

Update

Because we know he'll do an excellent job, and because he seems to want ithe seems to want it, we're appointing Tim Stone as a moderator on Stack Apps to add his skills and some redundancy to the team. Tim will be receiving his diamond shortly and going forth into Stack Apps moderation awesomeness.

Stack Apps is unique in that it's more of a showcase for applications written around our API and a resource to find libraries to interact with it. The site sees only marginal flag activity, and the current moderator does a pretty good job of staying on top of the flags and janitorial work the site creates.

What the site does not have is a default contact in the community team, since it's rather different - there didn't seem to be a need to add one. We've assigned one, thus guaranteeing that at least one employee will be stopping by the site daily in addition to the moderator keeping an eye on it. Thus, nothing should go without being handled for too long.

As for another moderator - the site could conceivably sustain an election, but I really doubt that there would be any kind of turn out - we'd probably end up giving diamonds to the one (or two) people that bothered to nominate. If flag activity starts to warrant more help, we'll revisit it then.

Update

Because we know he'll do an excellent job, and because he seems to want it, we're appointing Tim Stone as a moderator on Stack Apps to add his skills and some redundancy to the team. Tim will be receiving his diamond shortly and going forth into Stack Apps moderation awesomeness.

Stack Apps is unique in that it's more of a showcase for applications written around our API and a resource to find libraries to interact with it. The site sees only marginal flag activity, and the current moderator does a pretty good job of staying on top of the flags and janitorial work the site creates.

What the site does not have is a default contact in the community team, since it's rather different - there didn't seem to be a need to add one. We've assigned one, thus guaranteeing that at least one employee will be stopping by the site daily in addition to the moderator keeping an eye on it. Thus, nothing should go without being handled for too long.

As for another moderator - the site could conceivably sustain an election, but I really doubt that there would be any kind of turn out - we'd probably end up giving diamonds to the one (or two) people that bothered to nominate. If flag activity starts to warrant more help, we'll revisit it then.

Update

Because we know he'll do an excellent job, and because he seems to want it, we're appointing Tim Stone as a moderator on Stack Apps to add his skills and some redundancy to the team. Tim will be receiving his diamond shortly and going forth into Stack Apps moderation awesomeness.

4 Migration of MSO links to MSE links
source | link

Stack Apps is unique in that it's more of a showcase for applications written around our API and a resource to find libraries to interact with it. The site sees only marginal flag activity, and the current moderator does a pretty good job of staying on top of the flags and janitorial work the site creates.

What the site does not have is a default contact in the community team, since it's rather different - there didn't seem to be a need to add one. We've assigned one, thus guaranteeing that at least one employee will be stopping by the site daily in addition to the moderator keeping an eye on it. Thus, nothing should go without being handled for too long.

As for another moderator - the site could conceivably sustain an election, but I really doubt that there would be any kind of turn out - we'd probably end up giving diamonds to the one (or two) people that bothered to nominate. If flag activity starts to warrant more help, we'll revisit it then.

Update

Because we know he'll do an excellent job, and because he seems to want ithe seems to want it, we're appointing Tim Stone as a moderator on Stack Apps to add his skills and some redundancy to the team. Tim will be receiving his diamond shortly and going forth into Stack Apps moderation awesomeness.

Stack Apps is unique in that it's more of a showcase for applications written around our API and a resource to find libraries to interact with it. The site sees only marginal flag activity, and the current moderator does a pretty good job of staying on top of the flags and janitorial work the site creates.

What the site does not have is a default contact in the community team, since it's rather different - there didn't seem to be a need to add one. We've assigned one, thus guaranteeing that at least one employee will be stopping by the site daily in addition to the moderator keeping an eye on it. Thus, nothing should go without being handled for too long.

As for another moderator - the site could conceivably sustain an election, but I really doubt that there would be any kind of turn out - we'd probably end up giving diamonds to the one (or two) people that bothered to nominate. If flag activity starts to warrant more help, we'll revisit it then.

Update

Because we know he'll do an excellent job, and because he seems to want it, we're appointing Tim Stone as a moderator on Stack Apps to add his skills and some redundancy to the team. Tim will be receiving his diamond shortly and going forth into Stack Apps moderation awesomeness.

Stack Apps is unique in that it's more of a showcase for applications written around our API and a resource to find libraries to interact with it. The site sees only marginal flag activity, and the current moderator does a pretty good job of staying on top of the flags and janitorial work the site creates.

What the site does not have is a default contact in the community team, since it's rather different - there didn't seem to be a need to add one. We've assigned one, thus guaranteeing that at least one employee will be stopping by the site daily in addition to the moderator keeping an eye on it. Thus, nothing should go without being handled for too long.

As for another moderator - the site could conceivably sustain an election, but I really doubt that there would be any kind of turn out - we'd probably end up giving diamonds to the one (or two) people that bothered to nominate. If flag activity starts to warrant more help, we'll revisit it then.

Update

Because we know he'll do an excellent job, and because he seems to want it, we're appointing Tim Stone as a moderator on Stack Apps to add his skills and some redundancy to the team. Tim will be receiving his diamond shortly and going forth into Stack Apps moderation awesomeness.

3 added 441 characters in body
source | link

Stack Apps is unique in that it's more of a showcase for applications written around our API and a resource to find libraries to interact with it. The site sees only marginal flag activity, and the current moderator does a pretty good job of staying on top of the flags and janitorial work the site creates.

What the site does not have is a default contact in the community team, since it's rather different - there didn't seem to be a need to add one. We've assigned one, thus guaranteeing that at least one employee will be stopping by the site daily in addition to the moderator keeping an eye on it. Thus, nothing should go without being handled for too long.

As for another moderator - the site could conceivably sustain an election, but I really doubt that there would be any kind of turn out - we'd probably end up giving diamonds to the one (or two) people that bothered to nominate. If flag activity starts to warrant more help, we'll revisit it then.

Update

Because we know he'll do an excellent job, and because he seems to want it, we're appointing Tim Stone as a moderator on Stack Apps to add his skills and some redundancy to the team. Tim will be receiving his diamond shortly and going forth into Stack Apps moderation awesomeness.

Stack Apps is unique in that it's more of a showcase for applications written around our API and a resource to find libraries to interact with it. The site sees only marginal flag activity, and the current moderator does a pretty good job of staying on top of the flags and janitorial work the site creates.

What the site does not have is a default contact in the community team, since it's rather different - there didn't seem to be a need to add one. We've assigned one, thus guaranteeing that at least one employee will be stopping by the site daily in addition to the moderator keeping an eye on it. Thus, nothing should go without being handled for too long.

As for another moderator - the site could conceivably sustain an election, but I really doubt that there would be any kind of turn out - we'd probably end up giving diamonds to the one (or two) people that bothered to nominate. If flag activity starts to warrant more help, we'll revisit it then.

Stack Apps is unique in that it's more of a showcase for applications written around our API and a resource to find libraries to interact with it. The site sees only marginal flag activity, and the current moderator does a pretty good job of staying on top of the flags and janitorial work the site creates.

What the site does not have is a default contact in the community team, since it's rather different - there didn't seem to be a need to add one. We've assigned one, thus guaranteeing that at least one employee will be stopping by the site daily in addition to the moderator keeping an eye on it. Thus, nothing should go without being handled for too long.

As for another moderator - the site could conceivably sustain an election, but I really doubt that there would be any kind of turn out - we'd probably end up giving diamonds to the one (or two) people that bothered to nominate. If flag activity starts to warrant more help, we'll revisit it then.

Update

Because we know he'll do an excellent job, and because he seems to want it, we're appointing Tim Stone as a moderator on Stack Apps to add his skills and some redundancy to the team. Tim will be receiving his diamond shortly and going forth into Stack Apps moderation awesomeness.

2 Used the official name of Stack Apps, etc.
source | link
1
source | link