What about a whitelist for specific accounts? Opt-in lists are flexible but it would be a big effort to maintain reasonable lists across the 1000's of blogs. And frontends still have the challenge of selecting

There's no immediate incentive, but it costs about 3 STEEM to create a community, and communities helps pave the way for further gamification. Communities themselves could choose to provide certain benefits

The idea is that you could drain all your voting power with one vote (if you wanted to) and it would be ~20x stronger than a single vote today.

Apologies for the confusion.. will update the doc to be more clear on this. And yes, UIs could even not show any communities by default and charge a "listing fee" if they wish. Or just for some

Yeah! Tight-knit communities are easier to manage and it does not preclude them from growing organically.

The main priority is to launch communities since it allows the type of community organization you are referencing. Then once these basic tools are in place we can shift focus to onboarding. SMTs and

Even at 10 STEEM we'd still have hundreds of communities. A long tail will always be a long tail. The entry fee is not the only tool we have.

By home page do you mean the user's "Blog" section? Posts which go into a community will not be shown on users' blogs. When it comes to showing/hiding specific posts on user's blogs, we need

Much thought has gone into the communities design recommendation. As it's meant to be an open standard, it's important to collect feedback to encourage its use as an interoperable protocol when it goes

My point is that there will be a long tail of low-value communities regardless of entry fee. It will take more than that to highlight the best communities and de-prioritize dead/inactive ones.

I'm excited to see UIs play with gamification. There's not much of this right now and so much potential. Hive (and particularly hive communities) open a lot of options here, which I hope to explore once

H1 - Even if 100 communities are created in the first month only 10 may be good. We will have metrics to be able highlight the best. In the beginning we can just hand-select the active ones. The main benefit

E: The about field was meant to be a quick blurb that would, for example, show and be indexed in search results. I agree a paragraph might be a bit much for this purpose. What do you think about 256 or

@ackza as far as I understand, communities and tribes can be interoperable. The main difference is that hive communities is an open standard and all data and operations are on-chain -- meaning all UIs

A. Yes, backend work will be public and APIs made available to use, even if the UI is not. B. Our internal apps team will be building the UI for condenser. C. Feedback is appreciated on any blind spots

And wrt community setting their own ads -- this could be done with community pinned posts plus a modbot for now. If it's a private ad network I'm not sure it will be easy to have it be part of a standard

With regards to mutes not being retroactive, here's a sample scenario: a user contributes to a community, posting comments and getting involved in discussions. Later, his account is compromised and used

I'm a big fan of this approach. UIs should offer more incentives to power up.

Excited to see where this goes 😉

These are great suggestions and a few of these items are already on the radar. Noted, thanks!