Is your feature request related to a problem? Please describe.
Right now there is only one type for channel subscriptions, and this is HOME or "" in api.
There are also types like:
1) Coubs: type="simples"
2) Reposts: type="recoubs"
3) Stories: type="stories". (json contains different objects from coubs. Should be parsed differently. Low priority.)
4) Likes: type="likes". (If you are logged in, then it shows your likes for channel. Won't have any affect for bot)
Tag subscriptions have only one type=""
Community subscriptions doesn't have type at all.
Describe the solution you'd like
1) Add new types for channel subscription. Probably db schema change.
2) Add rest controller for types with filter by subscription type
3) Add bot command to fetch types.
4) Modify subscription command for channel to accept types.
5) Add integration flow for such modifications.
Describe alternatives you've considered
None
Additional context
Stories can be done just by fetching link to story. And if user wants to see story, he just open link. Seems like there is not need fetch all coubs in story and send them in chat.
Is your feature request related to a problem? Please describe.
Right now there is only one type for channel subscriptions, and this is HOME or "" in api.
There are also types like: 1) Coubs: type="simples" 2) Reposts: type="recoubs" 3) Stories: type="stories". (json contains different objects from coubs. Should be parsed differently. Low priority.) 4) Likes: type="likes". (If you are logged in, then it shows your likes for channel. Won't have any affect for bot)
Tag subscriptions have only one type=""
Community subscriptions doesn't have type at all.
Describe the solution you'd like 1) Add new types for channel subscription. Probably db schema change. 2) Add rest controller for types with filter by subscription type 3) Add bot command to fetch types. 4) Modify subscription command for channel to accept types. 5) Add integration flow for such modifications.
Describe alternatives you've considered None
Additional context Stories can be done just by fetching link to story. And if user wants to see story, he just open link. Seems like there is not need fetch all coubs in story and send them in chat.