create account

Future Proofing Communities by midlet

View this thread on: hive.blogpeakd.comecency.com
· @midlet ·
$13.01
Future Proofing Communities
![CommunitiesFeedback_SubCommunities.jpg](https://cdn.steemitimages.com/DQmVHytqpw7ejySc5r25Z32cct1S4cswgkuGCVWdP2J7H2D/CommunitiesFeedback_SubCommunities.jpg)

So I know we were all locked back out of the beta, but I'm still posting in here because I'm a rebel. Or this won't work and maybe something will explode. Either way on to the post.

So it wasn't long before it occurred to me that a large community would quickly run into a similar problem as the current Steem frontends. We can already see it in 3Speak in that it feels a bit "noisy". I think something that would be really valuable is at least one level deep sub communities within a community.

![subCommCU.jpg](https://cdn.steemitimages.com/DQmYmHueiJ2EiRjpkVXs39kgZBiisb3yuc9CWyXrkfWfWLb/subCommCU.jpg)

The functionality I'm envisioning is that when you follow a community you're automatically subscribed to all the sub-communities as well, but you can unfollow some of the sub-communities if you so choose. Using my community as an example, maybe I'm an artist who is into fine art and concept art, but really have no interest in graphic design, I'd be able to unfollow those sub-communities so I'm not shown that content.

Since it looks like communities is really an advanced tag sorting system, it would just be adding one more tag with a sort of "if the parent community tag is here(hive-xxxxxx) AND this sub community tag, show THIS content.

![SubCommunityPage.jpg](https://cdn.steemitimages.com/DQmUCMk5FWbCVQ8FSWC3AWs5HhFFQbZtiZwbhchDK1KRNP8/SubCommunityPage.jpg)

When you click on a sub-community it filters the posts to only the posts with both of those tags and when you post in the sub-community, you post automatically has both of those tags.

This would allow for the general idea of communities to simply be taken further. I imagine that if people wanted, there wouldn't even be a problem with this going deeper than a single level.

Steem Artstation/Illustration/Animals/Cats/Kittens

I could just see this sub-sub-sub-sub-community housing 95% of my communities subscribers. The heart wants what it wants. I think we should give the people the ultimate rabbit hole digging tools.

What do you all think?
πŸ‘  , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , and 291 others
πŸ‘Ž  , ,
properties (23)
authormidlet
permlinkfuture-proofing-communities
categoryhive-144703
json_metadata{"tags":["communities","feedback","steemit","palnet","neoxian"],"image":["https://cdn.steemitimages.com/DQmVHytqpw7ejySc5r25Z32cct1S4cswgkuGCVWdP2J7H2D/CommunitiesFeedback_SubCommunities.jpg","https://cdn.steemitimages.com/DQmYmHueiJ2EiRjpkVXs39kgZBiisb3yuc9CWyXrkfWfWLb/subCommCU.jpg","https://cdn.steemitimages.com/DQmUCMk5FWbCVQ8FSWC3AWs5HhFFQbZtiZwbhchDK1KRNP8/SubCommunityPage.jpg"],"app":"steemit/0.2","format":"markdown"}
created2019-12-07 03:56:45
last_update2019-12-07 03:56:45
depth0
children28
last_payout2019-12-14 03:56:45
cashout_time1969-12-31 23:59:59
total_payout_value7.227 HBD
curator_payout_value5.782 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length2,189
author_reputation293,267,832,592,637
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,184,891
net_rshares48,015,288,665,251
author_curate_reward""
vote details (358)
@bashadow ·
$0.04
It sounds like a good idea, then I do not need to subscribe to a Non-Fiction writing site and a fiction writing site, and a sci-fi site, steam-punk site, ect. One site to hold all. 

The arts and crafts community also have a lot of different arts and crafts from tie-dye t-shirts to crochet and knitting. the easier a community is able to make finding content for the casual user the better. There are a lot of other ones also, like sports, and photography, and likely ones I don't see on a daily basis.
πŸ‘  
properties (23)
authorbashadow
permlinkq24kit
categoryhive-144703
json_metadata{"app":"steemit/0.1"}
created2019-12-07 04:30:21
last_update2019-12-07 04:30:21
depth1
children2
last_payout2019-12-14 04:30:21
cashout_time1969-12-31 23:59:59
total_payout_value0.020 HBD
curator_payout_value0.020 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length503
author_reputation100,388,692,638,882
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,185,385
net_rshares241,374,440,609
author_curate_reward""
vote details (1)
@midlet ·
Exactly. Since certain communities will be trending, I think it will ultimately make it easier for people to not only find the content their looking for, but also the most popular communities, which will probably have the best content.
properties (22)
authormidlet
permlinkq24lav
categoryhive-144703
json_metadata{"app":"steemit/0.2"}
created2019-12-07 04:47:21
last_update2019-12-07 04:47:21
depth2
children0
last_payout2019-12-14 04:47:21
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length235
author_reputation293,267,832,592,637
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,185,758
net_rshares0
@riverflows ·
Right, yes, this makes total sense.
properties (22)
authorriverflows
permlinkq29k0e
categoryhive-144703
json_metadata{"app":"steemit/0.2"}
created2019-12-09 21:07:27
last_update2019-12-09 21:07:27
depth2
children0
last_payout2019-12-16 21:07:27
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length35
author_reputation2,099,972,515,195,631
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,265,718
net_rshares0
@bil.prag ·
$0.04
not a bad idea. we will see that problem mostly in "general" communities, but sub-communities would be nice addon.

i am not sure even how 3Speak community works. i think it is not automatic to post there when you post on 3Speak. is it a double post, or maybe just adding a hive-100421 tag?
πŸ‘  
properties (23)
authorbil.prag
permlinkre-midlet-q24jzv
categoryhive-144703
json_metadata{"tags":["hive-144703"],"app":"steempeak/2.2.5"}
created2019-12-07 04:19:09
last_update2019-12-07 04:19:09
depth1
children1
last_payout2019-12-14 04:19:09
cashout_time1969-12-31 23:59:59
total_payout_value0.020 HBD
curator_payout_value0.020 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length290
author_reputation462,311,710,234,002
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,185,233
net_rshares242,765,112,714
author_curate_reward""
vote details (1)
@midlet ·
Everything posted on 3Speak is automatically posted in their community. I think this is the way it should be with dapps especially considering something like Appics where the content is really a different format than the web apps, but in these cases especially it seems like sub-communities will be a must. Or else we'll just run into the same issue.
properties (22)
authormidlet
permlinkq24l4e
categoryhive-144703
json_metadata{"app":"steemit/0.2"}
created2019-12-07 04:43:27
last_update2019-12-07 04:43:27
depth2
children0
last_payout2019-12-14 04:43:27
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length350
author_reputation293,267,832,592,637
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,185,676
net_rshares0
@crypto.piotr ·
Hi @midlet

where could I find "sub-community" button?
properties (22)
authorcrypto.piotr
permlinkq2nlrt
categoryhive-144703
json_metadata{"users":["midlet"],"app":"steemit/0.1"}
created2019-12-17 11:12:00
last_update2019-12-17 11:12:00
depth1
children0
last_payout2019-12-24 11:12:00
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length54
author_reputation27,396,789,428,606
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd0
post_id93,488,944
net_rshares0
@ddrfr33k ·
I love everything about this idea.
properties (22)
authorddrfr33k
permlinkq2d5dp
categoryhive-144703
json_metadata{"app":"steemit/0.2"}
created2019-12-11 19:41:48
last_update2019-12-11 19:41:48
depth1
children0
last_payout2019-12-18 19:41:48
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length34
author_reputation132,019,955,620,005
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,325,172
net_rshares0
@gibic ·
I'm not really sure if people want to create their community under certain parent community. Speaking about ownership and authority, and... ego.... Looks like at current state, communities in steem are designed to be more like facebook groups (which is fine, since some of successful facebook group do have high engagements in their contents).
properties (22)
authorgibic
permlinkre-midlet-q25wn8
categoryhive-144703
json_metadata{"tags":["hive-144703"],"app":"steempeak/2.2.5"}
created2019-12-07 21:50:06
last_update2019-12-07 21:50:06
depth1
children2
last_payout2019-12-14 21:50:06
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length343
author_reputation34,268,502,310,257
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,205,108
net_rshares0
@midlet ·
The idea is this is just an extra tool for the community owner to organize content. Not create independent communities. As this becomes the new way forward, if you're into some specific genre of content and there is already a large community for that, you'd probably just rather join that one. But if you're really only interested in one subset of content in the community, you can just subscribe to that.
properties (22)
authormidlet
permlinkq25wuv
categoryhive-144703
json_metadata{"app":"steemit/0.2"}
created2019-12-07 21:54:33
last_update2019-12-07 21:54:33
depth2
children1
last_payout2019-12-14 21:54:33
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length405
author_reputation293,267,832,592,637
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,205,202
net_rshares0
@gibic ·
Ah, I see. Yes, it would be a great addition!
properties (22)
authorgibic
permlinkre-midlet-q25x14
categoryhive-144703
json_metadata{"tags":["hive-144703"],"app":"steempeak/2.2.5"}
created2019-12-07 21:58:15
last_update2019-12-07 21:58:15
depth3
children0
last_payout2019-12-14 21:58:15
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length45
author_reputation34,268,502,310,257
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,205,273
net_rshares0
@guiltyparties ·
It's a good idea. The way to do this would have to be for the main community to specify in a custom json broadcast what it's subs are. That way it would be able to pull subs in that aren't necessarily owned by it. However, that could create a scenario where someone adds a sub that shouldn't be a sub, misrepresenting ti.
properties (22)
authorguiltyparties
permlinkq29dv0
categoryhive-144703
json_metadata{"app":"steemit/0.2"}
created2019-12-09 18:54:36
last_update2019-12-09 18:54:36
depth1
children0
last_payout2019-12-16 18:54:36
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length321
author_reputation261,203,126,670,124
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,262,603
net_rshares0
@inertia ·
That would be a fun extension to communities.
πŸ‘  
πŸ‘Ž  
properties (23)
authorinertia
permlinkq24jqr
categoryhive-144703
json_metadata{"app":"steemit/0.2"}
created2019-12-07 04:13:39
last_update2019-12-07 04:13:39
depth1
children0
last_payout2019-12-14 04:13:39
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length45
author_reputation346,568,901,399,561
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,185,160
net_rshares104,376,156,292
author_curate_reward""
vote details (2)
@jarvie ·
$0.04
So there's a couple ways to sub organize a community. 
1. Let the community detail (community settings... aka metadata) which TAGS they'd like to use to subdivide posts. 
Not sure how well hivemind handles this but i'm guessing it will be just fine. 
This provides pretty much ONLY a subdivisions of content but also does kind of let users know which kinds of content is popular and expected. 
2. Have multiple hive communities tied together and Let a community state which community is a PARENT community. 
They would be legit communities each one of them ... this allows different moderators, labels, descriptions and allows people to SUBSCRIBE to different sections of a large community structure. The interfaces would be expected to list the child-communities and the child community the parent one. However the issue is letting people know they may not have child-community content show up in their feed unless they specifically subscribe. 
3. I suppose a mix of the two could be good. 
Meaning only tie multiple hive communities together if there is a reason to have varient leadership moderators and maybe subscribers. For example a POSTING community and a FORUM type community maybe a 3rd option could be a community that is for OFFICIAL POSTS and is more of a locked community that only the organization/business can post to. People can subscribe to that one as more of an Important feeds sort of thing. 
Otherwise divide by topic/keyword. 

Thoughts on that?
πŸ‘  
properties (23)
authorjarvie
permlinkre-midlet-q24k06
categoryhive-144703
json_metadata{"tags":["hive-144703"],"app":"steempeak/2.2.5"}
created2019-12-07 04:19:21
last_update2019-12-07 04:19:21
depth1
children4
last_payout2019-12-14 04:19:21
cashout_time1969-12-31 23:59:59
total_payout_value0.020 HBD
curator_payout_value0.020 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length1,468
author_reputation388,491,264,112,133
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,185,237
net_rshares243,487,460,343
author_curate_reward""
vote details (1)
@midlet ·
> Let the community detail (community settings... aka metadata) which TAGS they'd like to use to subdivide posts.
Not sure how well hivemind handles this but i'm guessing it will be just fine.
This provides pretty much ONLY a subdivisions of content but also does kind of let users know which kinds of content is popular and expected.

I think what I would prefer this as a basic option. This is basically what I was suggesting above, but I forgot to add that part, that the community owner dictates what sub-communities exist. I imagine it being an organic thing that once a certain portion of the community gets big enough, they can break off and form their own -sub-community.

I think that with the option to be able to have community mergers which sounds like what you were talking about in option two could be an advanced option that I could see being useful if two communities independently grow but have large intersections in their communities they could merge under a parent community, but also maintain their independence. THAT sounds really powerful especially combining that with smt's and the monetization of communities.
properties (22)
authormidlet
permlinkq24kz5
categoryhive-144703
json_metadata{"app":"steemit/0.2"}
created2019-12-07 04:40:18
last_update2019-12-07 04:40:18
depth2
children2
last_payout2019-12-14 04:40:18
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length1,135
author_reputation293,267,832,592,637
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,185,616
net_rshares0
@jarvie ·
So sub-dividion of content and yet also have sub-communities?
properties (22)
authorjarvie
permlinkre-midlet-q24ldz
categoryhive-144703
json_metadata{"tags":["hive-144703"],"app":"steempeak/2.2.5"}
created2019-12-07 04:49:12
last_update2019-12-07 04:49:12
depth3
children1
last_payout2019-12-14 04:49:12
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length61
author_reputation388,491,264,112,133
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,185,780
net_rshares0
@riverflows ·
I like the idea of a FORUM type community and an official posts locked section, or a search by keyword to find the thread you want to find out about. For example, say two weeks ago we had a conversation about 'sage' on Natural Medicine, and someone wants to know about it - they can easily search for that post/conversation. Or you could get alerts for new comments for that thread (too much?). Separating out the various types of posts within the communities would be awesome.
properties (22)
authorriverflows
permlinkq26p3s
categoryhive-144703
json_metadata{"app":"steemit/0.1"}
created2019-12-08 08:04:42
last_update2019-12-08 08:04:42
depth2
children0
last_payout2019-12-15 08:04:42
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length477
author_reputation2,099,972,515,195,631
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,216,056
net_rshares0
@jaydih ·
I support this simple but brilliant idea!
properties (22)
authorjaydih
permlinkq253td
categoryhive-144703
json_metadata{"app":"steemit/0.2"}
created2019-12-07 11:27:15
last_update2019-12-07 11:27:15
depth1
children0
last_payout2019-12-14 11:27:15
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length41
author_reputation160,272,694,389,766
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,192,401
net_rshares0
@riverflows ·
$0.06
Yes, this is what I'd like to do! I was trying to explain it to @crimsonclad in Dm, but couldn't explain it properly. From a @naturalmedicine perspective, we'd have 'herbalism' 'yoga' and so on.
πŸ‘  ,
properties (23)
authorriverflows
permlinkq26ozg
categoryhive-144703
json_metadata{"users":["crimsonclad","naturalmedicine"],"app":"steemit/0.1"}
created2019-12-08 08:02:06
last_update2019-12-08 08:02:06
depth1
children1
last_payout2019-12-15 08:02:06
cashout_time1969-12-31 23:59:59
total_payout_value0.032 HBD
curator_payout_value0.032 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length194
author_reputation2,099,972,515,195,631
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,216,015
net_rshares383,731,671,988
author_curate_reward""
vote details (2)
@midlet ·
Hopefully you can share this post with whoever can make it happen :)
properties (22)
authormidlet
permlinkq2723f
categoryhive-144703
json_metadata{"app":"steemit/0.1"}
created2019-12-08 12:45:15
last_update2019-12-08 12:45:15
depth2
children0
last_payout2019-12-15 12:45:15
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length68
author_reputation293,267,832,592,637
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,221,836
net_rshares0
@roadscape ·
$0.08
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 to all the children.
πŸ‘  
properties (23)
authorroadscape
permlinkq2f5fp
categoryhive-144703
json_metadata{"app":"steemit/0.2"}
created2019-12-12 21:38:12
last_update2019-12-12 21:38:12
depth1
children3
last_payout2019-12-19 21:38:12
cashout_time1969-12-31 23:59:59
total_payout_value0.042 HBD
curator_payout_value0.042 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length222
author_reputation27,406,317,697,121
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,358,668
net_rshares488,529,969,911
author_curate_reward""
vote details (1)
@midlet ·
How would you imagine that working in terms of ownership and content filtering? Master community shows all and the entire hierarchy still owned by the master owner account? Or does each sub have an owner? I guess what would be interesting about this is that even sub communities could have their own SE token, SMT or alternate frontend.
properties (22)
authormidlet
permlinkq2f6vn
categoryhive-144703
json_metadata{"app":"steemit/0.2"}
created2019-12-12 22:09:24
last_update2019-12-12 22:09:24
depth2
children2
last_payout2019-12-19 22:09:24
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length336
author_reputation293,267,832,592,637
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,359,208
net_rshares0
@roadscape ·
$0.03
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 of subcommunities, a super-community. It would probably be easier to implement, and could accomplish the same goals.
πŸ‘  
properties (23)
authorroadscape
permlinkq2ghk4
categoryhive-144703
json_metadata{"app":"steemit/0.2"}
created2019-12-13 14:57:39
last_update2019-12-13 14:57:39
depth3
children1
last_payout2019-12-20 14:57:39
cashout_time1969-12-31 23:59:59
total_payout_value0.013 HBD
curator_payout_value0.013 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length300
author_reputation27,406,317,697,121
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,377,774
net_rshares163,176,381,643
author_curate_reward""
vote details (1)
@ryivhnn ·
I think that is a magical idea.

I also think past a certain point (maybe three tiers?) it would have to be optional (at least for posting, give me all the tools to explore an entire rabbit labyrinth when browsing though!) otherwise it would drive people (or at least me XD) mad.

<div class="pull-right">https://technonaturalist.net/sites/default/files/styles/sensible_display/public/art/2019/09/heartfyn_0.png?itok=QHDoN0HE</div>
properties (22)
authorryivhnn
permlinkre-midlet-q24wma
categoryhive-144703
json_metadata{"tags":["hive-144703"],"app":"steempeak/2.2.5"}
created2019-12-07 08:51:48
last_update2019-12-07 08:51:48
depth1
children0
last_payout2019-12-14 08:51:48
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length431
author_reputation211,149,707,030,157
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,189,660
net_rshares0
@steemitqa · (edited)
$0.02
Yes, it probably will be needed. Maybe, communities have their own tags?
πŸ‘  
πŸ‘Ž  
properties (23)
authorsteemitqa
permlinkq24jzw
categoryhive-144703
json_metadata{"app":"steemit/0.1"}
created2019-12-07 04:16:09
last_update2019-12-07 04:18:51
depth1
children2
last_payout2019-12-14 04:16:09
cashout_time1969-12-31 23:59:59
total_payout_value0.010 HBD
curator_payout_value0.010 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length72
author_reputation22,135,803,163,402
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,185,194
net_rshares130,271,870,338
author_curate_reward""
vote details (2)
@midlet ·
Isn't that hive-xxxxxx? I think they already do.
properties (22)
authormidlet
permlinkq24l0c
categoryhive-144703
json_metadata{"app":"steemit/0.2"}
created2019-12-07 04:41:00
last_update2019-12-07 04:41:00
depth2
children1
last_payout2019-12-14 04:41:00
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length48
author_reputation293,267,832,592,637
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,185,629
net_rshares0
@steemitqa ·
Sorry, meant tags inside the community not the community itself.
properties (22)
authorsteemitqa
permlinkq25c7p
categoryhive-144703
json_metadata{"app":"steemit/0.1"}
created2019-12-07 14:25:39
last_update2019-12-07 14:25:39
depth3
children0
last_payout2019-12-14 14:25:39
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length64
author_reputation22,135,803,163,402
root_title"Future Proofing Communities"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id93,195,951
net_rshares0