I am dealing with a problem that I would like to force all the users of a Yammer network to automatically join some groups (like HR) or follow some topics (like newsletters). I haven't been able to find any solutions to this topic that wouldn't require the users to accept the invitation to the group, except the All Network group that is joined automatically. For the force to follow I haven't been able to find anything...
So my questions are:
Is it possible to force all the users to join some group, other than the All Network group?
Is it possible to force all the users to follow some topic?
Is it possible to enforce that the users won't be able to leave the group/unfollow the topic?
If anyone would please know any answers it would be super helpful. Thank you all so much in the advance.
Is it possible to force all the users to join some group, other than the All Network group?
Yes. You can use the impersonation endpoint to programmatically add users to a group. You'd need to be the network's verified admin to be able to do this. See details here.
Is it possible to force all the users to follow some topic?
Yes. Using the same impersonation endpoint described above, and by sending a POST request to https://api.yammer.com/api/v1/subscriptions with topic_id and target_type = topic as params. See details here
Is it possible to enforce that the users won't be able to leave the group/unfollow the topic?
No.
Related
I'm looking for a solution or GitHub code that searches on a regular basis Slack and finds sensitive credentials (user name, password, etc) that employee shares in channels, and delete it.
Can you assist me?
There is no finished solution here. You can write code based on slack_cleaner2.
Channel communication is now handled by Conversations API and everything is described here.
we are implementing stream in our application and so far we love the out of the box react components as well as the backend implementation stream ruby - this is our setup currently.
We are close to deploying a first MVP but found that it seems to be not possible to post activities to a flat feed from multiple users by default.
Our use case is that we have a group of people that want to post activities about a certain topic (think facebook groups). Therefore we create a feed for the object (lets say a company) and want each user to be able to post activities there. Our current workaround is to add the author id as additional data and add a custom header to a activity - obviously not the best solution as reactions won't work that way.
Looking around we found that this seems to not work out of the box see this issue and this question.
Is this a feature that is only available to paying customers or how can we activate it?
Thank you in advance!
When using Stream with React users can only post to their own user feed, this is a default permission policy that can be changed by Stream.
I suggest reaching to Stream support by email and ask to change the permission policy.
Is it possible (via the Yammer REST API or otherwise) to programmatically retrieve a list of all unique users who have posted to a specific Yammer group?
The network in question is a free Yammer network, therefore the data export approach is not available.
There's currently no way to directly get a list of contributors to a group. What you could do is use the messages api to crawl through all of the messages in a group and get the users who sent them. If it's a group with a reasonable number of messages, this shouldn't be that big of a problem. Just don't forget about the rate limits on making api calls.
The message endpoint for a group looks like this.
https://api.yammer.com/api/v1/messages/in_group/{{group_id}}.json?threaded=extended
Suppose you have an online social service like Facebook that might make it interesting for companies to create many accounts (e.g. to "Like" their posts).
Of course, you want to prevent the users to do something like that. Lets say, ideally you want at most one user per real person (I think there are company accounts in Facebook, but Facebook was only an example!).
How can you make sure, that no person is able to create and use multiple accounts? Are there publications about this topic? (Preferably free and publicly available)
Related questions
A similar question was asked here and I had many ideas how to approach this problem (see my answer). But although the question is similar, my focus in this question are references that discuss the topic. References might be blog articles and websites, but I would prefer papers / books.
Questions
Are there publications
that describe how to identify fake users in general?
that describe how to use the social graph for identifying fake users?
(Are there other ideas I did not list in my answer?)
Clarification
It doesn't matter if users create multiple accounts. It's ok if they create one account, use it, lose their credentials and create a new one they use.
It is not ok to create multiple accounts to manipulate counts (e.g. Like, +1, YouTube clicks, responses to an article, ...)
See my answers here and here. They don't refer to any specific publications, which I would be surprised to see, because of so different reasons why addressing this problem in first place (see these links for more discussion on that) and that post about being user-friendly.
Does anyone know if (and how) I can build an application (Java/Ruby/whatever) doing REST or RPC calls to a social network like Orkut (using opensocial) to search for a user by name or email address? So far I know that I can list all friends for a particular user ID, but I want to search among all users. Would I need to code it as an app/gadget running inside the google sandbox or is there a way to get a list of matching user ID via REST?
So far I got this one to work: http://code.google.com/p/opensocial-ruby-client/wiki/GettingStarted. But with this API and the gadget linked there I only get people that are already linked to me...
Thanks for answers,
Martin
No, you can't do that. At least, OpenSocial doesn't have spec like that.
In addition, SNS normally have privacy policy which disables developers to poke around users who hasn't installed your app.
Think OpenSocial API access to private information is quite limited.