Following an interesting discussion on programming.dev after the last article, I thought it would be good to add some extra notes regarding Webfinger.
Webfinger provides a standard API for discovering the user profile details and avatar from the username, no matter the software running on the node. The standard Webfinger endpoint is /.well-known/webfinger
. It must always be queried with at least the resource.
Some examples using my account on Lemmy (programming.dev) and Mastodon (hachyderm.io):
|
|
|
|
|
|
|
|
While I’m not sure exactly how this is useful, my assumption is that it’s useful during federation, and for generic activitypub clients because different Fediverse software maps usernames and profiles differently.
Read Next
I’m running an experiment for better content recommendations. These are the 3 posts that are most likely to be interesting for you:
-
The secret life of .well-known
Unravel the secrets of the web’s hidden directories and discover how they power up your favorite online spaces, from secure email setups to finding your next favorite fediverse platform. -
Read This Next: Using AI For Recommending Posts On My Blog
Exploring how Webfinger revolutionizes user discovery in the fediverse, you’ll be intrigued by how AI-driven recommendations can similarly transform your content exploration with smarter, more personalized suggestions. -
Get leads collected by a particular lead ad form between two timestamps using Facebook Graph API
Explore how to harness the power of APIs further by learning to extract valuable data from Facebook Lead Ads, just like you discovered the potential of Webfinger for user discovery across platforms.