Anyone have experience when dealing with "public" and "collection" addresses while implementing ActivityPub?
In #ActivityPub / #ActivityStream , you can address "https://www.w3.org/ns/activitystreams#Public" and follower collections (e.g. "https://todon.eu/u/<username>/followers" on activities - side by side with actual user uri.
I think it's VERY difficult to implement these when importing to my own instance. For example, using #ObjectionJS to automatically join messages with addressees' accounts is hard, because it requires these "virtual users" in the table of actual users.
Does anyone have any experience with implementing this in their own solution?
#ActivityPubDev #webdevelopment #nodejs #Fediverse
#activitypub #activitystream #objectionjs #activitypubdev #webdevelopment #nodejs #fediverse