hivemind issueshttps://gitlab.syncad.com/hive/hivemind/-/issues2021-09-06T16:37:03Zhttps://gitlab.syncad.com/hive/hivemind/-/issues/167Hive Communities Meta-issue2021-09-06T16:37:03ZGandalfHive Communities Meta-issueThis is a meta-issue for Hive Communities that's meant to coordinate work on "version 2"
See:
[docs/communities.md](/docs/communities.md)
and: https://github.com/stratos-steem/stratos/wiki/Subapp:-Communities
<br>to get idea on how it p...This is a meta-issue for Hive Communities that's meant to coordinate work on "version 2"
See:
[docs/communities.md](/docs/communities.md)
and: https://github.com/stratos-steem/stratos/wiki/Subapp:-Communities
<br>to get idea on how it planned **before**.
Also [community feedback](https://gitlab.syncad.com/hive/tasks_without_projects_yet/-/issues/39) gathered by @tmxshttps://gitlab.syncad.com/hive/hivemind/-/issues/149Communities: Support beneficiaries2021-11-05T12:40:57ZHowoCommunities: Support beneficiariesBeneficiaries would be a metadata that we would return and front ends would take that and apply it when creating a post in a community, it would be a json dict inside of the settings column where you can store up to 128 beneficiaries (hi...Beneficiaries would be a metadata that we would return and front ends would take that and apply it when creating a post in a community, it would be a json dict inside of the settings column where you can store up to 128 beneficiaries (hived limit)
beneficiaries would be set using the updateProps action.
On the posts we would use the "is_valid" column to set it as "false" if the beneficiaries in the post don't match those of the community. I think that approach works because you can just set posts as "valid" as you go during the sync and not have to look back once the beneficiaries change. (basically beneficiaries change are not retroactive in terms of "does it affect old posts)
@bwrona / @ABW thoughts ?HowoHowohttps://gitlab.syncad.com/hive/hivemind/-/issues/148communities: enable topics metadata2021-03-15T13:32:07ZHowocommunities: enable topics metadatafrom @Jarvie : https://peakd.com/hive-102930/@jarvie/history-of-blockchain-communities-and-what-is-next
"We (peakd.com) would really love to be able to classify each community by theme/topic so that we can present new (and old) users wi...from @Jarvie : https://peakd.com/hive-102930/@jarvie/history-of-blockchain-communities-and-what-is-next
"We (peakd.com) would really love to be able to classify each community by theme/topic so that we can present new (and old) users with communities related to topics they tell us are of interest to them. So it would be a very good time to allow the community to identify X number of topics their community is related to. Perhaps 3 or 5. The number could be debated. It can be an open system where a community could put whatever they want. BUT perhaps a front end could help the communities to choose from a list of common selections. Like ARTS/SPORTS/BLOCKCHAIN etc.
This would also be helpful when helping to sort communities as well. But mostly helpful to help present a new user with a list of Topics, Communities and maybe even Users that relate to subjects they like."
Basically this field already exists in the schema in two ways, not sure what @roadscape inteded those to be since they are different: `category` and `primary_tag`
I think that a single topic won't be enough, so we would store it as jsonb and use the updateProps action to update the topics. Then we would introduce a new api to fetch communities by topic (search for "sport" and get all communities that match).HowoHowohttps://gitlab.syncad.com/hive/hivemind/-/issues/141Query & return multiple posts2021-05-17T21:30:45ZtherealwolfQuery & return multiple postsThere are situations where I need to query multiple posts. For example when trying to create a feed based on different metrics than supported (i.e: Top Viewed Peakd). This results in batching multiple requests via `Promise.all()`. I thin...There are situations where I need to query multiple posts. For example when trying to create a feed based on different metrics than supported (i.e: Top Viewed Peakd). This results in batching multiple requests via `Promise.all()`. I think it would be better if an array of author/permlink could be set, which returns an array of posts, making only a single request.https://gitlab.syncad.com/hive/hivemind/-/issues/137Extract 'image' and 'users' metadata form the post/comment content and includ...2021-05-17T21:33:31ZSergioExtract 'image' and 'users' metadata form the post/comment content and include in the API responseMost frontends right now include some additional metadata for posts and comments. Usually at least `image` and `users` are provided.
I think will be cleaner to drop those metadata when publishing a post/comment and compute both those fi...Most frontends right now include some additional metadata for posts and comments. Usually at least `image` and `users` are provided.
I think will be cleaner to drop those metadata when publishing a post/comment and compute both those fields (array) in Hivemind. The fields will always be provide in the API response as it is right now.
This way Hivemind will not rely on data provided in the operation (that are not guaranteed to be up to date with the post content) and can also provide those field for posts published without including those values (improving consistency).https://gitlab.syncad.com/hive/hivemind/-/issues/125Implement the other community types included in the original design doc2021-03-13T14:38:07ZSergioImplement the other community types included in the original design docAccording to [this doc](https://gitlab.syncad.com/hive/hivemind/-/blob/master/docs/communities.md) there should have been 3 types of communities.
We have the first one, but still missing the second and third option:
1. ~~**Topic**: any...According to [this doc](https://gitlab.syncad.com/hive/hivemind/-/blob/master/docs/communities.md) there should have been 3 types of communities.
We have the first one, but still missing the second and third option:
1. ~~**Topic**: anyone can post or comment~~
2. **Journal**: guests can comment but not post. only members can post.
3. **Council**: only members can post or comment
This has been discussed in this [Hive Dev meeting](https://gitlab.syncad.com/hive/tasks_without_projects_yet/-/issues/29) and I'm opening the ticket to start a discussionHowoHowohttps://gitlab.syncad.com/hive/hivemind/-/issues/122API: Query JSON Metadata2021-05-17T21:30:01ZtherealwolfAPI: Query JSON MetadataI've talked about this with @dan shortly before and the idea is to be able to store data within the users JSON meta-data and being able to query it directly.
*Example:*
My app has a user with id `123` and the user connects a Hive accou...I've talked about this with @dan shortly before and the idea is to be able to store data within the users JSON meta-data and being able to query it directly.
*Example:*
My app has a user with id `123` and the user connects a Hive account and adds `appId: 123` to the meta-data. I'm then able to query metadata via API to get hive account where `appId` within `json_metadata` or `posting_json_metadata` equals `123`.
API structure would be:
```
type KeyType = 'posting' | 'active'
queryJsonMetadata(
key: string,
value: string,
type: KeyType | KeyType[]
): HiveAccount | HiveAccount[]
```
Raw SQL is something like
```
SELECT * FROM "users" WHERE CAST ("posting_json_metadata" -> key AS STRING) = value
```
Would be great if this could get a somewhat high priority as certain features within my app depend on this API functionality.https://gitlab.syncad.com/hive/hivemind/-/issues/108Allow 'reblog' to a specific community2021-05-17T21:37:17ZSergioAllow 'reblog' to a specific communityCurrently users can 'reblog' a post originally published into a community into their own blog. Would be nice to be able to 'reblog' into other communities too.
And while sharing it should be possible to provide a little context from the...Currently users can 'reblog' a post originally published into a community into their own blog. Would be nice to be able to 'reblog' into other communities too.
And while sharing it should be possible to provide a little context from the user doing the reblog. Basically a short text to explain why the reblog has been done and why it is relevant for a specific community)https://gitlab.syncad.com/hive/hivemind/-/issues/95Allow user to 'pin' posts in their own blog2021-01-04T13:27:26ZSergioAllow user to 'pin' posts in their own blogThis is very similar to what it's available for communities, I think we should allow users to PIN posts in their own blog too.This is very similar to what it's available for communities, I think we should allow users to PIN posts in their own blog too.