- Contributors: akirk
- Tags: friends, rss, decentralized, social-network, own-your-data
- Requires PHP: 7.2
- Tested up to: 6.7
- License: GPL-2.0-or-later
- Stable tag: 3.2.3
Your own WordPress at the center of your online activity. Follow friends and other websites and establish friendship relationships between blogs.
The Friends plugin allows you to follow content from other WordPress sites, and interact with them on your own site. You can follow friends and others via RSS. If you also have the ActivityPub plugin installed, you can follow people on Mastodon and other ActivityPub-compatible social networks.
Since version 2.6.0, no users will be created for subscriptions.
Combine this plugin with the ActivityPub plugin to make your own WordPress your own Mastodon instance. Use the Enable Mastodon Apps to use mobile and desktop Mastodon apps with your own site.
The Friends Plugin also has a "friend request" function which allows blogs to become friends with each other. This then allows private publishing on your blog while each of their friends has their own blog but will be able to see your privately published posts.
There are many small aspects that make it powerful self-hosted social reader:
You can...
- Have multiple feeds per person, so you can subscribe to their blog(s) and social media account(s).
- Categorize incoming content with Post Formats and view all posts of a certain format across your friends.
- Define rules to filter incoming content (sometimes you’re not interested in everything your friends do).
- Turn your favorite blog into your personal newsletter by receiving full-post notification e-mails
- Use feed rules to filter out content you are not interested in.
- Receive ePubs of your friends' posts to your eReader (via another plugin).
- Collect posts (from your feeds or around the web) in a collection for later reference (via another plugin).
The Friends Plugin was built to make use of what WordPress provides:
- You use the WordPress infrastructure (Gutenberg or Classic Editor, what you prefer) to create your posts.
- If a post is private, only logged-in friends can see it. They can only log in through their own Friends plugin on their blog.
- Therefore, your friend is just a user on your WordPress blog, their posts are theirs, you can delete them to unfriend them.
- No extra tables: The Friends plugin just uses a post type, options and some taxonomies to store its data. When you delete the plugin, your WordPress will be slim like before.
In future, I could see mobile apps instead of talking to a third party, to talk to your own blog. It will have your friends' posts already fetched. Maybe the apps will be specialized, like Twitter or Instagram, where you'd only interact with and create posts in the specific post format.
The logo was created by Ramon Dodd, @ramonopoly. Thank you!
Documentation for the plugin can be found on the GitHub project Wiki.
Development of this plugin is done on GitHub. Pull requests welcome. Please see issues reported there before going to the plugin forum.
- Upload the
friendsdirectory to the/wp-content/plugins/directory - Activate the plugin through the 'Plugins' menu in WordPress
No, all the functionality is achieved with standard WordPress means. Subscriptions or Friends are minimal-permission users on your install. External posts are cached in a custom post types and attributed to those users.
I believe this is a very elegant way to attribute content and it allows to delete the users content when you delete them. The users have minimal privileges, so they cannot be used to post actual content to your site.
The users can only be used for login through your specific friend's WordPress install (they are created with a strong password throw-away password), if they have been upgraded to a "friend" or "aquaintance" user.
For one, this allows to stick with established WordPress configurations and terminologies. For example, you can use the WordPress mobile apps to post privately to your site.
Secondly, a lot of WordPresses are like cell phones. Some are used by more than one person but mostly there is a 1:1 relationship between a WordPress blog and a person.
If someone has multiple WordPresses this actually allows to segment your friendships. Close friends might want to follow all your blogs but you'd only add your photographer friends to your photoblog.
You'll still see the public posts from the other WordPress, you've subscribed to its public RSS feed.
Well, that's actually exactly the point. Facebook owns your data, with WordPress you can decide where you want to host it and have all the benefits of running open source software.
There is a cache of your friends post in form of a Custom Post Type friend_post that is updated when you change a post. When you delete a post your friends' WordPresses are notified and they delete the cached post.
- Compact view is like Google Reader
- You can use it like a Feed Reader
- But it is centered around users; you can have multiple feeds per person, even on social networks (parsing capabilities provided by plugins)
- Extensible with plugins itself
- Use the customizer to adapt it to your liking
- Categorize incoming content with Post Formats and view all posts of a certain format across your friends
- Use rules to filter incoming content (sometimes you’re not interested in everything your friends do)
- Friends users are plain WordPress users with low privileges
- A Friend Request is accepted in the users screen. Delete the user to reject it or accept the request to make them a friend
- ActivityPub: Support update of posts and people (#421)
- Add support for ActivityPub Move activity (#420)
- Make tagged Friend Posts accessible (#419)
- Uninstall: Delete more taxonomy entries (#415)
- Standardize REST Error messages (#413)
- Use the ActivityPub blog user as an actor if set to blog profile only (#411)
- Add a Duplicate Remover (#409)
- Move permissions checks into a dedicated permission_callback (#408)
- Add more checks around friendships (#407)
Hoping that this hardening will bring back the plugin to the WordPress.org directory after this issue was reported. While I am unsure it qualified to get the plugin taken down, I've done some hardening and bugfixing in the above pull requests. Unfortunately it was not reported in a way that it could be patched in time. If you have a security issue to report, please follow the instructions on https://github.com/akirk/friends/blob/main/SECURITY.md and/or report through https://github.com/akirk/friends/security.
- OPML Import: Support OPMLs without nesting (#403)
- Fix bug with loading the main theme (#398)
- Fix missing JavaScript on the frontend (#396)
- Add a theme selector (#393)
- Followers: Add Support for ActivityPub plugins blog profile (#394)
- Generate the suggested user login from the display name (#395)
- Site Health: Check if the cron job is enabled (#391)
- Fix starring of a friend (#392)
- Layout improvements props @liviagouvea in (#384)
- Fix next page articles attached in the wrong place (#388)
- Allow an extra redirect when discovering feeds (#389)
- Fix Warning: Undefined variable $account (#385)
- Fixes for Friend Messages (#387)
- Add Podcast Support (#386)
- Fix support for threads.net (#378)
- Add a warning if a user has not enabled ActivityPub on their threads.net account (#377)
- Upgrade and improve the MF2 library (#374)
- Add mark tag CSS to emails to ensure highlighting (#365)
- Only show the dashboard widgets if the user has enough permissions (#368)
- Prevent retrieving the same feed in parallel (#366)
- Add Friend: Use more info from the given URL (#369)
- Log ActivityPub actions and add the publish date to Announcements (#364)
- Improve OPML Support (#370)
- Update blueprints for previewing in WordPress Playground (#371)
- Show Mutual Followers and allow removing of followers (#359)
- Add an e-mail notification for new and lost followers (#358)
- Add the ability to disable notifications per post format and feed parser (#357)
- Fix 404 on the New private post widget props @liviacarolgouvea (#361)
- Improve ghost.org ActivityPub compatibility (#356)