Nice developments, thank you.

In one of your earlier posts about communities, you mentioned the feature of subscribers requiring approval by an admin or moderator to join the community. This would be a welcome development, so that if you had criteria for joining, you could apply them, and also have a joining process.

I was thinking about this for a reading and writing community where I was looking for high quality writers who were already skilled as storytellers - so they would have to indicate this by submitting two or three pieces of writing to the community team in order to join the community. At the same time, I wanted to have readers (and consumers/curators) who would be able to vote and comment but not create posts unless they had passed the threshold for that. (Substack is doing this very well now).

I think there are other questions about the pros and cons of whether non-subscribers could view, vote and comment on posts (unless muted). The benefits would be the potential for wider audiences, the disadvantages would be if subscribers wanted to use the community for organising and wished their information to remain within the community. I haven't resolved these questions for myself yet, I think they need wider discussion. I know there was some concern about the inleo subscriptions where some posts from an account would only be visible to (paying) subscribers but votable by anyone including automated votes and how that fitted with the overall concepts of Hive and the potential for abuse.

The other thing that I found frustrating when I was admin for a community was that I couldn't access the whole subscriber list through the front end. It would show me a limited number, and this would contain different accounts, seemingly randomly selected, each time I viewed (I was using peakd).It would be great to have better access to this and some management tools. For example, if you learned that 80% of your subscribers had joined in the past three months, community posts could be tailored to that.