masto / AP dev help
I'm working on a new AP server. I respond to Webfinger:
❯ curl -s https://exlibris.social/.well-known/webfinger?resource=acct:dconley@exlibris.social | jq
{
"subject": "acct:dconley@exlibris.social",
"aliases": [
"https://exlibris.social/@dconley",
"https://exlibris.social/user/dconley"
],
"links": [
{
"rel": "http://webfinger.net/rel/profile-page",
"type": "text/html",
"href": "https://exlibris.social/@dconley"
},
{
"rel": "self",
"type": "application/activity+json",
"href": "https://exlibris.social/user/dconley"
}
]
}
1/
masto / AP dev help
and hitting the `self` endpoint returns data:
❯ curl -s -H 'accept: application/activity+json' 'https://exlibris.social/user/dconley' | jq
{
"@context": [
"https://www.w3.org/ns/activitystreams"
],
"id": "https://exlibris.social/user/dconley",
"type": "Person",
"following": "https://exlibris.social/user/dconley/following",
"followers": "https://exlibris.social/user/dconley/followers",
"inbox": "https://exlibris.social/user/dconley/inbox",
"outbox": "https://exlibris.social/user/dconley/outbox",
"preferredUsername": "dconley",
"name": "Dan!",
"url": "https://exlibris.social/@dconley",
"manuallyApprovesFollowers": true,
"publicKey": {
"id": "https://exlibris.social/user/dconley#main-key",
"owner": "https://exlibris.social/user/dconley",
"publicKeyPem": "-----BEGIN PUBLIC KEY-----\nMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDaR8kyz5VvKlFEPIgps8KJKgFN\n9wlHQi9q40LLuyIddzZzuvUFsyJnLx6F9a9Epkg0xWeYNo2yXEpcvkQtkVlIWNgR\ncnWQ+W2cuDGn2AogifyXQ6HagwNXypVokX12uemtmT6Hn9Cv+R3r5Ty8wO4Yqcin\nYQbxnHnpJRllm69SCQIDAQAB\n-----END PUBLIC KEY-----\n"
},
"endpoints": {
"sharedInbox": "exlibris.social/inbox"
}
}
BUT 2/3
masto / AP dev help
Searching for dconley@exlibris.social / @dconley@exlibris.social here on cybre produces no results.
Is it because the inbox/outbox don't currently do anything?
masto / AP dev help
or it could be because the profile page 404s
I'm wooooorkin on it!
I guess I just want to know when to expect this to work
masto / AP dev help
Update: I see it hitting webfinger in the logs! And then I return a 404 when I really shouldn't, which is weird. So that's my answer.