Evan Prodromou

> another thing that could make sense is a `mutuals` collection that is dynamically calculated based on a query of actors that are items of both `following` and `followers`: So,...

One option is to have a property of the actor profile that provides a collection of additional profile data objects. ``` { "@context": { "https://www.w3.org/ns/activitystreams", "profiles": "@id", }, "type": "Person",...

@thisismissem notes that the alternativeProfiles collection could be filtered by authorization by the server, as we do for filtered collections.

> What's the user story for this? followers collections? I think the main one would be for authorizing followers/following. Here's an example: ``` { "@context": "https://www.w3.org/ns/activitystreams", "id": "https://server1.example/user/a/note/1", "type": "Note",...

Whether or not the conflation of paged and unpaged collections was a good idea, it is already standardized and we will need to deal with the backwards compatibility for this...