Add a notice for Meta requirements on screencasts #159
Conversation
|
@Arusekk is attempting to deploy a commit to the Listinai Team on Vercel. A member of the Team first needs to authorize it. |
WalkthroughThe documentation for Facebook and Instagram provider setup was expanded to clarify the business verification process for public applications. Both now require a screencast demonstrating specific user interactions and warn about potential multiple review iterations. The Instagram documentation also adds a section detailing the advanced permissions and scopes needed for broader account access. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (4)
pages/providers/facebook.mdx (1)
19-25: Polish the wording & improve scannability of the screencast requirementsThe current sentence is long, colloquial (“actually”), and a bit hard to parse. Consider re-phrasing and switching to a bullet list so admins can quickly tick the items off when recording the video.
-Please be advised that for public applications, you will need to verify your business, -and [submit a screencast](https://developers.facebook.com/docs/resp-plat-initiatives/individual-processes/app-review/submission-guide) -showing log-in to your app, connecting an actual Facebook account, -clicking the during-connect link to privacy policy, posting something with a comment, -showing that it actually appears in the feed, and showing the Postiz analytics. -It can be one long video for all three (Facebook, Instagram (Facebook Business) and Instagram (standalone)) flows. -Expect many LLM-generated roundtrips with the review team. +If your app is public you must: + +* complete business verification; **and** +* [submit a screencast](https://developers.facebook.com/docs/resp-plat-initiatives/individual-processes/app-review/submission-guide) that demonstrates + 1. logging into the app; + 2. connecting a real Facebook account; + 3. clicking the privacy-policy link during the connection flow; + 4. publishing a post that contains a comment; + 5. confirming the post appears in the feed; + 6. viewing the post inside Postiz analytics. + +One continuous video can cover Facebook, Instagram (Business) and Instagram (Standalone) flows. +Be prepared for several review iterations with the Meta team.This keeps the required actions explicit and removes informal phrasing.
pages/providers/instagram.mdx (3)
26-33: Tighten language & break the sentence into a checklistSame readability issue as in the Facebook doc. Recommend restructuring:
-Please be advised that for public applications, you will need to verify your business, -and [submit a screencast](https://developers.facebook.com/docs/resp-plat-initiatives/individual-processes/app-review/submission-guide) -showing log-in to your app, connecting an actual Instagram account, -clicking the during-connect link to privacy policy, posting something with a comment, -showing that it actually appears in the feed, and showing the Postiz analytics. -It can be one long video for all three (Facebook, Instagram (Facebook Business) and Instagram (standalone)) flows. -Expect many LLM-generated roundtrips with the review team, -who might not be very helpful understanding the distinction between the two Instagram flows. +For public apps you must: + +* finish business verification; **and** +* [submit a screencast](https://developers.facebook.com/docs/resp-plat-initiatives/individual-processes/app-review/submission-guide) that shows + 1. logging in; + 2. connecting a real Instagram account; + 3. clicking the privacy-policy link during connection; + 4. publishing a post with a comment; + 5. the post appearing in the feed; + 6. the post inside Postiz analytics. + +One continuous video may cover Facebook, Instagram (Business) and Instagram (Standalone) flows. +Expect several review iterations; reviewers sometimes conflate the two Instagram flows.Removes informal tone and makes the list action-oriented.
166-174: Render the scope list as a fenced code block for consistent formattingWithout fencing, each back-ticked scope renders as an inline code fragment on its own line, which can look uneven. A single code block (like earlier sections) keeps the visual style consistent.
-`instagram_business_basic` -`instagram_business_content_publish` -`instagram_business_manage_comments` -`instagram_business_manage_insights` +```text +instagram_business_basic +instagram_business_content_publish +instagram_business_manage_comments +instagram_business_manage_insights +```
16-18: Fix “Developpers” typoMinor typo in the link anchor:
-... will require a [Meta for Developpers account]... +... will require a [Meta for Developers account]...
This is a minor warning for the curious admin trying to add a more seamless login experience for users.
Do you think this description is worthwhile to include?
Summary by CodeRabbit