RE: Do you want a Hive Community where Only Members Can Post?

You are viewing a single comment's thread:

These types are still planned, but currently disabled. Type 2 ("journal") is almost ready, and considering adding a new requirement for Type 3 ("council") -- that all payouts must be disabled.



0
0
0.000
3 comments
avatar

Thanks for replying Tim!

About the potential new requirement to disable payouts for "council" type communities, would they affect the payouts in SMTs, if a community decides to have one which would practically be closed to members only? Or that would apply only to the STEEM reward pool?

I'll be a kind of a messenger here with a question, if it's ok with you: will there be room in the future development of communities as you envision them for what I've seen requested a few times, the possibility to switch guest posting on and off within a community?

0
0
0.000
avatar

About the potential new requirement to disable payouts for "council" type communities, would they affect the payouts in SMTs, if a community decides to have one which would practically be closed to members only? Or that would apply only to the STEEM reward pool?

Good question. Ideally this would require disabling STEEM payouts only. I guess it depends on SMT implementation. But currently this is achieved by setting max_accepted_payout to 0.000 SBD, and I don't think its likely that this will apply to SMTs, because it would be complicated to get the market value for each, especially when many will be illiquid. So I think we're good.

will there be room in the future development of communities as you envision them for what I've seen requested a few times, the possibility to switch guest posting on and off within a community?

We'll have new community types which restrict who can post, but I don't think we can have it be editable at will. At least not initially. There are edge cases to consider for the backend, and the goal is to keep the protocol dead simple (and efficient) for now.

0
0
0.000
avatar

There are edge cases to consider for the backend, and the goal is to keep the protocol dead simple (and efficient) for now.

I agree! Plus there's the expectation, which with more work being done before the "official" launch, will make people anxious.

But it's great there's the longer term perspective for who's interested: :)

At least not initially.

Nice to hear about new types of communities too.

0
0
0.000