Proof Health
Open evidenceCommercial opportunities need traceable source links before they are treated as build-worthy.
100.0% of this page's analysis has direct source links.
0 rows here require auditable proof before promotion.
0 rows have source counts but still need direct links.
Related Opportunities
0 marketsNo opportunity report currently maps to this plugin's tags.
Source Evidence
Open evidence explorer‘Webfinger end point not accessible’ but no explainer: users show bugs, compatibility, missing feature pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Cant Make It Work: users show security, bugs, missing feature pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
htaccess rules for blog hosted in subfolder: users show bugs, compatibility, missing feature pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Webfinger not working?: users show bugs pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
WebFinger Endpoint Not Accessible: users show bugs pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Site Health Json error: users show bugs, compatibility, missing feature pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
should support email usernames: users show bugs, compatibility, missing feature pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Didn’t work.: users show missing feature, support, setup pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
[Plugin: Webfinger] WPMU: users show missing feature, setup pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
adding an alias: users show missing feature, support pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Competitor Context
3 shownThis row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Repeated Themes
0 shownNo repeated plugin-level themes have been generated yet.
Collected Signals
18 shown from 18 collectedThe user thinks WebFinger does not work because they are testing the endpoint without the required resource parameter and needs setup guidance.
Evidence: i get this message: missing "resource" parameterThis row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
A WebFinger request for an invalid user caused a critical error, and the maintainer confirmed and fixed the error-handling bug.
Evidence: There has been a critical error on this websiteThis row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Cant Make It Work: users show security, bugs, missing feature pain that may indicate a product gap.
Evidence: Cant Make It Work WebFinger endpoint is not accessible I have spent hours trying to get this to work, I have spent hours and a few days reading every posted solution, I have debugged and got no errors, I have verified every permission every security setting, nothing makes this work, curl -X GET “ https://2ndshot.photos/.well-known/webfi nger?resource=acct:paThis row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
‘Webfinger end point not accessible’ but no explainer: users show bugs, compatibility, missing feature pain that may indicate a product gap.
Evidence: Activitypub plugin 2.2.0 installed.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
WebFinger Endpoint Not Accessible: users show bugs pain that may indicate a product gap.
Evidence: WebFinger Endpoint Not Accessible Since the last update to the ActivityPub plugin I get this critical issue in my Site Health: “WebFinger endpoint is not accessible” Assistance would be appreciated.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Does as expected.: users show setup pain that may indicate a product gap.
Evidence: I installed Webfinger and typed in the domain for my website into Mastodon instance photog.social.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
htaccess rules for blog hosted in subfolder: users show bugs, compatibility, missing feature pain that may indicate a product gap.
Evidence: So I change it to RewriteRule "^\/.well-known/(webfinger|nodeinfo|x-nodeinfo2|activitypub)(.*)$" /blog/index.php?well-known [QSA] But I get an error: Fatal error: Uncaught Error: Call to undefined method WP_Error::get_url() in /srv/home/blog/domains/blog.com/htdocs/www/blog/wp-content/plugins/activitypub/integration/class-webfinger.php:36 Stack trace: #0 /srThis row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Webfinger to share Mastodon when I’m an ActivityPub/Friends plugin user: users show support pain that may indicate a product gap.
Evidence: Trying to wrap my head around how .well-known works.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Webfinger not working?: users show bugs pain that may indicate a product gap.
Evidence: Hi, Still testing the various indieweb resources… The WebFinger plugin seems broken on both WP blogs: https://webfinger.net/lookup/?resource=cybeardjm%40amf.didiermary.fr https://webfinger.net/lookup/?resource=cybeardjm%40www.didiermary.fr Request Log 15:42:12 Looking up WebFinger data for acct:cybeardjm@www.didiermary.fr 15:42:12 GET https://www.didiermary.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
adding an alias: users show missing feature, support pain that may indicate a product gap.
Evidence: adding an alias The WordPress plugin ActivityPub has got a great version 1.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Help getting WebFinger plugin to work: users show bugs, missing feature, support pain that may indicate a product gap.
Evidence: Help getting WebFinger plugin to work I have just set up a wordpress website and I need a webfinger to work on it.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Users privacy violation: neutral conversation with limited structured signal.
Evidence: When users add a private email address, this will be revealed by webfinger.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
No config easy way to add webfinger for your existing users: users show setup pain that may indicate a product gap.
Evidence: No config easy way to add webfinger for your existing users Adding this plugin adds handling for the WebFinger protocol for your existing users.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Didn’t work.: users show missing feature, support, setup pain that may indicate a product gap.
Evidence: There’s no admin panel and the documentation isn’t clear about how to configure the plugin.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Site Health Json error: users show bugs, compatibility, missing feature pain that may indicate a product gap.
Evidence: Site Health Json error I am getting this error on my Site Health, and I understandably can’t find myself on Mastodon or Webfinger search either.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
should support email usernames: users show bugs, compatibility, missing feature pain that may indicate a product gap.
Evidence: should support email usernames The get_user_by_uri() static functiopn should support useranmes which are email addresses I patched it by adding: `case ‘acct’: // check acct scheme if ($the_user = get_user_by(‘login’, $host)){ return $the_user; } Woocommerce and plenty of other plugins use the email address as the username.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Usage: users show setup pain that may indicate a product gap.
Evidence: I have a stupid question : I installed and activated the plugin but now I wonder how to use it.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
[Plugin: Webfinger] WPMU: users show missing feature, setup pain that may indicate a product gap.
Evidence: [Plugin: Webfinger] WPMU Is there a way to make this work with multiblog installations?This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.