WebFinger
Contributors: pfefferle, willnorris
Donate link: https://notiz.blog/donate/
Tags: discovery, webfinger, JRD, ostatus, activitypub
Requires at least: 4.2
Tested up to: 6.6
Stable tag: 3.2.7
License: MIT
License URI: https://opensource.org/licenses/MIT, (*1)
WebFinger for WordPress, (*2)
Description
Enables WebFinger (RFC 7033) support for WordPress., (*3)
About WebFinger:, (*4)
WebFinger is used to discover information about people or other entities on the Internet that are identified by a URI using standard Hypertext Transfer Protocol (HTTP) methods over a secure transport. A WebFinger resource returns a JavaScript Object Notation (JSON) object describing the entity that is queried. The JSON object is referred to as the JSON Resource Descriptor (JRD)., (*5)
(quote from the RFC), (*6)
Frequently Asked Questions
How to extend the JRD file
You can add your own links or properties like that:, (*7)
function oexchange_target_link( $array ) {
$array["links"][] = array( 'rel' => 'http://oexchange.org/spec/0.8/rel/resident-target',
'href' => 'http://example.com',
'type' => 'application/xrd+xml' );
return $array;
}
add_filter( 'webfinger_data', 'oexchange_target_link' );
You can add your own links or properties like that:, (*8)
function render_xrd($webfinger) {
// set custom header();
// JRD to XRD code
exit;
}
add_action( 'webfinger_render', 'render_xrd', 5 );
You can find a detailed example here https://github.com/pfefferle/wordpress-webfinger-legacy, (*9)
The spec
WebFinger is specified as RFC 7033, (*10)
Please visit http://webfinger.net, (*11)
Upgrade Notice
3.0.0
This versions drops classic WebFinger support to keep the plugin short and simple. All legacy stuff is bundled in this new plugin https://github.com/pfefferle/wordpress-webfinger-legacy, (*12)
Changelog
Project maintained on github at pfefferle/wordpress-webfinger., (*13)
3.2.7
- Added: better output escaping
- Fixed: stricter queries
3.2.6
3.2.5
3.2.4
3.2.3
- fixed
acct scheme for discovery
3.2.2
- fixed typo (thanks @ivucica)
- use
acct as default scheme
3.2.1
- make
acct protocol optional
3.2.0
3.1.6
- added
user_nicename as resource
- fixed WordPress coding standard issues
3.1.5
3.1.4
3.1.3
- add support for the 'aim', 'ymsgr' and 'acct' protocol
3.1.2
- fixed the legacy code
- added feeds
3.1.1
- fixed 'get_user_by_various' function
3.1.0
- Added WebFinger legacy plugin, because the legacy version is still very popular and used by for example OStatus (Mastodon, Status.NET and GNU Social)
- Added Webfinger for posts support
3.0.3
- composer support
- compatibility updates
3.0.2
-
get_avatar_url instead of custom code
- some small code improvements
- nicer PHP-docs
3.0.1
- updated version informations
- support the WordPress Coding Standard
3.0.0
- added correct error-responses
- remove legacy support for XRD and host-meta (props to Will Norris)
2.0.1
2.0.0
- complete refactoring
- removed simple-web-discovery
- more filters and actions
- works without /.well-known/ plugin
1.4.0
- small fixes
- added "webfinger" as well-known uri
1.3.1
- added "rel"-filter (work in progress)
- added more aliases
1.3
- added host-meta resource feature (see latest spec)
1.2
- added 404 http error if user doesn't exist
- added jrd discovery for host-meta
1.1
- fixed an odd problem with lower WordPress versions
- added support for the http://wordpress.org/extend/plugins/extended-profile/ (thanks to Singpolyma)
1.0.1
1.0
- basic simple-seb-discovery
- json support
- some small improvements
0.9.1
- some changes to support http://unhosted.org
0.9
- OStatus improvements
- Better uri handling
- Identifier overview (more to come)
- Added filters
- Added functions to get a users webfingers
0.7
- Added do_action param (for future OStatus plugin)
- Author-Url as Webfinger-Identifier
0.5
Installation
Follow the normal instructions for installing WordPress plugins., (*14)
Automatic Plugin Installation
To add a WordPress Plugin using the built-in plugin installer:, (*15)
- Go to Plugins > Add New.
- Type "
webfinger" 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.
Manual Plugin Installation
There are a few cases when manually installing a WordPress Plugin is appropriate., (*16)
- 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., (*17)
Backup your site completely before proceeding., (*18)
To install a WordPress Plugin manually:, (*19)
- Download your WordPress Plugin to your desktop.
- 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/plugins folder in your WordPress directory online.
- Go to Plugins screen and find the newly uploaded Plugin in the list.
- Click Activate to activate it.
Wallogit.com
