Friendica Communications Platform (please note that this is a clone of the repository at github, issues are handled there)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

132 lines
6.0 KiB

10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
10 years ago
  1. Installing Connectors (Facebook/Twitter/StatusNet)
  2. ==================================================
  3. * [Home](help)
  4. Friendica uses plugins to provide connectivity to some networks, such as Facebook and Twitter.
  5. There is also a plugin to post through to an existing account on a Status.Net service. You do not require this to communicate with Status.Net members from Friendica - only if you wish to post to an existing account.
  6. All three of these plugins require an account on the target network. In addition you (or typically the server administrator) will need to obtain an API key to provide authenticated access to your Friendica server.
  7. **Site Configuration**
  8. Plugins must be installed by the site administrator before they can be used. This is accomplished through the site administration panel.
  9. Each of the connectors also requires an "API key" from the service you wish to connect with. Some plugins allow you to enter this information in the site administration pages, while others may require you to edit your configuration file (.htconfig.php). The method for obtaining these keys varies greatly - but almost always requires an existing account on the target service. Once installed, these API keys can usually be shared by all site members.
  10. The details of configuring each service follows (much of this information comes directly from the plugin source files):
  11. **Twitter Plugin for Friendica**
  12. * Author: Tobias Diekershoff
  13. *
  14. * License:3-clause BSD license
  15. Configuration:
  16. To use this plugin you need a OAuth Consumer key pair (key & secret)
  17. you can get it from Twitter at
  18. Register your Friendica site as "Client" application with "Read & Write" access.
  19. We do not need "Twitter as login". When you've registered the app you get the
  20. OAuth Consumer key and secret pair for your application/site.
  21. Add this key pair to your global .htconfig.php
  22. ```
  23. $a->config['twitter']['consumerkey'] = 'your consumer_key here';
  24. $a->config['twitter']['consumersecret'] = 'your consumer_secret here';
  25. ```
  26. After this, your user can configure their Twitter account settings
  27. from "Settings -> Connector Settings".
  28. Documentation:
  29. **StatusNet Plugin for Friendica**
  30. * Author: Tobias Diekershoff
  31. *
  32. * License:3-clause BSD license
  33. Configuration
  34. When the addon is activated the user has to aquire the following in order to connect to the StatusNet account of choice.
  35. * The base URL for the StatusNet API, for this is
  36. * OAuth Consumer key & secret
  37. To get the OAuth Consumer key pair the user has to
  38. (a) ask her Friendica admin if a pair already exists or
  39. (b) has to register the Friendica server as a client application on the StatusNet server.
  40. This can be done from the account settings under "Settings -> Connections -> Register an OAuth client application -> Register a new application" on the StatusNet server.
  41. During the registration of the OAuth client remember the following:
  42. * Application names must be unique on the StatusNet site, so we recommend a Name of 'friendica-nnnn', replace 'nnnn' with a random number or your website name.
  43. * there is no callback url
  44. * register a desktop client
  45. * with read & write access
  46. * the Source URL should be the URL of your Friendica server
  47. After the required credentials for the application are stored in the configuration you have to actually connect your Friendica account with StatusNet. This is done from the Settings -> Connector Settings page. Follow the Sign in with StatusNet button, allow access and then copy the security code into the box provided. Friendica will then try to acquire the final OAuth credentials from the API.
  48. If successful the addon settings will allow you to select to post your public messages to your StatusNet account (have a look behind the little lock symbol beneath the status "editor" on your Home or Network pages).
  49. Documentation:
  50. **Installing the Friendica/Facebook connector**
  51. * register an API key for your site from
  52. This requires a Facebook account, and may require additional authentication in the form of credit card or mobile phone verification.
  53. a. We'd be very happy if you include "Friendica" in the application name
  54. to increase name recognition. The Friendica icons are also present
  55. in the images directory and may be uploaded as a Facebook app icon.
  56. Use images/friendica-16.jpg for the Icon and images/friendica-128.jpg for the Logo.
  57. b. The url should be your site URL with a trailing slash.
  58. You **may** be required to provide a privacy and/or terms of service URL.
  59. c. Navigate to Set Web->Site URL & Domain -> Website Settings. Set Site URL
  60. to Set Site Domain to your
  61. d. Install the Facebook plugin on your Friendica site at 'admin/plugins'. You should then see a link for Facebook under 'Plugin Features' on the sidebar of the admin panel. Select that.
  62. e. Enter the App-ID and App Secret that Facebook gave you. Change any other settings as desired.
  63. On Friendica, each member who wishes to use the Facebook connector should visit the Facebook Settings section of their "Settings->Connector Settings" page, and click 'Install Facebook Connector'.
  64. Choose the appropriate settings for your usage and privacy requirements.
  65. This will ask you to login to Facebook and grant permission to the
  66. plugin to do its stuff. Allow it to do so.
  67. You're done. To turn it off visit the Connector Settings page again and
  68. 'Remove Facebook posting'.
  69. Videos and embeds will not be posted if there is no other content. Links
  70. and images will be converted to a format suitable for the Facebook API and
  71. long posts truncated - with a link to view the full post.
  72. Facebook contacts will also not be able to view "private" photos, as they are not able to authenticate to your site to establish identity. We will address this in a future release.