nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqg7uv8c82xmn9kt8g9swc29v90cu25n9shnm89qkmx7ujary25mnqpya082 (nprofile…a082) nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqn9wg3u0qseyuk96ft4n82ltpc9av3ml6w5gve5vguezqs9wlh2xs0r7p3a (nprofile…7p3a)
Do you think I should elaborate more on this?
Yes. I think an example from FEP-1b12 realm will be helpful. Can actors from FEP-1b12 "moderators" collection be considered authorised actors?
There's a footnote on what authorised actors are, tldr it's however you decide to do it.
In that section, you mention "the 'invite-actor'". Does this term refer to InviteCode.attributedTo actor?
It's a side effect of Add currently. Should it be the other way around? I guess Create<Note> adds to the outbox, so it would make sense.
I would expect that an invite code is Created first, and then Added. At least when using ActivityPub API clients.
silverpill
npub1df…27gmw
2026-08-07 18:30:26 UTC
in reply to nevent1q…qhj4
Author Public Key
npub1df0nthpgzfmvxrzj0cfypmmt45l0y770j260auqhm3l45hp3uhkqx27gmwSeen on
wss://relay.ditto.pubPublished at
2026-08-07 18:30:26 UTCEvent JSON
{
"id": "0f2c29b586e0b249c6b7f49d017401474452d362e03f9bcc67af059be9b024a6",
"pubkey": "6a5f35dc281276c30c527e1240ef6bad3ef27bcf92b4fef017dc7f5a5c31e5ec",
"created_at": 1786127426,
"kind": 1,
"tags": [
[
"p",
"47b8c3e0ea36e65b2ce82c1d8515857e38aa4cb0bcf67282db37b92e8c8aa6e6",
"wss://relay.ditto.pub"
],
[
"p",
"995c88f1e08649cb17495d66757d61c17ac8effa7510ccd188e6440815dfba8d",
"wss://relay.ditto.pub"
],
[
"p",
"d63e02ff2d31dd1b1c798df0a9ba9d6582553eaef5efba62b3d961a48e05bdb4",
"wss://relay.ditto.pub"
],
[
"p",
"79d9cd1ae6ee4b8be5078122d1e25891a47f7f9ed6e7cb65964f96ad5d31fc1a",
"wss://relay.ditto.pub"
],
[
"e",
"67941b0a4a3a38b9be83288ba5f8402eb2cbcd0e23ed5540935dda8d226e23ba",
"wss://relay.ditto.pub",
"reply"
],
[
"proxy",
"https://mitra.social/objects/019fdd7d-a41d-75d0-9f4c-628ad40db96c",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqg7uv8c82xmn9kt8g9swc29v90cu25n9shnm89qkmx7ujary25mnqpya082 nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqn9wg3u0qseyuk96ft4n82ltpc9av3ml6w5gve5vguezqs9wlh2xs0r7p3a\n\nDo you think I should elaborate more on this?\n\nYes. I think an example from FEP-1b12 realm will be helpful. Can actors from FEP-1b12 \"moderators\" collection be considered authorised actors?\n\nThere's a footnote on what authorised actors are, tldr it's however you decide to do it.\n\nIn that section, you mention \"the 'invite-actor'\". Does this term refer to InviteCode.attributedTo actor?\n\nIt's a side effect of Add currently. Should it be the other way around? I guess Create\u003cNote\u003e adds to the outbox, so it would make sense.\n\nI would expect that an invite code is Created first, and then Added. At least when using ActivityPub API clients.",
"sig": "58c2115cb1e1d53edcb7c339bdb5a65c20d300be5606b365348832cbca44bb08c0fed907517be58c06f00c5afabf48bd181090d3105729e16ab1718cb29bad1e"
}