FEP-2677: Identifying the Application Actor

[silverpill]

This document MUST then contain a link with relation https://purl.archive.org/funfedi/applicationActor

@helge I suggest using https://www.w3.org/ns/activitystreams#Application relation type, which would be self-describing.

Next, a request to https://node.example/actor with accept header application/activity+json could return

Spec-compliant implementations MUST use application/ld+json; profile="https://www.w3.org/ns/activitystreams"

@nutomic

For Lemmy we simply have the instance actor available at the root path, eg at https://lemmy.ml/. I think that makes a lot more sense than a separate resolve step, or hardcoding a software specific path.

This might be difficult to implement in some cases, for example when instance root URL is a static site. NodeInfo/WebFinger provides more flexibility.

---

Also, an old discussion on instance actors: Activities for Federation Application?