create account

RE: Call for Steem Developers - Building Curie's frontend by kevinwong

View this thread on: hive.blogpeakd.comecency.com

Viewing a response to: @son-of-satire/re-xeroc-re-curie-call-for-steem-developers-building-curie-s-frontend-20170116t021300386z

· @kevinwong ·
@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)
properties (22)
authorkevinwong
permlinkre-son-of-satire-re-xeroc-re-curie-call-for-steem-developers-building-curie-s-frontend-20170116t033111195z
categorycurie
json_metadata{"tags":["curie"],"users":["xeroc"],"app":"steemit/0.1"}
created2017-01-16 03:31:12
last_update2017-01-16 03:31:12
depth3
children3
last_payout2017-02-15 17:55:15
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length146
author_reputation621,253,570,295,288
root_title"Call for Steem Developers - Building Curie's frontend"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id2,257,669
net_rshares0
@son-of-satire ·
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.

> If we go this route - the code will be closed, but its operations can still be made transparent..

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.
properties (22)
authorson-of-satire
permlinkre-kevinwong-re-son-of-satire-re-xeroc-re-curie-call-for-steem-developers-building-curie-s-frontend-20170116t035518653z
categorycurie
json_metadata{"tags":["curie"],"app":"steemit/0.1"}
created2017-01-16 03:55:09
last_update2017-01-16 03:55:09
depth4
children1
last_payout2017-02-15 17:55:15
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length1,273
author_reputation112,996,205,695,573
root_title"Call for Steem Developers - Building Curie's frontend"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id2,257,764
net_rshares0
@liberosist · (edited)
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.
properties (22)
authorliberosist
permlinkre-son-of-satire-re-kevinwong-re-son-of-satire-re-xeroc-re-curie-call-for-steem-developers-building-curie-s-frontend-20170116t043953992z
categorycurie
json_metadata{"tags":["curie"],"app":"steemit/0.1"}
created2017-01-16 04:40:09
last_update2017-01-16 04:40:57
depth5
children0
last_payout2017-02-15 17:55:15
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length600
author_reputation177,167,275,265,899
root_title"Call for Steem Developers - Building Curie's frontend"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id2,258,003
net_rshares0
@xeroc ·
$0.03
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 ..
👍  , , ,
properties (23)
authorxeroc
permlinkre-kevinwong-re-son-of-satire-re-xeroc-re-curie-call-for-steem-developers-building-curie-s-frontend-20170116t100535281z
categorycurie
json_metadata{"tags":["curie"],"app":"steemit/0.1"}
created2017-01-16 10:05:36
last_update2017-01-16 10:05:36
depth4
children0
last_payout2017-02-15 17:55:15
cashout_time1969-12-31 23:59:59
total_payout_value0.021 HBD
curator_payout_value0.007 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length740
author_reputation118,819,064,085,695
root_title"Call for Steem Developers - Building Curie's frontend"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id2,259,527
net_rshares1,106,293,860,850
author_curate_reward""
vote details (4)