You are viewing a single comment's thread from:
RE: Call for Steem Developers - Building Curie's frontend
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.