Source evidence

not work because OAuth 2.0 Authentication is required.

XPoster – Share to Bluesky and Mastodon · review · 2023-11-27T03:19:00+00:00

XPoster – Share to Bluesky and Mastodon plugin evidence original source source API

complaintsentiment

mediumseverity

0.86relevance

2replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

2 / 30 rows with source links

6.7% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

28 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

review · 1 stars

ekatoekato unresolved

It does not work because OAuth 2.0 Authentication is required when I make up a new twitter project or edit default project . Any way I tried to post then this error come up. “403: Client Forbidden: When authenticating requests to the Twitter API v2 endpoints, you must use keys and tokens from a Twitter developer App that is attached to a Project. You can create a project via the developer portal.” I do not know when this x developer “User authentication settings” changed. Thank you. Did you follow the instructions at XPosterPro.com ? If there’s something missing from those instructions, I definitely would like to know about it. If you did set up your app to OAuth 2.0, I have found that is pretty much impossible to reverse that, and you have to delete the app and start over. As long as you don’t choose a Type of App in the User Authentication Settings, you should be fine. Sheesh. They have changed the process again, so those directions are misleading. Would be nice if they’d leave this process the same for more than a couple weeks. Regardless, in the testing I just ran, you’re fine in your setup as long as you pick ‘Read & Write’ in the OAuth 1.0a permission settings, and it doesn’t matter what you do in the Type of App settings.

Commercial Context

Opportunity

onsite conversion and engagement operations

Sharing conversion widget assurance for turning onsite engagement widgets into measurable leads, trust, and conversions

Buyer: marketing teams, agencies, publishers, and ecommerce operators

Wedge: audit sharing display rules, lead capture, trust signals, and campaign attribution

Investigate Pain card complete market

Analysis

heuristic-v1

Summary: not work because OAuth 2.0 Authentication is required.: users show bugs, missing feature, setup pain that may indicate a product gap.

Evidence quote: It does not work because OAuth 2.0 Authentication is required when I make up a new twitter project or edit default project .

Affected feature: api

bugs missing feature setup api

Plugin

API

XPoster – Share to Bluesky and Mastodon

10.0K active installs · 4.1M downloads · rating 76.0

bluesky mastodon post sharing social

Comments

2 shown

Joe Dolson 2023-11-27T17:28:00+00:00

Did you follow the instructions at XPosterPro.com ? If there’s something missing from those instructions, I definitely would like to know about it. If you did set up your app to OAuth 2.0, I have found that is pretty much impossible to reverse that, and you have to delete the app and start over. As long as you don’t choose a Type of App in the User Authentication Settings, you should be fine.

Joe Dolson 2023-11-27T17:38:00+00:00

Sheesh. They have changed the process again, so those directions are misleading. Would be nice if they’d leave this process the same for more than a couple weeks. Regardless, in the testing I just ran, you’re fine in your setup as long as you pick ‘Read & Write’ in the OAuth 1.0a permission settings, and it doesn’t matter what you do in the Type of App settings.