You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While thinking through my own implementation it occurs to me that one could make a quick call to {domain}/.well-known/nodeinfo and stop processing immediately if that route returns non-200, since it's one signal you could use to determine that an instance does not support ActivityPub.
In terms of sensitivity vs. specificity, this is a not a high sensitivity test, because an instance returning nodeinfo might not be a true AP server or respond appropriately via any of the documented methods for link discovery.
However it is fairly specific, in that its absence can indicate no support at all. Given that nodeinfo support cannot be assumed, this test is not foolproof.
The text was updated successfully, but these errors were encountered:
While thinking through my own implementation it occurs to me that one could make a quick call to
{domain}/.well-known/nodeinfo
and stop processing immediately if that route returns non-200
, since it's one signal you could use to determine that an instance does not support ActivityPub.In terms of sensitivity vs. specificity, this is a not a high sensitivity test, because an instance returning nodeinfo might not be a true AP server or respond appropriately via any of the documented methods for link discovery.
However it is fairly specific, in that its absence can indicate no support at all. Given that nodeinfo support cannot be assumed, this test is not foolproof.
The text was updated successfully, but these errors were encountered: