New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

activitypub profile discovery #204

donpdonp opened this Issue Apr 24, 2017 · 5 comments


None yet
5 participants
Copy link

donpdonp commented Apr 24, 2017

I'm trying to piece together the activitystream steps and I havent seen a spec for finding someone's "Person" object from a homepage url. I looked at an existing identifier I had on my homepage

<link rel="alternate" type="application/ld+json" href="webid.json"/>

and fixed it up to look more like something an activitypub service might discover.

<link rel="me" type='application/ld+json; profile=""' href="as-person.json"/>

I'm not sure if the profile part of the mime-type belongs in the type field. I put indieweb's "me" rel in place of "alternate" because its friendlier. I dont expect anything to consume this tag today, I just added it to my site ( to see how it might work.


This comment has been minimized.

Copy link

csarven commented Apr 25, 2017

Wouldn't the relation be along the lines of primaryTopic/creator/maker?


This comment has been minimized.

Copy link

donpdonp commented Apr 25, 2017

there was some discussion on the w3c irc meeting today

with the conclusion being

<link rel="alternate" type="application/activity+json" href="as-person.json"/>

would be an acceptable tag.


This comment has been minimized.

Copy link

cwebber commented Apr 25, 2017

I think the conversation from today is that those are acceptable link relations and are informative / welcome for people to put places. Our official way of moving from a link describing an actor to their profile is via content negotiation though. That said, a client might even know how to look up a profile based on finding that on a uri, but we aren't putting that in the official spec, doing so would be an extension... but maybe defining such an extension would be good work to do through the community group.

Does that answer things @donpdonp? Thanks! :)


This comment has been minimized.

Copy link

donpdonp commented Apr 25, 2017

given "", and needing a json Person document for activitypub operations, doing a GET with Accept: application/activity+json seems ok as one way to get this document.

As a recommendation for someone trying to add an activitystream identitiy to their website, using content negotiation seems like a rocky path. The average php hosting service for example, does not have a paradigm in its UI for a document per mime type. Even with full control of an nginx config, its an unusual kind of configuration entry.

Having link rel="alternative" as a fallback is a great alternative. Anyone who knows how to edit html will be able to add an extra tag linking to the url of the json document for that person.

@donpdonp donpdonp closed this Apr 25, 2017


This comment has been minimized.

Copy link

strugee commented Apr 25, 2017

I've added this to the list of possible AP extensions:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment