Well, I feel awkward lobbying for my own project, but since you asked... Here's where I would probably start if I were directing the community curators...
(Background)
The thoth.test account is currently seeking out posts from authors who have been active within about 950 days. I have to balance how long it takes to run vs. trying not to direct too many rewards to people who are never coming back, so the number of days changes from time to time.
It also tries not to direct rewards to people who are actively posting on other chains.
Lots of other filtering is in place w.r.t. the author, the content, the engagement, and the strength of the author's network, but points 1 & 2 are probably the two main points that you would care about.
There are a small number of exceptions to those points for some people who I personally followed in the past, but the community curators could exercise their own discretion if those posts happen to get discovered.
(Plan)
Community curators would be permitted to vote for one of the thoth.test posts or replies daily/weekly/etc..
Personally, I would probably have them vote on one of Thoth's replies that focuses rewards to a single author, not the top-level post that scatters them around to five different authors. That could probably be argued either way, though.
Importantly, curation reports should tag the authors that gained supported retroactively and the community curators could also click through and reply to the original post. The point is just to inform authors and the rest of the community that increased incentives are available for posts with lasting value.
(Alternate Plan) Steemit could setup and run its own Thoth account and take full control of the filtering and the beneficiary split among null, authors, delegators, and Steemit - itself (or even create multiple accounts doing independent reports in English, German, and Spanish). This would also have the benefit of increasing the number of authors who get reached each day.
If I were running a company like Tron/Steemit, I'd actually go with the alternate plan, fork it, and make it into a professional grade product that uses hivemind instead of the public API endpoints, but I know that you may be constrained by access to development resources. Of course, you could start with the first one and switch to the second later if it works out. They're not mutually exclusive.
Well, I feel awkward lobbying for my own project, but since you asked... Here's where I would probably start if I were directing the community curators...
(Background)
thoth.testaccount is currently seeking out posts from authors who have been active within about 950 days. I have to balance how long it takes to run vs. trying not to direct too many rewards to people who are never coming back, so the number of days changes from time to time.(Plan)
thoth.testposts or replies daily/weekly/etc..(Alternate Plan) Steemit could setup and run its own Thoth account and take full control of the filtering and the beneficiary split among
null, authors, delegators, and Steemit - itself (or even create multiple accounts doing independent reports in English, German, and Spanish). This would also have the benefit of increasing the number of authors who get reached each day.If I were running a company like Tron/Steemit, I'd actually go with the alternate plan, fork it, and make it into a professional grade product that uses hivemind instead of the public API endpoints, but I know that you may be constrained by access to development resources. Of course, you could start with the first one and switch to the second later if it works out. They're not mutually exclusive.