nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqh73s7j2mdwzzv6a2fm9tfjchlaw4r7a59pfl0keqrahfja2k3stqle2gus (nprofile…2gus) Publishing process doesn't change much. A generic server should deliver activities to actors specified in to and cc fields. It should keep track of collections, such as followers collection, and "expand" them before delivery. This part is not different from the regular ActivityPub.
I think ID assignment should also work the same. In the FEP I proposed Add activity without object as a special activity for creating collections, but now I see that it will not work if IDs are minted by a server (no FEP-ae97).
Perhaps it should be a Create, after all, as nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq4uc4sdaw2f2dn9h3c7l5vx2fdcs66pjtuav2xyrv9c4j350cy5pqaqu8dh (nprofile…u8dh) described in an adjacent comment. I was hesitant to use Create because this is a problem for FEP-ae97 clients (not a big one though).
nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqku30mphs68tg30c4jj0d80g698resvue70hhrvnawxvdfaq4p0ushyd8rs (nprofile…d8rs) nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq4uc4sdaw2f2dn9h3c7l5vx2fdcs66pjtuav2xyrv9c4j350cy5pqaqu8dh (nprofile…u8dh)
