- Documentation
- Guide · Version 1.0
- Own applications
Own applications
On this page
If a network blocks the Quiet Social application, your connections can go through an application you created yourself on that network. It is a fallback, which the Quiet Social team opens network by network.
When to use it
All connections normally go through the Quiet Social developer application. If a network suspends it, throttles it or rejects its review, the team opens Own applications for that network, and you are told.
Mastodon and Bluesky are not concerned: Quiet Social registers itself with each Mastodon server, and presents itself to Bluesky by its own address, with no application to declare; no network can block all your Mastodon connections at once, nor Bluesky all your Bluesky connections, short of refusing our client.
Until then, the Own applications menu does not appear: there is nothing to do. Own applications are not offered on the free plan: a free workspace stays on the Quiet Social application, and a workspace that falls back to it no longer publishes through its own application until it takes a paid plan again.
Create the application on the network
In the network's developer console (Meta for Developers, LinkedIn Developers, Pinterest Developers), create an application and enter:
- the redirect address that Quiet Social shows when you declare the application, exactly as shown;
- the permissions shown in the same place, and no more.
To publish on accounts that do not belong to the administrators of your application, the network usually requires an application review: it is your application, and it is up to you to obtain it. For Threads, the Meta application carries two pairs of credentials: declare here the Threads identifier and secret (Threads use case), not the Facebook ones, which would make every connection fail on the way back.
Declare the application
Own applications menu, Declare an application: pick the network, then paste the application's identifier and secret. This is reserved to administrators and the owner. The secret is encrypted and never shown again.
Then connect the account from the Connected accounts menu: the new connection goes through your application. The list of connected accounts shows, for each one, the application it goes through.
What does not change
A connection stays served by the application that established it. A connection opened through the Quiet Social application therefore keeps going through it. To move it to yours, connect the account again:
- if a new connection appears (as with Meta and Threads, where each application sees the account under a different identifier), attach your Pages and accounts to it from its page, then revoke the old connection;
- if the same connection is updated (Pinterest), its destinations follow; then remove the Quiet Social application's access in your account settings on the network.
When the team closes own applications again, your existing connections carry on the same way: only new ones go back through Quiet Social.
Replace the secret or delete the application
Replace the secret, after renewing it in the network's console: connections carry on without reconnecting. The identifier does not change: another application is declared after deleting the first one.
Delete is only possible once no connection depends on it any more: revoke them first. Without the secret, their access could no longer be used, nor withdrawn at the network.