You are viewing a single comment's thread from:
RE: Introducing Curator: advanced standalone curation interface and the age of #curation-as-a-service
Hi i like the idea of it. I just logged in with the owner's credentials and i curated/rejected some posts already. I was looking into creating an account myself, but it looks rather complicated to me.
Is it any way it can be explained or guided less technical? Or is there a Discord channel to join for further engagement?
And by the way, how can i submit a post for the Curator bot, if i'd like to be reviewed for curation? Thank you.
to create an account, please visit the "team" in the left sidebar. when there simply click on the "add member" button which will generate a popup for you to fill in the info of the new user you want to invite.
.png)
the demo uses ethereal.email as email STMP server so no emails are delivered to the real addresses - instead they are caught to ethereal.email's own email servers. my ethereal.email account details are on the Github page of curator. log in to ethereal.email/messages, and see all emails from the demo there.
now click on the one you sent, and follow the sets in it to activate your account and that's it.
On the second question of post submission, you do not submit anything to curator. a curation service will stream content directly from the blockchain - by category, author or app. so just write your post from any client using the target category and the curator will automatically catch it - there is nothing to submit.
if a curation is curated by author(eg: multi-author blogs such as @adsactly), then only posts from the author account will be curated. if the curation team is curating from an app such as steemit or busy, then you would have to create your app from those app.
i hope this clarifies some of your concerns. i am putting together a second post to further explain Curator. thanks for your interest!
It would be interesting (and useful) to separate the submission of content to the Curator queue from direct feeding from the blockchain, instead pulling from a bin of content which is itself the result of either automated or manual submission, a filter which lives between the blockchain and the database and only lets content through which fulfill some condition or something as straightforward as a Google Sheet to which authorized users or processes put links for consideration.
That would definitely enable standalone teams with thematic or content-oriented purposes to make better use of Curator for its intended purpose. It would open up the possibility of "submitting to Curator" for certain communities if that's how they wanted to run things as well as automated filter discovery.
This is part of that "breaking things down into Producers and Consumers" thing that can be so useful for creating online services.