ActivityStreams endpoints #10

New Issue

Open

opened 2022-09-28 09:02:54 +00:00 by heartles · 0 comments

heartles commented

2022-09-28 09:02:54 +00:00

Owner

Need endpoints that serve the ActivityStreams object for:

Users (Actors with type of Person or Service based on bot status)
Posts (Notes)
Reactions? probably, if we're supporting different types. (Activitys with type of Like)

Endpoints can overlap with existing endpoints, but the router would have to be updated to also switch based on media type.

The activity MUST be served if the client requests a media type of

application/activity+json
application/ld+json, especially with profile="https://www.w3.org/ns/activitystreams"
Should probably do it for application/json too for robustness
Can serve for other media types too, but if we're having this endpoint overlap another one (say, public HTML) then we'd have to figure out which one takes priority

Deleted objects should serve up a Tombstone object with little/no data

https://www.w3.org/TR/activitystreams-vocabulary
https://www.w3.org/TR/activitystreams-core

Need endpoints that serve the ActivityStreams object for: - Users (`Actor`s with type of `Person` or `Service` based on bot status) - Posts (`Note`s) - Reactions? probably, if we're supporting different types. (`Activity`s with type of `Like`) Endpoints *can* overlap with existing endpoints, but the router would have to be updated to also switch based on media type. The activity MUST be served if the client requests a media type of - `application/activity+json` - `application/ld+json`, especially with `profile="https://www.w3.org/ns/activitystreams"` - Should probably do it for `application/json` too for robustness - Can serve for other media types too, but if we're having this endpoint overlap another one (say, public HTML) then we'd have to figure out which one takes priority Deleted objects should serve up a Tombstone object with little/no data https://www.w3.org/TR/activitystreams-vocabulary https://www.w3.org/TR/activitystreams-core