Hi I have a facebook quiz application. When a user comes to the app then he will see questions about his/her friend. Now once user answer or clicks yes/no the app will make publish to his friend's wall.
No when I see in application >> insight >> diagonastic I can see user limit
limit per user, per day : 50
Now my question is if my application has 5000 daily visitors and each user posts 10 answers to their friends' wall then my app will be deleted by facebook? Is there any way to track or limit postings?
Thanks
No, you don't need to worry about app banning, because that after the limit, every post your application makes will results in an error from Facebook ("post limit exceed", something like that). But still be careful because if you post too much, very likely users will report your application as spam, and it may get banned.
To track limit postings, you can simply write your own trackings (record to database when user request to post, for example).
Related
I am trying to construct a Top 5 of engaged users and users that liked something on my Facebook page(a non-profit)(for instance posts, links or images). It has to be an aggregated total of engagement and likes for all items on the page per user.
Can anybody provide with some clues as to which Facebook API calls I could use for this. At this moment I am only capable of determining which users liked the page, or a particular post.
If the question is too general or anything else, I'll gladly modify it. I would have liked to attach image for clarification, but is not a possibility for me yet due to reputation score.
The only way to do this is to get all likes/comments/whatever from every single post with the API, store the numbers in your database and compare User IDs. You would have to keep it up to date too, so you would need to refresh your database entries from time to time.
What features would have my canvas app to submit application on App Center?
Facebook give me this response:
Ineligible Submission
Your app does not have high enough ratings and user engagement to be eligible for the App Center at this time.
What could I do to enhance my rating and user engagement?
I agree, its not a very helpfull message from facebook, how to get high ratings how much user engagement, they don't tell you this information before you start to write an app!
Some advice from a facebook guy, not me ...
There are no numbers because it is not as simple as you need more than 1000 users and a rating higher than 4. We weigh both user engagement and ratings together with other stuff to try to figure out what a high quality app is.
There are several other ways your can get visibility. Publish Open Graph stories and using Requests are 2 things you can do.
I have build a Facebook-app that needs to post to the users wall in certain situations. I've come a long way in doing this: it works perfectly, even when the user is not logged in. However, I need to post to the user's wall on behalf of the app, not the user himself. The reason is that posting as the user will not trigger a notification.
Does anybody know how to do this?
This is not possible; apps cannot post to the profiles of users - if you want someone to come back to your app, you could use a Request which will increment the counter on the user's bookmark for your app, but it's not possible to post to a user's profile 'from' a page or application
Our users can invite their friends to our app by posting to their friends' walls. Some users have gotten really excited and invited hundreds of their friends (woohoo!), but we're constantly getting the "(#341) Feed action request limit reached" Oauth error and these never make it to any walls (argh).
I know FB limits the posts per user per day (I can see we're limited to 30/user/day in my insights page and the first 30 that were sent seem to go out) but it's been over 36 hours since the last post and I'm still getting "Feed action request limit reached" Oauth errors.
Should the limit have reset at this point? Is there a way to see if they're being blocked because FB thinks they're spam?
You'll probably get disconnected by anti spam systems if you're using wall posts as an invite mechanism - posts like that get blocked and removed quite a lot by the target users.
To answer your question, the feed action limit is a rolling window as far as i know, so doesn't reset after 24 hours exactly - if the API call fails just wait and try again later - I don't think using the Feed Dialog is subject to the same limits because it's manually approved by the user instead of just being up to the app to ensure policy compliance
My spec says 30 days. I am about to argue for quite a longer TTL, something like 90 - 120 days. What do you think?
This is for a standard website, not an intranet app.
My personal advice would be to do it as a combination of relatively-short expiration cookie with sliding expiration and a long expiration identity cookie.
The first part is your standard week/month-long expiration authentication ticket cookie, which you renew on each request or at certain time interval, or whatever other sliding expiration scheme you want to employ.
The second part is you remember the identity of the user in a half year/year-expiration cookie. This is not an authentication ticket, just an identity reminder, so that if the user returns after their session has expired, they get greeted and you might choose to show some non-sensitive personal information, like number of emails in inbox or anything like that, but to actually access any sensitive information, they need to authenticate themselves.
This will give your regular users (visiting every day or week) continuous never-expiring session, while still keeping the authentication tickets with relatively short time frame. At the same time, for people that return after more than a month, you can still give them a personalized experience, yet their account is secure. I don't think anyone would actually have a problem, if you ask them to authenticate to access certain parts of their account after a month of absence, even if they'd checked the remember me/remember my password checkboxes.
It Depends is the most natural answer. Additionally, we should also ask the user if it's a personal laptop or shared workstation or a public machine.
If Is it a social network or a mail portal or something similar than 2 weeks. in case of personal workstation >4 weeks. If it's a banking system then there's nothing like Remember Me and persistent auth. In fact session should be terminated for no activity in last 15 minutes.
So It depends.
Its depends upon whos using the system. If its an employee of a company using his assigned computer regularly and one of the intranet site sets up "remember me" cookie it can be longer a year or more.