RE: Feedback Wanted: “Communities” Design Document
EVERYONE INTERACT TO HELP MAKE IT HAPPEN
- I heavily encourage @busy.org @partiko @good-karma @ekitcho @sida and others to jump in on this conversation. Let's start a trend to build products together with the support of steemit. And push them to not be able to not communicate. haha
- Big thanks to @shred7 @asgarth and @roadscape for getting the ball rolling/re-rolling on communities.
- Anyone else please participate in the conversation... tag me or jump into the @steempeak discord to let us know who you'd like to see of the UI for communities. If you use another interface go ask them if they have a plan to develop for communities. Take a look at this spec as it's gonna impact a lot of what we can do utilizing hivemind if you think of something for now or later let them know and let us know how awesome it can be so we can also push for it with you.
PUBLIC QUESTIONS AND FEEDBACK FOR STEEMIT INC
A. Are you willing to release the backend/hivemind changes even before you have your own steemit.com design ready?
B. Who's working on your UI for communities at Steemit Inc?
C. What are the 2-3 things you want the most feedback on in your document?
D. Are you willing to eventually consider multi-owners perhaps when the blockchain supports multi-signature type technology?
E. I think short description "About" should be shorter than 512 characters. This needs to be crafted to fit into social re-shares like discord, reddit, fb etc
Or what's the reasoning behind 512?
F. About could be a good place for it... but i'm thinking there needs to be a json data that basically and shortly responds to the question of "What content is acceptable as part of this community?"
G. if i'm not mistaken iso693-3 is a 3 letter language code and your examples are 2 letters
H. I think many people would like to see a small fee for communities with the steem being BURNED or sent to the Steem Proposals fund. Any reason not to do that? I know there's less need since it's number identifier and not a unique name. But still it's good for the health of steem and helps with the SNR (noise)
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 or potential pain points.
D. Yes, actually multi-owner is possible today using on-chain multisig.
E.
aboutlimit of 512 is based off reddit model and it's roughly a paragraph.F. Community standards could fit into
description(long field describing what the community is about) orflag_text(describing what will result in posts being muted).G. Good catch -- URL was left as a note. I'm not sure how granular we need to be. It seems like
639-1may be a good place to start for simplicity, and expanded to639-3if there is a proven need.H. I agree, though I think that requiring an account creation is enough of a rate limit.
Thanks for the feedback @jarvie!
very good planing good luck