RE: The Always Up to Date Proposal to Support PeakD.com by howo

View this thread on: hive.blog | peakd.com | ecency.com

Viewing a response to: @steempeak/the-always-up-to-date-steempeak-proposal

steempeak · @howo · Oct 27 '19

I love your work but I won't vote for this proposal for a few reasons : 

You are closed source, I don't think public funds should be funding closed source projects as the value can easily be "lost" if you decide to pull the plug at any time. Imo closed source should fund themselves or get open source. And I see a lot of ways for you to monetize your front end.

I really, really dislike those proposals that run for years that are just "support us" with a list of features that you may do, without a clear roadmap or accountability. Instead of a clear proposal per feature set. I am very familiar with the sps and I know how time consuming it is to raise votes. But why don't you do something like a per quarter proposal ? This way there is a clear roadmap and accountability. And spending some time every 3 months to get votes is okay, especially if your previous proposal was a success.

👍 dhimmel

`author`	howo
`permlink`	q012od
`category`	steempeak
`json_metadata`	{"app":"steemit/0.1"}
`created`	2019-10-27 10:05:12
`last_update`	2019-10-27 10:05:12
`depth`	1
`children`	2
`last_payout`	2019-11-03 10:05:12
`cashout_time`	1969-12-31 23:59:59
`total_payout_value`	0.000 HBD
`curator_payout_value`	0.000 HBD
`pending_payout_value`	0.000 HBD
`promoted`	0.000 HBD
`body_length`	891
`author_reputation`	517,888,995,750,373
`root_title`	"The Always Up to Date Proposal to Support PeakD.com"
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	0
`post_id`	91,945,753
`net_rshares`	0
`author_curate_reward`	""

properties (23)vote details (1)

voter	weight	wgt%	rshares	pct	time
dhimmel	0 B		0	100%

@asgarth · Oct 27 '19

$0.52

Totally understandable points ...and we were expecting this from some people.

Just some considerations:
- some projects are open source (busy.org) but as the developers behind them disappeared the project just died. And steemit funded the project for years with an huge delegations so in a way we lost values also if the code is available to everyone. This is because the code is shared, but the project leadership is not.
- we are working on steempeak in our free time, so have a commitment on the order of features (roadmap) and a timeframe (quarter) to complete them is not easy for us. Specially considering that we can get or lose funding during the quarter.

They said I understand you stance and I'm happy that you like our work ;)

👍 howo, steempeak, sgt-dan

`author`	asgarth
`permlink`	re-howo-q0186f
`category`	steempeak
`json_metadata`	{"tags":["steempeak"],"app":"steempeak/1.19.0"}
`created`	2019-10-27 12:03:51
`last_update`	2019-10-27 12:03:51
`depth`	2
`children`	0
`last_payout`	2019-11-03 12:03:51
`cashout_time`	1969-12-31 23:59:59
`total_payout_value`	0.261 HBD
`curator_payout_value`	0.260 HBD
`pending_payout_value`	0.000 HBD
`promoted`	0.000 HBD
`body_length`	740
`author_reputation`	45,109,414,272,952
`root_title`	"The Always Up to Date Proposal to Support PeakD.com"
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	91,948,275
`net_rshares`	2,483,023,929,868
`author_curate_reward`	""

properties (23)vote details (3)

voter	rshares	pct
howo	1,994,871,623,178	100%
sgt-dan	67,574,993,674	100%
steempeak	420,577,313,016	70%

@dhimmel · May 23 '20

I currently support this proposal but am on the fence due to the lack of open sourcing under a permissive license.

@asgarth it seems like open sourcing large parts of the platform would give this proposal (or a new one) the boost it needs to get funded.

properties (22)