Viewing a response to: @wehmoen/community-creation-on-scale
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.
author | therealwolf |
---|---|
permlink | q1hhzm |
category | community |
json_metadata | {"users":["roadscape"],"app":"steemit/0.2"} |
created | 2019-11-24 17:30:24 |
last_update | 2019-11-24 17:30:24 |
depth | 1 |
children | 4 |
last_payout | 2019-12-01 17:30:24 |
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 | 596 |
author_reputation | 581,693,011,827,252 |
root_title | " " |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 92,795,493 |
net_rshares | 78,121,242,695 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
wehmoen | 0 | 77,816,382,970 | 25% | ||
kleingeldpilotin | 0 | 304,859,725 | 100% |
@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 :)
author | test-safari |
---|---|
permlink | q1jd2y |
category | community |
json_metadata | {"users":["therealwolf","wehmoen"],"app":"steemit/0.2"} |
created | 2019-11-25 17:40:21 |
last_update | 2019-11-25 17:40:21 |
depth | 2 |
children | 0 |
last_payout | 2019-12-02 17:40:21 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.045 HBD |
curator_payout_value | 0.045 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 291 |
author_reputation | 1,424,111,563,138 |
root_title | " " |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 92,825,499 |
net_rshares | 526,184,825,465 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
therealwolf | 0 | 526,184,825,465 | 4% |
author | wehmoen |
---|---|
permlink | q1hq9z |
category | community |
json_metadata | {} |
created | 2019-11-24 20:30:00 |
last_update | 2020-06-03 06:18:21 |
depth | 2 |
children | 2 |
last_payout | 2019-12-01 20:30:00 |
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 | 1 |
author_reputation | 86,504,380,503,125 |
root_title | " " |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 92,799,814 |
net_rshares | 0 |
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.
author | imwatsi |
---|---|
permlink | q1hww8 |
category | community |
json_metadata | {"app":"steemit/0.1"} |
created | 2019-11-24 22:52:57 |
last_update | 2019-11-24 22:52:57 |
depth | 3 |
children | 1 |
last_payout | 2019-12-01 22:52:57 |
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 | 528 |
author_reputation | 131,386,362,730,495 |
root_title | " " |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 92,802,595 |
net_rshares | 0 |
author | wehmoen |
---|---|
permlink | q1iqp0 |
category | community |
json_metadata | {} |
created | 2019-11-25 09:36:36 |
last_update | 2020-06-03 06:15:57 |
depth | 4 |
children | 0 |
last_payout | 2019-12-02 09:36:36 |
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 | 1 |
author_reputation | 86,504,380,503,125 |
root_title | " " |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 92,814,295 |
net_rshares | 0 |