I am try to implement location based feed in React Native app with getstream. For example user in New York only see only see feed post from other user in New York. If user in LA then user only see feed post from other user in LA.
So I am use geolocation. This possible with getstream?
There are multiple ways to do it:
add a custom property to activities and read the feed and ignore unrelated
add activities to different feed, simply decide while writing. For example, if an activity should be seen by LA, then write it to LA feed
contact support for personalization (paid though)
Related
I would like to build an Instagram-like social app, where on the user timeline, you also have his own activities displayed. My first thought was to follow his own user feed but from what I read in this blog post: https://getstream.io/blog/best-practices-for-instagram-style-feeds/
We recommend blocking a user's timeline feed from following their own user feed
Can someone explain why it would be a bad practice ? How could I implement my use case if that is the case ?
Thanks !
Looking at this myself. I think the logic they describe is incorrect. The full statement in context make a little more sense in terms of what I think they mean.
We recommend blocking a user's timeline feed from following their own
user feed, and also blocking users from seeing/following another
user's timeline feed.
The first part of the sentence I believe is backwards. What I think it should says is that the "user" feed should be blocked from following the "timeline" feed. The user feed should just contain actions that the user performed, so it shouldn't contain data from the timeline feed. But if you want the user's activities to appear in the timeline feed than it seems to me that you should definetly make the user's timeline feed follow thier user feed, and prevent the user's timeline feed from unfollowing their own user feed.
The second part that says you should block users from following another user's timeline feed. I believe this is correct because the timeline feed is a series of peronalised items for an individual user. It doesn't make sense to follow another user's timeline feed.
This is how I have implemented my logic and it seems to be working so far, but if I come across any issues with it I'll come back here and update this answer.
I'm looking to add a "company feed" to a corporate intranet SaaS application. More or less a timeline of posts very similar to facebook.
1) I think the Flat feed type is what I'd want for that but not sure.
2) I don't want users to have to "follow" one another. If you post on the company feed, everyone in the company should probably see it. How would you set this up on GetStream?
1) Yes, a flat feed is what you'd want.
2) If the users don't follow each other, everyone in the company posts to the same feed, and the same feed is shown to everyone in the company, then the best option is probably to set up a single feed group (timeline, maybe), with one feed in it (timeline:company1234) that everyone posts to and reads from.
Then, whenever a user posts on the company's feed, you'll add an activity to the timeline:company1234 feed, and whenever someone needs to read the feed, you'll retrieve the activities from the timeline:company1234 feed.
In my application, I have a 'user_post' feed which is responsible for storing the posts of a user. I would like a way to retrieve the likes of each individual post.
If I added a feed called 'post_like' I could store the likes of each post in their own feed. Is this approach efficient?
I'd suggest using a notification feed for that, not a flat feed. Set the verb to 'like' or whatever is appropriate for your app, and the actor is the user who 'liked' the original activity. When you call the user's notification feed, you'll get a list of all users who liked it.
If you store the likes in your own database and send the like to us with a foreign ID then you can always remove the activity later if they 'un-like' something afterward.
I have this scenario:
A user follows a feed and they receive all of that feed's current posts as new posts (via realtime notification.. likely caused by a fanout)
While its accurate that all that feed's items are new to the follower, I'd like to stop the notification from appearing..Is it possible to disable the fanout notification when a feed follows another?
We don't currently have a way to suppress realtime notifications upon follow. The only way I think you could accomplish this would be for User A to follow User B without copying any old items, but then User A would only see new activities going forward.
I'll mention this to the team as a feature request.
In SharePoint 2013 we have a about me for all the employees that work at our company.
I would like to get for example all the employees that have filled in a twitter account in their ABOUT ME page in SP2013.
So I could do something with their twitter account, all be storing it in a array.
Im using a sharepoint hosted app, so the preffered programing language is jscript.
The question is how to get this data out of the about me for all employees?
The "About Me" page in SharePoint is really just a UI layer for data specific to the User whose page you're on; for the data you describe, it sounds like your users have the ability to add to their User Profile their Twitter handle.
If that's the case, it's fairly straightforward to query data from the User Profile Service using the JSOM (JavaScript Object Model). This MSDN article should be more than enough to get you started: http://msdn.microsoft.com/en-us/library/office/jj920104%28v=office.15%29.aspx
A note of guidance; if your users are instead putting their Twitter handle inside some block of multi-line text, like say a "Summary" property on their User Profile, I would strongly recommend updating your User Profiles to include a custom property for storing their Twitter handle (reference here). SharePoint makes it fairly easy to add custom User Profile properties and so having to otherwise parse something like a Twitter handle out of a block of text would be unnecessarily complicated & likely perform worse.