Contributors: pfefferle, mediaformat
Donate link: https://notiz.blog/donate/
Tags: OStatus, fediverse, activitypub, activitystream
Requires at least: 4.7
Tested up to: 6.0
Stable tag: 0.13.4
Requires PHP: 5.6
License: MIT
License URI: http://opensource.org/licenses/MIT
The ActivityPub protocol is a decentralized social networking protocol based upon the ActivityStreams 2.0 data format.
This is BETA software, see the FAQ to see the current feature set or rather what is still planned.
The plugin implements the ActivityPub protocol for your blog. Your readers will be able to follow your blogposts on Mastodon and other federated platforms that support ActivityPub.
The plugin works with the following federated platforms:
Implemented:
- profile pages (JSON representation)
- custom links
- functional inbox/outbox
- follow (accept follows)
- share posts
- receive comments/reactions
To implement:
- signature verification
- better WordPress integration
- better configuration possibilities
- threaded comments support
ActivityPub for WordPress extends WordPress with some Fediverse features, but it does not compete with platforms like Friendica or Mastodon. If you want to run a decentralized social network, please use Mastodon or GNU social.
Compatibility
ActivityPub for WordPress is compatible with OStatus and IndieWeb plugin suites. Pterotype is incompatible with the standalone WebFinger plugin, so it can't be run together with OStatus.
Custom tables
Pterotype creates/uses a bunch of custom tables, ActivityPub for WordPress only uses the native tables and adds as little meta data as possible.
In order for webfinger to work, it must be mapped to the root directory of the URL on which your blog resides.
Apache
Add the following to the .htaccess file in the root directory:
RedirectMatch "^\/\.well-known(.*)$" "\/blog\/\.well-known$1"
Where 'blog' is the path to the subdirectory at which your blog resides.
Nginx
Add the following to the site.conf in sites-available:
location ~* /.well-known {
allow all;
try_files $uri $uri/ /blog/?$args;
}
Where 'blog' is the path to the subdirectory at which your blog resides.
Project maintained on GitHub at pfefferle/wordpress-activitypub.
- fix webfinger for email identifiers
- fix: Create and Note should not have the same ActivityPub ID
- fix Follow issue AGAIN
- fix Inbox issue
- add Autor URL and WebFinger health checks
- fix NodeInfo endpoint
- use "pre_option_require_name_email" filter instead of "check_comment_flood". props @akirk
- save only comments/replies
- check for an explicit "undo -> follow" action. see https://wordpress.org/support/topic/qs-after-latest/
- fix inconsistent
%tags%placeholder
- fix follow/unfollow actions
- add support for customizable post-content
- first try of a delete activity
- do not require email for AP entries. props @akirk
- fix timezones bug. props @mediaformat
- fix digest header bug. props @mediaformat
- fix inbox activities, like follow
- fix debug
- add image alt text to the ActivityStreams attachment property in a format that Mastodon can read. props @BenLubar
- use the "summary" property for a title as Mastodon does. props @BenLubar
- support authorized fetch to avoid having comments from "Anonymous". props @BenLubar
- add new post type: "title and link only". props @bgcarlisle
- disable shared inbox
- disable delete activity
- some code refactorings
- fix #73
- fixed accept header bug
- add all required accept header
- better/simpler accept-header handling
- add debugging mechanism
- Add setting to enable AP for different (public) Post-Types
- explicit use of global functions
- fixed PHP warnings
- Moved followers list to user-menu
- added admin_email to metadata, to be able to "Manage your instance" on https://fediverse.network/manage/
- refactorings
- fixed PHP warnings
- better hashtag regex
- fixed JSON representation of posts https://merveilles.town/@xuv/101907542498716956
- fixed inbox problems with pleroma
- finally fixed pleroma compatibility
- added "following" endpoint
- simplified "followers" endpoint
- fixed default value problem
- add tags as hashtags to the end of each activity
- fixed pleroma following issue
- followers-list improvements
- fixed name-collision that caused an infinite loop
- complete refactoring
- fixed bug #30: Password-protected posts are federated
- only send Activites when ActivityPub is enabled for this post-type
- show avatars
- finally fixed backlink in excerpt/summary posts
- fixed backlink in excerpt/summary posts (thanks @depone)
- finally fixed contact list
- added settings to enable/disable hashtag support
- fixed follower list
- send activities only for new posts, otherwise send updates
- added "followers" endpoint
- change activity content from blog 'excerpt' to blog 'content'
- better json encoding
- basic hashtag support
- temporarily deactivated likes and boosts
- added support for actor objects
- fixed encoding issue
- customizable backlink (permalink or shorturl)
- show profile-identifiers also on profile settings
- added option to switch between content and excerpt
- removed html and duplicate new-lines
- fixed "excerpt" in AS JSON
- added settings for the activity-summary and for the activity-object-type
- added basic WebFinger support
- added basic NodeInfo support
- fully functional "follow" activity
- send new posts to your followers
- receive comments from your followers
- refactoring
- functional inbox
- nicer profile views
- initial
Follow the normal instructions for installing WordPress plugins.
To add a WordPress Plugin using the built-in plugin installer:
- Go to Plugins > Add New.
- Type "
activitypub" into the Search Plugins box. - Find the WordPress Plugin you wish to install.
- Click Details for more information about the Plugin and instructions you may wish to print or save to help setup the Plugin.
- Click Install Now to install the WordPress Plugin.
- The resulting installation screen will list the installation as successful or note any problems during the install.
- If successful, click Activate Plugin to activate it, or Return to Plugin Installer for further actions.
There are a few cases when manually installing a WordPress Plugin is appropriate.
- If you wish to control the placement and the process of installing a WordPress Plugin.
- If your server does not permit automatic installation of a WordPress Plugin.
- If you want to try the latest development version.
Installation of a WordPress Plugin manually requires FTP familiarity and the awareness that you may put your site at risk if you install a WordPress Plugin incompatible with the current version or from an unreliable source.
Backup your site completely before proceeding.
To install a WordPress Plugin manually:
- Download your WordPress Plugin to your desktop.
- Download from the WordPress directory
- Download from GitHub
- If downloaded as a zip archive, extract the Plugin folder to your desktop.
- With your FTP program, upload the Plugin folder to the
wp-content/pluginsfolder in your WordPress directory online. - Go to Plugins screen and find the newly uploaded Plugin in the list.
- Click Activate to activate it.