diff --git a/architecture design proposal.md b/architecture design proposal.md
index 4c05473..7f2b5d5 100755
--- a/architecture design proposal.md	
+++ b/architecture design proposal.md	
@@ -181,7 +181,7 @@ The specifications allow for a lot of flexibility in their use. As WordPress web
 
 ## What features does our event federation project need?
 
-- For maximum Mobilizon compatibility we would love to have simply an actor of type `Application`, preferable called `@relay@wordpress.site`, that announces all events. Nonetheless, in theory, a Mobilizon instance should have the capability to follow any other actor as well.
+- For maximum Mobilizon compatibility we would love to have simply an actor of type `Application`, preferable called `@relay@wordpress.site`, that announces all events. Nonetheless, in theory, a Mobilizon instance should have the capability to follow any other actor as well. More or less this can already be achieved with the current blog-actor.
 
 - Additionally, for example, organizers in [The Event Calendar](https://wordpress.org/plugins/the-events-calendar/) could also offer their own actor of type `Organizer` or `Group` to publicize events, or create events if the `author`-actors are not enabled.