From 0faaa256ca937887f2db848e222874c064373bd0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Menrath?= Date: Tue, 10 Oct 2023 16:09:12 +0200 Subject: [PATCH] fix grammar mistake --- architecture design proposal.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/architecture design proposal.md b/architecture design proposal.md index 0deda92..78ba2c4 100755 --- a/architecture design proposal.md +++ b/architecture design proposal.md @@ -218,7 +218,7 @@ We keep in mind that every post type shall only ever send as a `Create` Activity - Maybe forbid, that a user can automatically announce a post, because it's the "lowest level". ## Actor collisions -Each ActivityPub actor must have a [unique ID](https://www.w3.org/TR/activitypub/#obj-id). In our case this is a HTTPS URI. +Each ActivityPub actor must have a [unique ID](https://www.w3.org/TR/activitypub/#obj-id). In our case this is an HTTPS URI. But in reality [webfinger](https://webfinger.net/) is used: `@actor-name@instance.tld`. Actors like Persons and Groups and Applications have public keys attached to them, as well as their ID is probably cached by most software. So assigning some actor-name to something new also can cause unintended behavior. If multiple plugins want to individually federate their content (like events, products, and blog posts or even the built-in WordPress categories), they must be able to have something like an actor API, the ActivityPub plugin can register. The ActivityPub plugin being the main coordinator is necessary because actors are globally unique.