Now tribes can specify which Steem community tag they use and the nitrous will post automatically to it. This uses the post category and not the tags in the metadata.
Note that for now the reverse does not happen. Posts to the community still need to be tagged with a Scotbot compatible tag to be picked up by Scotbot. This will make it so that the hive tag shows up nicely in the tag labels.
Soon I anticipate the names will be taken from hive but for now this allows a smooth integration to the individual tribe community.
For a long while unstake timings were delayed and did not immediately take away the next unstake amounts when unstakes were happening (they would have deducted only after the next pending unstakes was released). Now it will match how Steem works, deducting the next pending unstake amount immediately, and on each subsequent pending unstake event.
Note that UIs reporting on effective Scotbot stake need to take into account the pending unstakes, and it requires listing unstakes using the Steem Engine API and deducting the next payout from each.
Right now it also does not apply the stake events on the appropriate block (it periodically syncs token data and computes effective stake), and there's work in progress for addressing that. It effectively duplicates the smart contract logic for computing and paying out the unstake tokens or undelegation return stake, which has been a pretty error-prone process and in testing on a parallel test Scotbot. But I am expecting to complete it soon and roll it out.
Another feature requested and released is for the SCT tribe. Scotbot has integrated with their SCT-STEEMP-KRW price feed, and now author and beneficiary payouts are done with KRWP instead of SCT.
When payout occurs an entry will be recorded in 
Now (released for a while now) there is a setting exclude_apps_from_token_beneficiary for tribes that apply beneficiary to token account if a post is not using the Tribe Website to post. This is currently being applied to NeoxianCity.
There's a small nitrous change that's turned off by default because other tribes do not show the beneficiary token portion by default, but this indicates whether the feature is working properly.
