Connect with us

FACEBOOK

Legislator mocks trans Biden nominee on Facebook, apologizes

Published

on

HARRISBURG — A Pennsylvania legislator shared on Facebook an image mocking the appearance of the state’s recently departed health secretary, Dr. Rachel Levine, a transgender woman who has been nominated to serve in the Biden administration, and then offered a general apology Saturday.

State Rep. Jeff Pyle, a Republican from Armstrong and Indiana counties, said on Facebook that he “had no idea” the post mocking Levine “would be … received as poorly as it was” but that “tens of thousands of heated emails assured me it was.”

“I got my ass kicked,” Pyle said Monday. “It’s still being kicked.”

The fallout from Pyle’s post continued to mount. He said he’s as contrite as he can be.

Advertisement
free widgets for website

“My perspective is this. I screwed up,” he told the Gazette. “And I’m willing to admit I screwed up and I’m sorry that I hurt people by screwing up and I won’t do it again. But I think people calling for my resignation are premature.”

Pyle weighed the outcry Monday from his office in the state capitol, while he said he and colleagues were drafting a series of bills to excuse liquor license holders from certain Pennsylvania Liquor Control Board rules during the pandemic.

“I owe an apology and I offer it humbly,” Pyle wrote Saturday on his Facebook page, not specifically apologizing to Levine or other transgender people, but later repeating an apology “to all affected.”

Levine has not commented. The state health department did not immediately respond to an email seeking a reaction to Pyle’s initial post or his apology.

Comments on his Facebook page had called for him to resign.

Advertisement
free widgets for website

President Joe Biden tapped Levine a day before his inauguration be his assistant secretary of health, leaving her poised to become the first openly transgender federal official to be confirmed by the U.S. Senate.

See also  Build a Smart Bookmarking Tool with Rust and Rocket

Pyle, who was first elected in 2004, cited a conversation with the Democratic leader in the state House “who explained the error of my post.”

He stressed that he did not come up with the meme but merely shared it, though he said he should not have done so.

“From this situation I have learned to not poke fun at people different than me and to hold my tongue. Be a bigger man,” he wrote.

“It’s pretty discouraging right now; it’s pretty bleak,” Pyle elaborated Monday. “There’s thousands of people telling me what an (profanity) I am, and I’ll cop to it, I am an (profanity). But what I did compared to what they’re doing to me is not even close … it’s savage, man.”

Advertisement
free widgets for website

Pyle again pledged that he’s finished with such posts on Facebook.

“I’m not going to be doing it again,” he said. “People want me to quit, but I’m not gonna do that. I’ve got a college I gotta build. That’s the end-all, be-all. Then when I’m done with that, maybe I’ll think of quitting. But not before then.”

Pyle, who was unopposed in November for his election to a ninth term in the state house, is being treated for cancer and recovering from a stroke.

Pyle wrote he would leave Facebook “soon” but was not resigning from his position and would focus on a Butler Community College project and the economic revitalization of Pennsylvania amid the COVID-19 pandemic.

Advertisement
free widgets for website

Copyright 2021 The Associated Press. All rights reserved. This material may not be published, broadcast, rewritten or redistributed without permission.

See also  Facebook streamlines the settings page on mobile

Read More

Continue Reading
Advertisement free widgets for website
Click to comment

Leave a Reply

Your email address will not be published.

FACEBOOK

Messenger Private Reply Updates for the Developer Community

Published

on

By

messenger-private-reply-updates-for-the-developer-community

Private Replies allows a business’ Facebook Page to send a single message to a person who published a post, who commented on a post or commented on the Page.

Support for Private Reply for Groups

In September, we extended this support for Facebook Groups, allowing businesses to be able to send private replies to a person who commented on their Page’s post in Facebook Groups.

How it Works

To send a private reply to a post or comment, send a POST request to the /PAGE-ID/messages endpoint with the recipient parameter set to the post_id or comment_id and the message parameter set to the message you wish to send.

The following example shows a reply to a post published on your Page by a customer:

Hi, I want to buy a gift for my nephew. Do you have any suggestions?

Advertisement
free widgets for website
  curl -X POST -H "Content-Type: application/json" -d '{     "recipient": {         "post_id": "PAGE-POST-ID"     },          "message": {       "attachment":{         "type":"template",         "payload":{           "template_type":"button",           "text":"Of course, what is your budget for the gift?",           "buttons":[               {                   "type": "postback",                   "title": "LESS THAN $20",                   "payload": "GIFT_BUDGET_20_PAYLOAD"               },               {                   "type": "postback",                   "title": "$20 TO $50",                   "payload": "GIFT_BUDGET_20_TO_50_PAYLOAD"               },               {                   "type": "postback",                   "title": "MORE THAN $50",                   "payload": "GIFT_BUDGET_50_PAYLOAD"               }           ]         }       }     } }' "https://graph.facebook.com//PAGE-ID/messages?access_token="

Triggers a Private Reply flow like this.

For more information, please review the below documents:

First seen at developers.facebook.com

See also  Akron Zoo reveals adorable penguin chick's name on Facebook Live
Continue Reading

FACEBOOK

Enabling developers to create innovative AIs on Messenger and WhatsApp

Published

on

By

enabling-developers-to-create-innovative-ais-on-messenger-and-whatsapp

Every week over 1 billion people connect with businesses on our messaging apps. Many of these conversations are made possible by the thousands of developers who build innovative and engaging experiences on Messenger, Instagram and WhatsApp.

Since opening access to our Llama family of large language models, we’ve seen lots of momentum and innovation with more than 30 million downloads to date. As our messaging services continue to evolve, we believe the technology from Llama and other generative AI models have the potential to enhance business messaging through more natural, conversational experiences.

At Connect Meta announced that developers will be able to build third-party AIs – a term we use to refer to our generative AI-powered assistants – for our messaging services.

We’re making it easy for any developer to get started, so we’re simplifying the developer onboarding process and providing access to APIs for AIs that make it possible to build new conversational experiences within our messaging apps.

All developers will be able to access the new onboarding experience and features on Messenger in the coming weeks. For WhatsApp, we’ll be opening a Beta program in November – if you’re interested in participating please sign up to the waitlist here to learn more.

Advertisement
free widgets for website

We’ll keep everyone updated as we make these tools available to more developers later this year. We look forward to your feedback and seeing what you create.

First seen at developers.facebook.com

See also  Parish's Live-Streaming Mass Returns to Facebook
Continue Reading

FACEBOOK

Introducing Facebook Graph API v18.0 and Marketing API v18.0

Published

on

By

introducing-facebook-graph-api-v180-and-marketing-api-v18.0

Today, we are releasing Facebook Graph API v18.0 and Marketing API v18.0. As part of this release, we are highlighting changes below that we believe are relevant to parts of our developer community. These changes include announcements, product updates, and notifications on deprecations that we believe are relevant to your application(s)’ integration with our platform.

For a complete list of all changes and their details, please visit our changelog.

General Updates

Consolidation of Audience Location Status Options for Location Targeting

As previously announced in May 2023, we have consolidated Audience Location Status to our current default option of “People living in or recently in this location” when choosing the type of audience to reach within their Location Targeting selections. This update reflects a consolidation of other previously available options and removal of our “People traveling in this location” option.

We are making this change as part of our ongoing efforts to deliver more value to businesses, simplify our ads system, and streamline our targeting options in order to increase performance efficiency and remove options that have low usage.

This update will apply to new or duplicated campaigns. Existing campaigns created prior to launch will not be entered in this new experience unless they are in draft mode or duplicated.

Advertisement
free widgets for website

Add “add_security_recommendation” and “code_expiration_minutes” to WA Message Templates API

Earlier this year, we released WhatsApp’s authentication solution which enabled creating and sending authentication templates with native buttons and preset authentication messages. With the release of Graph API v18, we’re making improvements to the retrieval of authentication templates, making the end-to-end authentication template process easier for BSPs and businesses.

With Graph API v18, BSPs and businesses can have better visibility into preset authentication message template content after creation. Specifically, payloads will return preset content configuration options, in addition to the text used by WhatsApp. This improvement can enable BSPs and businesses to build “edit” UIs for authentication templates that can be constructed on top of the API.

See also  Rick Scott lobbies Twitter, Facebook CEOs to 'protect children', back social media study

Note that errors may occur when upgrading to Graph API v18 if BSPs or businesses are taking the entire response from the GET request and providing it back to the POST request to update templates. To resolve, the body/header/footer text fields should be dropped before passing back into the API.

Re-launching dev docs and changelogs for creating Call Ads

  • Facebook Reels Placement for Call Ads

    Meta is releasing the ability to deliver Call Ads through the Facebook Reels platform. Call ads allow users to call businesses in the moment of consideration when they view an ad, and help businesses drive more complex discussions with interested users. This is an opportunity for businesses to advertise with call ads based on peoples’ real-time behavior on Facebook. Under the Ad set Level within Ads Manager, businesses can choose to add “Facebook Reels” Under the Placements section.
  • Re-Launching Call Ads via API

    On September 12, 2023, we’re providing updated guidance on how to create Call Ads via the API. We are introducing documentation solely for Call Ads, so that 3P developers can more easily create Call Ads’ campaigns and know how to view insights about their ongoing call ad campaigns, including call-related metrics. In the future, we also plan to support Call Add-ons via our API platform. Developers should have access to the general permissions necessary to create general ads in order to create Call Ads via the API platform.

    Please refer to developer documentation for additional information.

Deprecations & Breaking Changes

Graph API changes for user granular permission feature

We are updating two graph API endpoints for WhatsAppBusinessAccount. These endpoints are as follows:

  • Retrieve message templates associated with WhatsAppBusiness Account
  • Retrieve phone numbers associated with WhatsAppBusiness Account

With v18, we are rolling out a new feature “user granular permission”. All existing users who are already added to WhatsAppBusinessAccount will be backfilled and will continue to have access (no impact).

The admin has the flexibility to change these permissions. If the admin changes the permission and removes access to view message templates or phone numbers for one of their users, that specific user will start getting an error message saying you do not have permission to view message templates or phone numbers on all versions v18 and older.

Advertisement
free widgets for website

Deprecate legacy metrics naming for IG Media and User Insights

Starting on September 12, Instagram will remove duplicative and legacy, insights metrics from the Instagram Graph API in order to share a single source of metrics to our developers.

This new upgrade reduces any confusion as well as increases the reliability and quality of our reporting.

After 90 days of this launch (i.e. December 11, 2023), we will remove all these duplicative and legacy insights metrics from the Instagram Graph API on all versions in order to be more consistent with the Instagram app.

We appreciate all the feedback that we’ve received from our developer community, and look forward to continuing to work together.

Please review the media insights and user insights developer documentation to learn more.

Advertisement
free widgets for website

Deprecate all Facebook Wi-Fi v1 and Facebook Wi-Fi v2 endpoints

Facebook Wi-Fi was designed to improve the experience of connecting to Wi-Fi hotspots at businesses. It allowed a merchant’s customers to get free Wi-Fi simply by checking in on Facebook. It also allowed merchants to control who could use their Wi-Fi and for how long, and integrated with ads to enable targeting to customers who had used the merchant’s Wi-Fi. This product was deprecated on June 12, 2023. As the partner notice period has ended, all endpoints used by Facebook Wi-Fi v1 and Facebook Wi-Fi v2 have been deprecated and removed.

API Version Deprecations:

As part of Facebook’s versioning schedule for Graph API and Marketing API, please note the upcoming deprecations:

Graph API

  • September 14, 2023: Graph API v11.0 will be deprecated and removed from the platform
  • February 8, 2024: Graph API v12.0 will be deprecated and removed from the platform
  • May 28, 2024: Graph API v13.0 will be deprecated and removed from the platform

Marketing API

  • September 20, 2023: Marketing API v14.0 will be deprecated and removed from the platform
  • September 20, 2023: Marketing API v15.0 will be deprecated and removed from the platform
  • February 06, 2024: Marketing API v16.0 will be deprecated and removed from the platform

To avoid disruption to your business, we recommend migrating all calls to the latest API version that launched today.

Facebook Platform SDK

As part of our 2-year deprecation schedule for Platform SDKs, please note the upcoming deprecations and sunsets:

  • October 2023: Facebook Platform SDK v11.0 or below will be sunset
  • February 2024: Facebook Platform SDK v12.0 or below will be sunset

First seen at developers.facebook.com

See also  HHVM: A Contributor’s Story with Jonathan Warner
Continue Reading

Trending