Call for Steem Developers - Building Curie's frontend
Announcing development of Curie's frontend
As already briefly announced in #curie, in the early months of 2017, we intend to commission development of an automated frontend. We'll make it as complete as our budget would allow, but to begin with we are looking at a simple submission system that will automatically check posts for guidelines and forward them to voters. Accounting has become a daunting task for our team, and this process will now be further automated by this frontend.
For curators in #curie this will mean fewer guidelines, higher submission limits, and a drastic reduction in the minimum elapsed time down from 6 hours to maybe a couple of hours. We would love to hear feedback and suggestions from curators in #curie!
We also intend to feature curated posts and authors, publishing statistics and lists on the frontend. Additionally, Daily Curie posts may continue on Steemit, but with payout declined, as long as there's demand for it. Ultimately, we hope to use the @curie account only for announcements and communication.
Do note that the Curie frontend would be more about public submissions and verification - we'd still need the Curation Guilds feature as proposed by Steemit Inc.
The code for this frontend will be open sourced available for all curation guilds on the Steem network.
The plan
With channel #curie on Steemit.chat growing in activity, it's been getting difficult to keep track of submissions. Please note that we do not vote on everything submitted on that channel. Rather, we will usually check the many suggested posts against a certain guideline. Posts are suggested by #curie finders. After a post proved to have met the guideline, one of @curie voters will vote on said post. Subsequently, our manual process keeps track of the related #curie finder's fees and @curie voter's fees in a database - we're using a .csv spreadsheet at the moment.
So in this case, #curie finder is a community curator, and @curie voter is a guild member - the one that selectively votes for what is curated by the #curie community.
The goal here is to automate both guideline-checking and accounting.
What we have in mind
If anyone knows how to achieve the above by utlizing the channel that we already have #curie or https://steemit.chat/channel/curie, perhaps with some script - that will be great.
If not, we are thinking of a simple website. Here's what it should feature:-
a. Curator submission page.
- Curators submit posts with two text fields - Steemit ID and Steemit.com link.
- Steemit ID is checked against submission limit per day. Most curators have a fixed limit, but select top curators have specific limits. E.g. If the Steemit ID is @fubar-bdhr, the limit is greater. Everyday at 1200 UTC the limit resets.
b. Steemit.com link is checked for -
- No duplicate submissions
- Posts must be between X hours and Y hours old.
- The post's author's rep must be less than R.
- Post must have generated less than $S at the time of submission.
- Author must not have been voted by Curie in the last Z hours.
- If the link fails, the curator should be notified of which guideline(s) they are failing. (Or in version 1, just a blanket doesn't meet guidelines will do)
- If the link passes the guidelines, the posts are passed on to the voters' page.
c. Voters can log in with specific username and password. (No user management required)
- Voters can either accept or reject a submission.
d. Accounting -
- If the voter accepts a submission, the curator who submitted the link will get a FF Steem fee. (If the voter rejects the submission, curator does not get a fee)
- The voter will get a VF Steem fee irrespective of whether they accept or reject.
- At the end of each day (or whatever), a script will be generated to pay both voters and curators. (We already use a Piston script - it should be a fairly simple matter). As well as a CSV for records. (This can be version 2)
e. Apart from that, a couple of additional pages -
- Of course, mandatory FAQ / Introductory pages
- Live feed of Curie's curation. Basically just outgoing votes from @curie as here https://steemdb.com/@curie/votes
- A filtered list of posts meeting the guidelines stated above linking to Steemit.com (jesta had made this earlier though our guidelines have long since changed. He said it was pretty straightforward https://steemdb.com/comment/curie )
We would like to thank @ontofractal for helping us narrow down on this spec. This is the version 1 spec, we have other features in mind for the future.
Contact us
Of course, what we've suggested here is just based on our limited knowledge. Any improvement or simpler ideas for execution would be appreciated. Name-your-price - just drop us a message here. Similarly, you may contact @kevinwong or @liberosist, on https://steemit.chat.
Please re-steem this if possible. Thanks for your time!
![](https://steemitimages.com/640x0/https://s27.postimg.org/lskufss37/steemitrocks.png)
I can build this for you. Ideally (for me) would be to integrate this kind of feature into streemian (i have already started working on something very similar). However that would mean that it will not be open source, but i can offer the same service to other guilds .. How about we get together for a call/chat this week?
Awesome :) TBH we're not sure if we want to stray away from being an open-source project, but definitely worth considering your option - let's have a chat sometime this week. Will invite you to a private channel on steemit.chat - is that alright?
Sounds great ...
I have invited on steemit.chat :) #brightest
I think it is important to keep it open-source. Curie has been doing great work here. Let's not give anyone a reason to doubt their motives and tarnish their reputation.
@xeroc is an awesome dev..
If we go this route - the code will be closed, but its operations can still be made transparent.. (that's what i think)
The idea is this:
I build a platform that is as open as possible from the content perspective and allows you to organize your curators more nicely. This service will not necessarily require you to give posting permissions to streemian but only gives people a set of links they may (consider) to upvote that is curated by curie. The content can be very open to you but the underlying technology that does this for you needs to be closed source until I have another significant advantage over competitors.
Either way, I can understand that you'd rather prefer a open source solution and it is of course totally up to you. All I can offer is a probably quicker implementation as part of streemian instead of a new development from scratch ..
I know xeroc has some major skills. I'm not doubting the abilities, nor the intentions. I have been a great advocate for curie, having upvoted every post I have ever seen and made posts requesting that others do the same.
I have seen in the past others speak of their distaste for curie, and it is that which I referred to in my previous comment.
By the operations being transparent, do you mean that someone will explain what's going on in the code, but without it being publicly viewable?
If so, I feel that any transparency in that case would be subjective, for one would need to place there trust in a human, rather than in a visible, irrefutable code.
I fear this would not help to sate the reservations of those that already harbour doubts about Curie, and I would hate to see anymore animosity within the community in regards to this issue.
I feel Curie offered me a ton of help, and I know they have helped a lot of others too. It seems that, based on this post, it was already part of the plan to make it open source, perhaps for similar reasons. I don't think that you should so easily abandon your initial vision for this new advancement of the project.
I understand why open source aligns well with Curie's spirit and that has always been the intention. However, personally, I feel Curie's primary goal is to curate posts; reward and retain new authors. So far, we haven't really heard back from any developer who would make this an open source project and finish in a timely manner. So it's a simple dilemma - consider closed source by committed developers or the new authors you seek to reward suffer due to lower operational capacity.
Of course it's important that even if it's closed source, other curation guilds have access to this functionality.
If you do this as an open source project on GitHub or similar I would join that. It'd be the best way to attract people to contribute, you just need to create a lead developer account.
Are you open to this?
Oh man, I'm only trained in the ways of old devs - barely scratched the surface with github - so far been using it for n00b stuff for ethereum lol.. I do have an account though!
But anyway, not sure if that'll speed up the process. A dedicated closed development in the beginning will do too!
I'm sorry but I'd be against closed development. Let live in the open air and sunshine! ☀️🌈
Best of luck in any case.
I have some spare time to do development work and I've been getting back into Steemit. I'll try to hop on at some point to get more details if you still need devs.
Alright - thanks will keep you in the loop when the time comes (oh and welcome back!)
This is great, streamlining the process will allow for an easier time getting good new posters rewarded for their efforts. Keep it up @curie team.
hmmm... great!
cool. hope it gets accomplished.
simplifying the front end is vital.
Re-steemed
Cool! Idea
Resteemed