Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-logging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
{"id":3535,"date":"2018-01-25T11:28:26","date_gmt":"2018-01-25T11:28:26","guid":{"rendered":"https:\/\/nextcloud.com\/?p=3535"},"modified":"2018-01-25T11:28:26","modified_gmt":"2018-01-25T11:28:26","slug":"activitypub-the-new-standard-for-decentralized-networks","status":"publish","type":"post","link":"https:\/\/staging.nextcloud.com\/it\/blog\/activitypub-the-new-standard-for-decentralized-networks\/","title":{"rendered":"ActivityPub: the new standard for decentralized networks"},"content":{"rendered":"

Today, the World Wide Web gained a new standard: ActivityPub.<\/a> The recommendation has been published by the responsible W3C workgroup after 3 years of work, started in no small part by Christopher Lemmer Webber, founder of the Mediagoblin project. Nextcloud uses ActivityPub, implementing it to handle Activity federation between servers, crucial for our Global Scale architecture.<\/a><\/p>\n

And indeed, you may already be using ActivityPub now without realizing it.<\/p><\/blockquote>\n

–Christopher Lemmer Webber<\/p>\n

Nextcloud and ActivityPub<\/h2>\n

Nextcloud implements ActivityPub to inform users about changes to their files, new calendar and so on between users on different Nextcloud servers since Nextcloud 12. This makes ActivityPub part of what makes Nextcloud Global Scale work!<\/a><\/p>\n