Facebook Methods description: photos.createAlbum
Creates and returns a new album owned by the current session user. See photo uploads for a description of the upload workflow. The only storable values returned from this call are aid and owner.
Facebook Hack: How to Easily Get Access to Limited Profile of Non-Friends
The following description is an easy way to get access to the limited profile of a user from which you should not be allowed to see any part of his (her) profile except a small picture and a name as you can see it on the following sample:
The only think to do is to send a message to the concerned user you want to get access to his limited profile and wait his answer (hoping he or she will answer).
As soon as he answer, Facebook authorize you to see the limited profile of the user for one week (date starting from the answer).
So as a user, don’t forget that when you answer to someone (who sent you a message) who is not in your friends list, you will allow this person to access your limited profile.
ps: if you like ore dislike this kind of post, please let me know.
.
.
Facebook Methods description: photos.addTag
Adds a tag with the given information to a photo. See photo uploads for a description of the upload workflow.
Facebook News (hack): XML Sitemaps & FBML? New Facebook Vulnerability? - Part 2 1st of April
Do you remember my past article with the following title:
“Facebook News (hack): XML Sitemaps & FBML? New Facebook Vulnerability?”
“
In a news from developers.facebook.com from March 12, 2008 and according to Alex Moskalyuk:
“Starting today, you can serve XML sitemaps off apps.facebook.com domain, and notify search engines about changes on your pages. Naturally, this works better for pages that display content without requiring logins.”
This is indeed a really nice news for apps developers… But this implies:
“Facebook will serve any file with “.xml.gz” extension without interpreting it through FBML parser.”
Might this “non-interpretation” be dangerous in any kind of way? A new vulnerability in Facebook?
Facebook Methods description: profile.getFBML
Gets the FBML that is currently set for a user’s profile. See the FBML documentation for a description of the markup and its role in various contexts.
Facebook Methods Description: Admin.getAllocation
Returns the current allocation limits for your application for the specified integration points. Allocation limits are determined daily. Integration points include:
Facebook Methods description: profile.setFBML
Sets the FBML for a user’s profile, including the content for both the profile box and the profile actions. See the FBML documentation for a description of the markup and its role in various contexts.
Facebook Methods description: notifications.sendEmail
Send an email to the specified users, who must have added your application. You can only send one email to a user per day. Requires a session key for desktop apps, which may only send emails to the person whose session it is (does not require a session for web apps).
Facebook Methods description: notifications.send
Send a notification to a set of users. You can send messages to the user’s notification page without needing any confirmation. Notifications sent to the notifications page for non-app users are subject to spam control. Additionally, any notification that you send on behalf of a user will be shown on that user’s notifications page as a “sent notification.”
Facebook News: Allocations to Email Sent From Applications to Users Feedback-based.
For some weeks now, users may have noticed that when they receive a private email from a Facebook application they get something like:
“This email was sent by xyz application. You can disable emails here.”
According to a news published by Tom Whitnah from Facebook, the rate at which users disable email from within an email message will, starting this week, primarily determine the static limit on the number of email messages an application can send to a given user per day. Facebook calls that a “user feedback-based allocation system”.
Still according to Tom, this will
“increase the value of email that applications send to users and to give users control over what email they want to receive.”
For users, this means that your feedback will be used to rate email limits an application will be able to send in the future to all his users.
For application developers, this means you will have to learn to use a new method: Admin.getAllocation 
