Return-path: Envelope-to: fb@vin-fm.com Delivery-date: Mon, 08 Apr 2013 21:26:13 +0700 Received: from outmail012.snc7.facebook.com ([69.171.232.146]:44039 helo=mx-out.facebook.com) by server01-iix.secureserver.web.id with esmtp (Exim 4.80) (envelope-from ) id 1UPD1Q-0008Te-Hn for fb@vin-fm.com; Mon, 08 Apr 2013 21:26:13 +0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=facebookmail.com; s=s1024-2011-q2; t=1365430766; bh=fIKxKaIajn7TjpqfiP1fGcxR63cqe2rSIFfWzk0d2gQ=; h=Date:To:From:Subject:MIME-Version:Content-Type; b=Mya4y+Kgs2AWth4N+FtIA/MuGxGuo3RTP19Los5pEZcnN660ANGpDbXPNvd0gvJGO NJa3yp/im3M02+TbBTW4tOBvSRMfAcqZDcudq94Mhs2vgQdKlb3C2tO7VV90x1mlQP Db/8Gzmci8BAFAxDsECqt7L/U7Icx+ORcQ5UItAU= Received: from [10.79.27.43] ([10.79.27.43:42490]) by smout008.snc7.facebook.com (envelope-from ) (ecelerity 3.5.1.37927 r(/root/Momo-dev:tip)) with ECSTREAM id DC/62-08830-DE1D2615; Mon, 08 Apr 2013 07:19:26 -0700 X-Facebook: from zuckmail ([MTI3LjAuMC4x]) by async.facebook.com with HTTP (ZuckMail); Date: Mon, 8 Apr 2013 07:19:25 -0700 To: fb@vin-fm.com From: "Facebook" Subject: Developer Blog Weekly Digest for Apr 8, 2013 Message-ID: <17f11f450b7da847989a95f9396b8ff8@async.facebook.com> X-Priority: 3 X-Mailer: ZuckMail [version 1.00] X-Facebook-Notify: ; mailid= X-FACEBOOK-PRIORITY: 0 X-Auto-Response-Suppress: All MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="b1_17f11f450b7da847989a95f9396b8ff8" --b1_17f11f450b7da847989a95f9396b8ff8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Halo Vincent, Here are all the posts from the Developer Blog in the last week. Facebook Home, 5 April pukul 1:00 Published by Jenny Yuen Today we announced Facebook Home on Android, which is the mobile = experience designed to put your friends at the center of your phone. For = developers, Home enables new ways to surface your content to help people = discover your app and reengage with existing users. These include: Cover feed: With Home, people can immediately access your app content from = their News Feed once they turn on their phone. We also make it easy for = people to engage with your content as they can simply double tap to like a = post and comment right from cover feed. At launch, Open Graph stories with = user generated photos will be supported in cover feed. Click here for a = complete list of the story types that cover feed supports now. Notifications: People will receive bigger, bolder notifications from you = right on their phone home screen. We=E2=80=99ve made improvements to = notifications to make them more engaging and easier for people to interact = with. It=E2=80=99s never been easier to reengage with people using your = app. Chat heads: We=E2=80=99ve optimized messaging so that people can = seamlessly receive messages in a non-intrusive fashion while they're using = your apps. This will help improve engagement as it lets people jump in and = out of conversations without ever having to leave your app. App launcher: Home=E2=80=99s launcher makes it easy for people to get to = your apps quickly. People choose what's on their app launcher and = it=E2=80=99s simple for them to get your app in there. Cover feed Notifications Chat heads We=E2=80=99re excited to give you new ways to engage with people through = Home. This release is a first step and we'll continue to improve Home - = including enabling support for additional Open Graph story types. Learn = more about Home. ---------- New APIs for Comment Replies, 4 April pukul 7:38 Published by Alex Madjar Last week, we launched comment replies on Facebook pages and profiles with = more than 10,000 followers. This allows businesses and celebrities to = engage with their fans more directly. Today, we=E2=80=99re updating the = API so developers can build tools that make it easier for brands to = monitor and respond to comment replies. API Updates Our API now supports different "views" of the comments on posts through = our updated comments API and FQL comment table. Top Level Comments The first view of the comments on a post is called "top level". The = comments that are on the post (and are not replies to individual comments) = are called "top level comments." Top level comments may be ranked, = depending on the post and the number of top level comments on that post so = far. The top level view of comments corresponds to what a user would see on = Facebook. To get the top level view of comments in Graph API: GET {object_id}/comments?filter=3Dtoplevel In FQL, you can issue the request: SELECT id, fromid, time, text, likes=20 FROM comment=20 WHERE object_id=3D{object_id} AND parent_id=3D'0' Replies Comments on comments are called "replies." You get replies by querying = for the comments on a comment id. Graph API: GET {comment_id}/comments FQL: SELECT id, fromid, time, text, likes=20 FROM comment=20 WHERE parent_id=3D{comment_id} Comment Stream Another view of the comments on a post is the "stream". The comments = "stream" gives all comments (top level and replies to comments) together. = The "stream" view provides comments in chronological order, so it's easy = for you to just get what's new. Graph API: GET {object_id}/comments?filter=3Dstream FQL: SELECT id, fromid, time, text, likes=20 FROM comment=20 WHERE object_id=3D{object_id}=20 ORDER BY time Getting Started with the APIs To get started today with the new APIs, opt into the "July 2013 Breaking = Changes" migration for your app by visiting the Advanced tab of your app = dashboard. If you're currently using our existing comments APIs, here are a few = changes to keep in mind: 'comments' field from 'stream' FQL table is deprecated. Please use = the'comment_info' column to fetch the 'can_comment' and 'comment_count' = fields. We are removing the fields on the FQL 'comment' table that were used = exclusively for legacy Comments Plugins -- 'xid', 'reply_xid', 'username' = and 'comments'. We are removing the undocumented 'count' field on the 'comments' = connection in the Graph API. Please request = '{id}/comments?summary=3Dtrue' explicitly if you would like the summary = field which contains the count (now called 'total_count') Please read the documentation for details on how to use these new features = and the Roadmap for details on the API changes. We're excited to continue working with you, our community of developers, = to improve the quality of the conversations happening on Facebook and = can't wait to see what you build. ---------- Platform Updates: Operation Developer Love, 4 April pukul 7:27 Published by Sean Quinlan Since last Wednesday's post, we announced all the events in April we will = be attending. Defaulting new apps to sandbox mode Starting today, all newly created apps will be in "sandbox mode" by = default. This hides your app for people not listed as admins, developers = or testers, so you can build your app without worrying about other people = accessing it. When you are ready to take your app live, sandbox mode can = be toggled off in the basic settings area of the App Dashboard. Image requirements for the new News Feed We are rolling out the new design for News Feed, which is optimized for = sharing high-resolution images of Open Graph, feed, and share stories on = web and mobile. To prepare for a broader roll-out of the new design, = images must be at least 200x200 pixels for desktop web and ideally, = 600x600 pixels or greater for the best experience across devices. Images may not appear in the new design if they are smaller than 200x200 = pixels, and rectangular photos may be cropped. Image requirements include:=20 * 4 Megapixel limit * 5MB limit * direct links to the image only * only JPG, PNG, GIF, or BMP file formats We strongly encourage you to make sure your images meet these = requirements, so that the rollout does not negatively impact your app. April 2013 breaking changes As announced in January, the following change has gone into effect = permanently for everyone starting today: Removing ability to POST to USER_ID/questions=20 As it's no longer possible for users to create questions, we will remove = this functionality from the Graph API. POSTs to USER_ID/questions will = fail. July 2013 breaking changes (90-day notice) The following changes can be enabled/disabled using the "July 2013 = Breaking Changes" migration until July 10th when they will go into effect = permanently for everyone: Social plugins will require an absolute URL in the 'href' parameter=20 Social plugins, such as the Like Box and Like Button, will require an = absolute URL in the 'href' parameter. =20 Page 'category' field name change We are renaming the 'category' field to 'category_lists' for Pages Graph = API =20 Stream table will throw exception with invalid filter_key Query stream_filter table for a set of valid stream filters. The stream = table will throw an exception if called with an invalid 'filter_key' = option. =20 Removing 'publish_checkins' permissions Publishing a Checkin object is deprecated in favor of creating an Open = Graph story with a location attached. You can also create a Post with a = location attached using the 'publish_action' permission. =20 FQL Checkin table 'page_id' change We are renaming 'page_id' to 'target_id' for the Checkin table. =20 Removing 'version' field for Groups We introduced 'version' field to indicate whether the group was created = prior to launch of the current groups product in October 2010. We are = removing this field as all Groups on Facebook are now the same version. = This impacts both Group Graph API and Group FQL Table. =20 Photos will no longer return larger sizes than the uploaded version =20 'images' field in photos and photo_src table will no longer return image = sizes larger than the original uploaded version of the photo. =20 Cannot create multiple create actions for the same Open Graph object =20 We are no longer allowing multiple create actions for the same Open = Graph object, as documented here. =20 Deprecating 'comments' field from 'stream' FQL table =20 We are deprecating the 'comments' field from 'stream' FQL table. Please = select the 'comment_info' column to fetch the 'can_comment' and = 'comment_count' fields (formerly called 'can_post' and 'count'), and use = the comment table directly to retrieve the list of comments. =20 Removing 'xid', 'reply_xid', 'username' and 'comments' from 'comment' = FQL table We are removing the fields on the FQL 'comment' table that were used = exclusively for legacy Comments Plugins -- 'xid', 'reply_xid', 'username' = and 'comments'. We now treat comments the same across plugins and within = Facebook. Please query for comment replies left on the plugin the same way = as you would for other comments. =20 Removing 'count' from 'comments' Graph API connection We are removing the undocumented 'count' field on the 'comments' = connection in the Graph API. Please request = '{id}/comments?summary=3Dtrue' explicitly if you would like the summary = field which contains the count (now called 'total_count') The following changes will go into effect on July 10, 2013: Mobile App Install Ads change We are updating the Creative Spec parameter 'app_platform_type' to = 'mobile_store'. The possible values for mobile_store are now "itunes", = "itunes_ipad", and "google_play". =20 Conversion spec and tracking pixel ID changes We are deprecating the use of 'tracking_pixel_id' when specifying the = desire to track a conversion pixel in an ad. You should instead specify = the pixel in the newly launched tracking_specs field. We are also deprecating the use of conversion specs in bid types that = are not optimized for actions (e.g. CPM, CPC, and oCPM when no bid value = is placed on actions). You should instead use tracking_specs to track = conversions for these bid types. =20 Custom Audiences change We have changed the targeting spec parameter 'excluded_user_adclusters' = to be 'excluded_custom_audiences'. Additionally, the endpoint to create = and retrieve your custom audiences is now: = https://graph.facebook.com/(act_adaccountid)/customaudiences. =20 Accessing link stats change =20 App access tokens will be required for accessing the link_stat FQL = table. App access tokens will also be required for retrieving data from = Graph API endpoint for link stats, ie: = http://graph.facebook.com/?id=3Dhttp://example.com. =20 Graph API search changes App access tokens will be required for all search Graph API calls except = Places and Pages. Search for application will no longer be supported. =20 Open Graph apps using custom actions for fitness, books, movies, and TV As announced in March, any apps that previously used custom actions to = represent this type of sharing will need to move to common actions by July = 10, 2013. =20 Removing 'page_friends_of_fans' metric We are removing the metric: 'page_friends_of_fans' from the Insights = Dashboard and the Insights API. =20 Removing the ability to "Select All" or "Pre-Select" for Requests As part of our efforts to improve user sentiment, we have updated our = platform policy so that apps may not offer a select all option or = pre-select multiple recipients to receive requests. Other Request dialog = functionality will remain the same. Weekly stats The following stats are for activity between 03/27/2013-04/03/2013: Bugs activity 185 bugs were created 34 bugs were assigned 179 bugs were resolved 30 bugs were fixed 149 bug were were duplicate, invalid, or by design Bugs fixed 500 Error on oauth Custom Audience gone, recieving error #U8I8 New news feed doesn't add fb_action_ids and fb_ref to outbound links Apostrophe showing hex code in recommendatrions box Stories published via feed dialog no longer appear in the news feed or = games feed Recommentations Plugin - Querystring Error in related questions FB.getLoginStatus/ auth.statusChange not firing in Galaxy S3 native = browser auth_type=3Dreauthenticate not prompting users to enter password URGENT: App Settings Not Saving payment_success variable not found Related questions links are broken Image not shown Unclear distinction between screenshot examples for Action Tagging and = Mention Tagging 500 error on bugs search Sending a User to Login with OAuth gives them a "Not Logged In" Page mobile Feed and bookmark links route players to App Store instead of the = app Typo - change 'user' to 'request' Auth fails when app doesn't support backgrounding in iOS SDK=20 Update adgroup with pagepost creative : wrong post is assigned No Activity At App Timeline Missing image for 'Server-side Login' section. Need to mention caveat for posting to a friend's wall related to Timeline = privacy settings Out-of-date screenshot. Missing double quote symbol (") "What's New in 3.2" iOS SDK page points to 3.2 SDK package, but 3.2.1 is = available Character encoding is no longer being returned for content type for /me = graph call Error in code js Inconsistent Page insights after end_date 2013-03-13T07:00:00 Oauth returning a server error page on both new authentications and = existing logins. Started around 9pm CST on May 26, 2013 Activity on facebook.stackoverflow.com 321 questions asked 49 questions with a score of 1 or greater 15 answered, 31% answered rate 26 replied, 53% reply rate ---------- =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ___________________ This message was intended for fb@vin-fm.com. Anda menerima surel ini = karena anda telah memilih untuk menerima pembaruan pengembang dari = Facebook. Ingin mengendalikan pembaruan pengembang mana saja yang anda = terima? Pergi ke: http://developers.facebook.com/settings Facebook, Inc., Attention: Department 415, PO Box 10005, Palo Alto, CA = 94303 --b1_17f11f450b7da847989a95f9396b8ff8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Facebook
facebook
Halo Vincent,
Here are all the posts from the Developer = Blog in the last week.
 

3D"Jenny
5 April pukul 1:00
Published by Jenny = Yuen

Today we announced Facebook = Home on Android, which is the mobile experience designed to put your = friends at the center of your phone. For developers, Home enables new ways = to surface your content to help people discover your app and reengage with = existing users. These include:

Cover feed: With Home, people can immediately access = your app content from their News Feed once they turn on their phone. We = also make it easy for people to engage with your content as they can = simply double tap to like a post and comment right from cover feed. At = launch, Open Graph stories with user generated photos will be supported in = cover feed. Click here for a = complete list of the story types that cover feed supports now.

Notifications: People will receive bigger, bolder = notifications from you right on their phone home screen. We=E2=80=99ve = made improvements to notifications to make them more engaging and easier = for people to interact with. It=E2=80=99s never been easier to reengage = with people using your app.

Chat heads: We=E2=80=99ve optimized messaging so that = people can seamlessly receive messages in a non-intrusive fashion while = they're using your apps. This will help improve engagement as it lets = people jump in and out of conversations without ever having to leave your = app.

App launcher: Home=E2=80=99s launcher makes it easy = for people to get to your apps quickly. People choose what's on their app = launcher and it=E2=80=99s simple for them to get your app in there.


Cover = feed

Notifications

Chat = heads

We=E2=80=99re excited to give you new ways to engage with people = through Home. This release is a first step and we'll continue to improve = Home - including enabling support for additional Open Graph story types. = Learn more about = Home.


 

3D"Alex
4 April pukul 7:38
Published by Alex = Madjar

Last week, we launched comment replies on Facebook pages = and profiles with more than 10,000 followers. This allows businesses and = celebrities to engage with their fans more directly. Today, we=E2=80=99re = updating the API so developers can build tools that make it easier = for brands to monitor and respond to comment replies.

API Updates

Our API now supports different "views" of the comments on posts through = our updated comments API and FQL = comment table.

Top Level Comments

The first view of the comments on a post is called "top level". The = comments that are on the post (and are not replies to individual comments) = are called "top level comments." Top level comments may be ranked, = depending on the post and the number of top level comments on that post so = far.

The top level view of comments corresponds to what a user would see on = Facebook. To get the top level view of comments in Graph API:

GET {object_id}/comments?filter=3Dtoplevel

In FQL, you can issue the request:

SELECT id, fromid, time, text, likes=20
FROM comment=20
WHERE object_id=3D{object_id} AND parent_id=3D'0'

Replies

Comments on comments are called "replies." You get replies by querying = for the comments on a comment id.

Graph API:

GET {comment_id}/comments

FQL:

SELECT id, fromid, time, text, likes=20
FROM comment=20
WHERE parent_id=3D{comment_id}

Comment Stream

Another view of the comments on a post is the "stream". The comments = "stream" gives all comments (top level and replies to comments) together. = The "stream" view provides comments in chronological order, so it's easy = for you to just get what's new.

Graph API:

GET {object_id}/comments?filter=3Dstream

FQL:

SELECT id, fromid, time, text, likes=20
FROM comment=20
WHERE object_id=3D{object_id}=20
ORDER BY time

Getting Started with the APIs

To get started today with the new APIs, opt into the "July 2013 = Breaking Changes" migration for your app by visiting the Advanced tab of = your app dashboard.

If you're currently using our existing comments APIs, here are a few = changes to keep in mind:

  • 'comments' field from 'stream' FQL table is deprecated. Please use = the'comment_info' column to fetch the 'can_comment' and 'comment_count' = fields.

  • We are removing the fields on the FQL 'comment' table that were = used exclusively for legacy Comments Plugins -- 'xid', 'reply_xid', 'username' and = 'comments'.

  • We are removing the undocumented 'count' field on the 'comments' = connection in the Graph API. Please request = '{id}/comments?summary=3Dtrue' explicitly if you would like the summary = field which contains the count (now called 'total_count')

Please read the documentation for details on how to use these new features = and the Roadmap for details = on the API changes.

We're excited to continue working with you, our community of = developers, to improve the quality of the conversations happening on = Facebook and can't wait to see what you build.


 

3D"Sean
4 April = pukul 7:27
Published = by Sean = Quinlan

Since last Wednesday's post, we announced = all the events in April we will be attending.

Defaulting new apps to sandbox mode

Starting today, all newly created apps will be in "sandbox mode" by = default. This hides your app for people not listed as admins, developers = or testers, so you can build your app without worrying about other people = accessing it. When you are ready to take your app live, sandbox mode can = be toggled off in the basic settings area of the App Dashboard.

Image requirements for the new News Feed

We are rolling out the new design for News Feed, which is = optimized for sharing high-resolution images of Open Graph, feed, and = share stories on web and mobile. To prepare for a broader roll-out of the = new design, images must be at least 200x200 pixels for desktop web and = ideally, 600x600 pixels or greater for the best experience across = devices.

Images may not appear in the new design if they are smaller than = 200x200 pixels, and rectangular photos may be cropped.

Image requirements include:=20 * 4 Megapixel limit * 5MB limit * direct links to the image only * only JPG, PNG, GIF, or BMP file formats

We strongly encourage you to make sure your images meet these = requirements, so that the rollout does not negatively impact your app.

April 2013 breaking changes

As announced in January, the following = change has gone into effect permanently for everyone starting today:

Removing ability to POST to USER_ID/questions
As it's no longer possible for users to create questions, we will remove = this functionality from the Graph API. POSTs to = USER_ID/questions will fail.

July 2013 breaking changes (90-day notice)

The following changes can be enabled/disabled using the "July 2013 = Breaking Changes" migration = until July 10th when they will go into effect permanently for = everyone:

Social plugins will require an absolute URL in the 'href' = parameter
Social = plugins, such as the Like Box and Like Button, will require an = absolute URL in the 'href' parameter.

=20

Page 'category' field name change
We are renaming the 'category' field to 'category_lists' for Pages = Graph API

=20

Stream table will throw exception with invalid = filter_key
Query stream_filter table for a set of valid stream filters. The stream table will throw an exception if called with an invalid = 'filter_key' option.

=20

Removing 'publish_checkins' permissions
Publishing a Checkin object is deprecated in favor of creating an Open = Graph story with a location attached. You can also create a Post with a location = attached using the 'publish_action' permission.

=20

FQL Checkin table 'page_id' change
We are renaming 'page_id' to 'target_id' for the Checkin table.

=20

Removing 'version' field for Groups
We introduced 'version' field to indicate whether the group was created = prior to launch of the current groups product in October 2010. We are = removing this field as all Groups on Facebook are now the same version. = This impacts both Group = Graph API and Group = FQL Table.

=20

Photos will no longer return larger sizes than the uploaded = version
'images' field in photos and photo_src table will no longer return image sizes larger than the = original uploaded version of the photo.

=20

Cannot create multiple create actions for the same Open Graph = object
We are no longer allowing multiple create actions for the same Open = Graph object, as documented here.

=20

Deprecating 'comments' field from 'stream' FQL table =
We are deprecating the 'comments' field from 'stream' FQL table. Please = select the 'comment_info' column to fetch the 'can_comment' and = 'comment_count' fields (formerly called 'can_post' and 'count'), and use = the comment table directly to retrieve the list of comments.

=20

Removing 'xid', 'reply_xid', 'username' and 'comments' from = 'comment' FQL table
We are removing the fields on the FQL 'comment' table that were used = exclusively for legacy Comments Plugins -- 'xid', 'reply_xid', 'username' and 'comments'. = We now treat comments the same across plugins and within Facebook. Please = query for comment replies left on the plugin the same way as you would for other comments.

=20

Removing 'count' from 'comments' Graph API = connection
We are removing the undocumented 'count' field on the 'comments' = connection in the Graph API. Please request = '{id}/comments?summary=3Dtrue' explicitly if you would like the summary = field which contains the count (now called 'total_count')

The following changes will go into effect on July 10, 2013:

Mobile App Install Ads change
We are updating the Creative Spec parameter 'app_platform_type' to 'mobile_store'. = The possible values for mobile_store are now "itunes", "itunes_ipad", and = "google_play".

=20

Conversion spec and tracking pixel ID changes
We are deprecating the use of 'tracking_pixel_id' when specifying the = desire to track a conversion pixel in an ad. You should instead specify the pixel = in the newly launched tracking_specs field. We are also deprecating the use of conversion = specs in bid types that are not optimized for actions (e.g. CPM, CPC, = and oCPM when no bid value is placed on actions). You should instead use = tracking_specs to track conversions for these bid types.

=20

Custom Audiences change
We have changed the targeting spec parameter 'excluded_user_adclusters' = to be 'excluded_custom_audiences'. Additionally, the endpoint to create = and retrieve your custom audiences is now: = https://graph.facebook.com/(act_adaccountid)/customaudiences.

=20

Accessing link stats change
App access tokens will be required for accessing the link_stat FQL table. App access tokens will also be required for = retrieving data from Graph API endpoint for link stats, ie: = http://graph.facebook.com/?id=3Dhttp://example.com.

=20

Graph API search changes
App access tokens will be required for all search Graph API calls except = Places and Pages. Search for application will no longer be supported.

=20

Open Graph apps using custom actions for fitness, books, = movies, and TV
As announced in March, any = apps that previously used custom actions to represent this type of sharing = will need to move to common actions by July 10, 2013.

=20

Removing 'page_friends_of_fans' metric
We are removing the metric: 'page_friends_of_fans' from the Insights = Dashboard and the Insights API.

=20

Removing the ability to "Select All" or "Pre-Select" for = Requests
As part of our efforts to improve user sentiment, we have updated our = platform policy so that apps may not offer a select all option or = pre-select multiple recipients to receive requests. Other Request dialog = functionality will remain the same.

Weekly stats

The following stats are for activity between 03/27/2013-04/03/2013:

Bugs activity
  • 185 bugs were created
  • 34 bugs were assigned
  • 179 bugs were resolved
  • 30 bugs were fixed
  • 149 bug were were duplicate, invalid, or by design
Bugs fixed
Activity on facebook.stackoverflow.com
  • 321 questions asked
  • 49 questions with a score of 1 or greater
  • 15 answered, 31% answered rate
  • 26 replied, 53% reply rate

 


This = message was intended for fb@vin-fm.com. Anda menerima surel ini = karena anda telah memilih untuk menerima pembaruan pengembang dari = Facebook. Ingin mengendalikan pembaruan pengembang mana saja yang anda = terima? Pergi ke:
= http://developers.facebook.com/settings
Facebook, Inc., Attention: = Department 415, PO Box 10005, Palo Alto, CA = 94303
--b1_17f11f450b7da847989a95f9396b8ff8--