Repository

https://github.com/surpassinggoogle/ulog-communties

This is still a new repository created to receive pull requests for the development of a steem-based bot to enable and run ulog-communities and ulog-subtags on https://ulogs.org  

Details

I please need help with creating a "bot feature" for an existing steem account. This "summon bot" is one which can vote and comment but shaped for "communities".

On Ulogs.org we have "ulog-communities". This currently takes the from of ulog-subtags found on ulogs.org, each of which have overseers. Sample ulog-subtags can be found on the screenshot below:

Please visit https://ulogs.org/created/ulog-snookmademedoit to see an example of how ulog-subtags form spaces for ulog-communities

We have many such ulog-subtags (ulog-communities) across https://ulogs.org and each of these hashtag-spaces have "a list of overseers".

See sample:

 

Overseers comprise of "certified Uloggers" only. 

A certified ulogger can also be an overseer for more than one ulog-subtag e.g @sunnylife maybe an overseer on https://ulogs.org/created/ulog-gratefulvibes as well as an overseer on https://ulogs.org/created/ulography

The whole ulogs.org ecosystem is build around a "grey-list of certified uloggers". This list will be populated organically over the course of time and is represented by the "followed list" of the @uloggers account.

You can also find this list on https://ulogs.org/discover

Each "certified ulogger" has certain perks (tools & features) all across on ulogs.org, that isn't available to every ulogger e.g in ulogs.org (alpha version), "certified uloggers" have a "personal delegate button" attached to the bottom of their posts etc 

By this means, we can create extra value for the role, "certified".

Now back to ulog-subtags! Each ulog-subtag is actually a ulog-community. If you visit any of the ulog-subtags on ulogs.org, you will notice that each ulog-subtag space, has a list showing "the overseers" (in charge of each of these ulog-communities). 

Again, these overseers can only picked be from among the "certified uloggers" only.

We want to empower each of these ones to be able to autonomously grow each ulog-community, that they oversee (independent of their own steem power). 

This means that we want each one to have extra SP to vote on others, within the ulog-community that they oversee. 

A special perk of being a "certified ulogger" is the ability to oversee or own and grow a ulog-community, and being give extra influence in the form of voting SP, to do so.

Being that we still have limited SP (with ulogs.org), we need to set some standards in place to maximize this "limited power" for the growth of these ULOG-communities. 

Note that "certified uloggers" can be "every(any)one", where the only requirement is "human". This also means that, even if you still have limited SP, say 15 SP, you can still "oversee" a ulog-community (after you become "certified ulogger") and have extra SP (influence) courtesy of our joint SP on ulogs.org, to curate posts from authors under the #ulog-subtag space that you oversee.

To accomplish this, we need a "summon bot", one that has the basic capability of being able to vote and comment. Ofcourse, "everyone" can summon this bot and at the very least, receive a response (comment) in return. However, this bot will only vote and comment on an author, when summoned by a qualified "certified ulogger".

We want "qualified certified uloggers" who have been assigned to oversee certain ulog-subtag/ulog-subtags, to be able to summon this bot, to vote on content from authors, who have posted under these ulog-subtag/ulog-subtags.

Besides, the bot would only vote on such posts, if these have been posted using ulogs.org only. 

On ulogs.org, "certified uloggers" are "owners" basically and actual "true fans" of #ulog and should love the art of organically growing our ecosystem. Thus, we want the "summon bot" to be modeled, to incentivize "certified uloggers (overseers) to curate content as "true fans" and we are integrating paradigms in this bot, to enable this.

I explain further with examples...

#ulog is our main tag and it is also more popular. Much of the content displayed on ulogs.org overall, favors the first tag #ulog. 

To build different ulog-communities and incentivize the creation of niche-based ulogs, we create ulog-subtags. We also created ulog-subtags, to be able to integrate every existing hashtag, enterprise, project and community etc present on steem and in the world as a whole 

e.g https://ulogs.org/created/ulog-utopian (#ulog-utopian) allows users to ulog about their daily experiences with utopian as "true fans". They can also ulog under #ulog-utopian to emulate utopian, to giveback to utopian, to share feedback etc

In general, ulogs.org is about "true fanhood" for projects and entities alike etc and this is where ulog-subtags & ulog-communities come in.

Note once again that our umbrella hashtag is #ulog, followed by a #ulog-subtag

So for instance, even if a person wants to create fresh memes using from photography and sentiments drawn from a particular day and decides to ulog about it under "#ulog-memes"; the template when it comes to hashtags will be; 1. #ulog 2. #ulog-memes 3. etc

Now, notice that we are trying to establish the eventual parameters that our "summon bot" will need to check, to function correctly. Based on what we have explained so far, concerning #ulog-subtag always being a second tag, next to our more popular #ulog (which should always be the first tag for every ulog); it is obvious that one parameter that this "summon bot" will have to check, before it votes and comments accordingly, is the first and second tag i.e "it will only vote on posts that have #ulog as first tag and #ulog-subtag as second tag. 

Another key thing established, which is the keyest thing is; the "summon bot" will only get ready to vote and comment (on an author post), if it was summoned by a "qualified certified ulogger".

Let me break it down further....

Let's visit ulogs.org/created/ulog-snookmademedoit! You will notice a header text and towards the bottom of this header text, is a list of certified uloggers who oversee this ulog-subtag. In this case, it is the users; snook & shadowspub

Now, assuming snook is curating posts from ulogs.org/created/ulog-snookmademedoit (#ulog-snookmademedoit) and she finds a post that she wants to upvote; she simple summons @botaccount or summons it using a command, within a reply to the author's post. Snook now expects the bot to arrive, vote on the author's post and leave a "reply" (comment) to the author. 

The @botaccount will only vote on this author's post and leave a comment to that effect (to the author), if all of the following conditions below are met;

1. Snook is on the "followed list" of @uloggers (on the greylist of certified uloggers).
2. Snook has summoned the bot on a post, with #ulog-snookmademedoit as second tag, where #ulog is assumed to be the first tag.
3. #ulog-snookmadedoit is on the list of ulog-subtags that have been assigned to snook (Note that some certified uloggers can oversee more than one ulog-subtag).
4. The post was published using ulogs.org
5. The post upon which Snook made the comment has met all 4 criteria above 

Else, if one of the criteria above is unmet, the bot should leave a directional response (comment) to Snook, telling her a possible list of conditions that were unmet and possible course of action to take.

One other thing that is very obvious at this point, is that this bot should have the ability to receive data-entry from the bot owner or me. Thus, it will likely need a simple UI or perhaps, this can be done by sending "transfer memos".

The lists, of "certified uloggers" & their respective ulog-subtags etc are dynamic and need to be updated regularly.

Now, going back to the parameters that determines the bot's course-of-action, it is also obvious, that the very first check to be done by the bot any time it is summoned, "is to see if the summoner is on the "followed list of @uloggers account" i.e is the summoner a "certified ulogger" at all? 

Note that "everyone" has the ability of calling the bot.

Ultimately, the first bot has two core actions i.e 

• vote & comment (reply) on an author 
• OR simply comment (reply) to the summoner. 

All that we have explained so farm now leaves basis for likely algorithm for the "summon bot". (Note that this can be done according to your expertise and discretion as long as it accomplishes what's required)

Bot Algorithm

When Bot is summoned?

Course of action: Bot check if summoner is on the "list of certified uloggers". If "Yes", bot makes sure the other 4 of the 5 criteria mentioned earlier (above) are met and if met, bot votes and comments on the author post; else, bot leaves a reply to the summoner (certified ulogger), with a list of possible 4 other criteria that wasn't met. 

If "No", bot leave a generic comment (meant for "everyone") to the summoner, stating why the bot did not vote and how they can go on to becoming "certified uloggers" etc.

Notice that we don't want to complicate the bot by allowing it to provide specific comment responses, for each specific failed criteria. Thus, we apply the use of "general response comment".

Summary

• If summoner is not on the list of certified uloggers, the bot has only one action and it is; to respond to summoner with one pre-written comment.
• If summoner is on the list of certified uloggers, bot checks to make sure the remain 4 of the 5 criteria is met. If even one condition is not met, it responds with a "one pre-written comment" to the summoner (certified ulogger), stating that one of remaining 4 criteria wasn't met. 
• If summoner is on the list of "certified uloggers" and the post involved meets all other 4 criteria; the bot votes on the author's post and leaves a pre-written reply to the author, encouraging the author and giving credit to the summoner (true fan & certified ulogger)

It is now evident that this bot, will have a total of 3 comment variant to disperse and 3 possible actions all together.

Of key importance thus, is a simple UI that accepts data-entry for the bot parameters and comments. 

If you chose that these entries can be done with "transfer memos", this is also acceptable.

Here is a simple screenshot (UI):

I would like to have this bot deployed on my Herokuapp and also to a Github. These details we will discuss in a chat as it is necessary that we have a chat, if you are to take up this task.

 

Component.

It may be of importance to find a bot framework for this. I have noticed that there are some open source bot projects on https://steemprojects.com/categories/bot/

I have seen some likely bot framework that can serve as basis but i am not too sure if that is the case. One to look at, which i also found while exploring SteemProjects.com is: https://github.com/mattyice/communitybot 

Overall, carry out the task according to your preference and expertise, submitting a pull request and thereafter a post following Utopian's guidelines for Development (contributions).  

Bounty

An additional 100 SBD. (Subject to increment upon discussion) 

Deadline

10 days 

Communication

You can contact me on:         

• Telegram (username: @surpassinggoogle)
• Discord (username: surpassinggoogle#1660)

You can also indicate interest by leaving a comment underneath this post or on Github. 

It is recommended that we are able to discuss, for a better understanding of the task.

Github

https://github.com/surpassinggoogle/ulog-communties

Submit PR to the fresh repository above.