One of the great benefits I see in Communities is that you're no longer fighting for attention alone. Your community is your team and when people see someone else's content in a particular community that

Great ideas. One of my goals is to define a few standard layouts in the protocol, as a per-community setting. But these could be extended per UI. Examples: standard (condensed lines with thumbnail, like

A "Steem help" community is a great idea 👍

As you noted, the important part is the underlying notifications engine, which can be extended with push notifications later. I agree it would be ideal for users to customize them further, including adding

Thanks for the feedback. I agree with another poster that the default view when opening a community should be NEW or at least have the option of setting the default view. This would be an issue for busy

A 'Communities' account tab will be launched soon. When released, community beneficiaries will be mandatory at first. The community can specify a number of destination accounts and a required % for each.

Changing the soft-consensus can lead to ui forks, but it's in developer's best interest to be interoperable. The goal is that devs can extend communities for their own needs, but any changes that can benefit

Excellent feedback, thanks for sharing your experience. Profile – A users need to go to the wallet to update their profile image and info. This is not very intuitive and not an obvious place to check.

The initial release is conservative in terms of design changes. However, the back end has been swapped out to allow for fast iteration going forward. Although unseen, these are big changes, which is why

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

What if account creation credits were made transferrable (and only requiring posting key). They could be used as on-chain tipping token without involving active key. And the claim op could be reduced to

Anyone could 'cross-post' into a community, similar to reblogging.

Hi @loreennaa, communities can filter posts easily by "muting" them. With regards to "cross-posting" into multiple communities, this is something that will be possible with a future

The master community could be a simple container object; otherwise each "subcommunity" would function as a "community" does now. It's just a reverse approach to think about -- instead

Cool idea 👍Another way to implement this could be 'parent communities' -- i.e. a container which holds multiple communities. When you subscribe to the parent community, you are automatically subscribed

There is no active powerdown...

Only altruistic behaviour -- at a real, tangible value cost -- can change the direction of the system or undo any entrenchment. What about non-monetary costs? Many can't be quantified.. yet they may be

Test

Test2

Yes, the only concern is that with this approach hivemind would have to track uniqueness of permlink/id's, and create/track a valid/invalid state on each. This opens up more edge cases and would make it