You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, it's up to users to register apps for providers like Google, Facebook, Instagram and Twitter. However, a great deal of support and issues is spent on troubleshooting these platforms, and their connections to them. Providing support is tricky as we're often dealing with client accounts, which we shouldn't be accessing for privacy reasons.
It also means that it requires a developer account/app with providers, setting that up correctly, and handling Client ID/Secrets. This proves challenging when providers (Facebook) constantly change their platform.
An option to get around this, alleviate support and provide a better UX, is to connect via a Verbb Authenticator service. So instead of handling OAuth credentials yourselves, you could pick a provider, be redirected to Verbb's service to start the OAuth handling. You'll then use Verbb's app for the respective platforms without ever needing to manage an app or credentials yourselves.
Suffice it to say, Verbb isn't going to be storing anything about the account you connect with, as that'll all be directly with the provider. It'll be more that you'll be using the Verbb Facebook/Instagram/etc app to read/write content. This would be an approved app, so you'll get the benefit of advanced permissions. You'll be able to use it for unlimited sites, and at no additional charge.
In addition, the Twitter API is locked down to payment only. We may consider providing this for free as part of our service.
The text was updated successfully, but these errors were encountered:
Currently, it's up to users to register apps for providers like Google, Facebook, Instagram and Twitter. However, a great deal of support and issues is spent on troubleshooting these platforms, and their connections to them. Providing support is tricky as we're often dealing with client accounts, which we shouldn't be accessing for privacy reasons.
It also means that it requires a developer account/app with providers, setting that up correctly, and handling Client ID/Secrets. This proves challenging when providers (Facebook) constantly change their platform.
An option to get around this, alleviate support and provide a better UX, is to connect via a Verbb Authenticator service. So instead of handling OAuth credentials yourselves, you could pick a provider, be redirected to Verbb's service to start the OAuth handling. You'll then use Verbb's app for the respective platforms without ever needing to manage an app or credentials yourselves.
Suffice it to say, Verbb isn't going to be storing anything about the account you connect with, as that'll all be directly with the provider. It'll be more that you'll be using the Verbb Facebook/Instagram/etc app to read/write content. This would be an approved app, so you'll get the benefit of advanced permissions. You'll be able to use it for unlimited sites, and at no additional charge.
In addition, the Twitter API is locked down to payment only. We may consider providing this for free as part of our service.
The text was updated successfully, but these errors were encountered: