Collections in ActivityPub are special, because they are not independent objects, but aggregations of activities. I think FEP-ef61 implementations should not add integrity proofs to them, but treat them as virtual objects whose representations are always server-generated. Re-signing collections and collection pages after every update is not practical.
#fep_ef61
silverpill /
npub1df0…7gmw
2024-06-05 22:45:40
Author Public Key
npub1df0nthpgzfmvxrzj0cfypmmt45l0y770j260auqhm3l45hp3uhkqx27gmwPublished at
2024-06-05 22:45:40Event JSON
{
"id": "fe8fdc5a36d11dee507a1271b2bc19faa6890ff8d3fa2860a81b7d5c38efa529",
"pubkey": "6a5f35dc281276c30c527e1240ef6bad3ef27bcf92b4fef017dc7f5a5c31e5ec",
"created_at": 1717620340,
"kind": 1,
"tags": [
[
"t",
"fep_ef61"
],
[
"proxy",
"https://mitra.social/objects/018fea26-7605-6128-ee72-5291484d8206",
"activitypub"
]
],
"content": "Collections in ActivityPub are special, because they are not independent objects, but aggregations of activities. I think FEP-ef61 implementations should not add integrity proofs to them, but treat them as virtual objects whose representations are always server-generated. Re-signing collections and collection pages after every update is not practical.\n\n#fep_ef61",
"sig": "38a44f82ef30b553c6576ddf7f61eb2f360cdf33829a23c25fc52e1edc7502fc928688de191a80cedb6b8ae2bd9d7a3f643741d7a1622c17b1f81fa85530433e"
}