Clever Geek Handbook

GetStream and Activity Channels

I have an existing notification feed, but I'm looking at possibly going to GetStream.

I am currently using Laravel notifications to notify users and other objects.

I currently have something like the following:

1) Users 2) Groups 3) Group members

So, when I CRUD a group, I just notify all members of the group as well as the group ( $group->notifications

returns a collection) which works great.

Looking through the GetStream docs there seems to be a concept of "followers".

Does this mean that all members of the group must be followers of each other in order to see all notifications?

How about other objects, like getting a feed for a group? Do I need another one Group Type

in the toolbar to save the actions?

So, if I Person A and Person B are members of group 1, when Person A saves group 1, I would like Person A to see something like:

You saved Group 1

and Person B will see:

Person A saved Group 1

When I view the Group page, I would like to trigger the actions that happened to this group.

Is it possible?

thank

+3


source to share


1 answer


Does this mean that all members of the group must be followers of each other in order to see all notifications?

Probably not. Stream allows you to customize channel groups, following relationships and use "targeting" to send actions to different channels.

Based on the use case you described, you are probably best using two channel groups for example. group

and user_timeline

. You can provide each user with their own user timeline feed and customize it accordingly to other group feeds.

When a user does something related to a group, the activity can be added to the feed group

. This action is then propagated to all users who follow the group.



How about other objects, such as getting a feed for a group? Do I need a different type of group in the dashboard to save actions?

You can always create multiple channel groups for a given application. An example with two groups is probably sufficient for your use case, but you can continue with three groups ...

  • user

    : Custom messages sent to this channel. This channel will handle specific and non-group related activities. If the action belongs to a group, the "to" field can be filled with the name of the group, and this will cause the actions to be copied to that channel (and in turn passed on to its followers).
  • user_timeline

    : Received by users. Follows the feeds of groups. A user can also follow another user's user_timeline feed to receive all events from that user (for example, an asymmetric approach like Twitter / or symmetric like Facebook).
  • group

    : Retrieves user created actions using 'to' targeting. System / admin generated actions can also be added directly to the feed.
+2


source






More articles:


All Articles