create account

by therealwolf

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

Viewing a response to: @wehmoen/community-creation-on-scale

· @therealwolf ·
I've got a problem with the naming conventions (1,2,3) for community types (open, closed, private). It creates a conflict where changes in these types will result in the creation of a new community/account altogether.

For example: if you'd like to change your open community to closed after creation, you will need to create a new one, even if it has thousands of active subscribers.

If there is no other way for whatever reason (instead of e.g. using the account metadata), then I could accept it, however, it is a nuisance. 

Would be interested to hear some thoughts on this from @roadscape.
👍  ,
properties (23)
authortherealwolf
permlinkq1hhzm
categorycommunity
json_metadata{"users":["roadscape"],"app":"steemit/0.2"}
created2019-11-24 17:30:24
last_update2019-11-24 17:30:24
depth1
children4
last_payout2019-12-01 17:30:24
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_length596
author_reputation581,693,011,827,252
root_title" "
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id92,795,493
net_rshares78,121,242,695
author_curate_reward""
vote details (2)
@test-safari ·
$0.09
@therealwolf / @wehmoen - membership structure is a fundamental property of a community, switching between different types at will creates a lot of backend and frontend edge cases. Trying to keep the protocol as simple as possible, particularly for first version. Let's collect data first :)
👍  
properties (23)
authortest-safari
permlinkq1jd2y
categorycommunity
json_metadata{"users":["therealwolf","wehmoen"],"app":"steemit/0.2"}
created2019-11-25 17:40:21
last_update2019-11-25 17:40:21
depth2
children0
last_payout2019-12-02 17:40:21
cashout_time1969-12-31 23:59:59
total_payout_value0.045 HBD
curator_payout_value0.045 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length291
author_reputation1,424,111,563,138
root_title" "
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id92,825,499
net_rshares526,184,825,465
author_curate_reward""
vote details (1)
@wehmoen · (edited)
 
properties (22)
authorwehmoen
permlinkq1hq9z
categorycommunity
json_metadata{}
created2019-11-24 20:30:00
last_update2020-06-03 06:18:21
depth2
children2
last_payout2019-12-01 20:30:00
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
author_reputation86,504,380,503,125
root_title" "
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id92,799,814
net_rshares0
@imwatsi ·
Both options should be possible.

Integrating into "setProps" will need a little more logic to implement, since the op is also available to mods. It'll be a matter of adding a check for permissions, but it's not complicated.

A custom JSON op like "setType" would need even less changes to current logic to implement.

My thoughts were that maybe it's more an issue of making a community "immutable" in that current members who like it the way it is still get to keep it, while a new one can always be created for a new purpose.
properties (22)
authorimwatsi
permlinkq1hww8
categorycommunity
json_metadata{"app":"steemit/0.1"}
created2019-11-24 22:52:57
last_update2019-11-24 22:52:57
depth3
children1
last_payout2019-12-01 22:52:57
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_length528
author_reputation131,386,362,730,495
root_title" "
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id92,802,595
net_rshares0
@wehmoen · (edited)
 
properties (22)
authorwehmoen
permlinkq1iqp0
categorycommunity
json_metadata{}
created2019-11-25 09:36:36
last_update2020-06-03 06:15:57
depth4
children0
last_payout2019-12-02 09:36:36
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
author_reputation86,504,380,503,125
root_title" "
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id92,814,295
net_rshares0