Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon 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 6131 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-sites 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 6131 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-schema-pro 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 6131 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the uael 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 6131 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpforms-lite 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 6131 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo 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 6131 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the convertpro-addon 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 6131 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra 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 6131 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon 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 6131 Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6131) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1902 {"id":1652,"date":"2023-04-18T17:12:49","date_gmt":"2023-04-18T17:12:49","guid":{"rendered":"https:\/\/ap-wa-blog-admin-2.azurewebsites.net\/?p=1652"},"modified":"2023-04-18T17:12:51","modified_gmt":"2023-04-18T17:12:51","slug":"amulet-adds-2-more-networks-to-our-social-media-arsenal-%f0%9f%a7%bf","status":"publish","type":"post","link":"https:\/\/amulet.org\/blog\/amulet-adds-2-more-networks-to-our-social-media-arsenal-%f0%9f%a7%bf\/","title":{"rendered":"Amulet adds 2 more networks to our social media arsenal! \ud83e\uddff"},"content":{"rendered":"\n
\n\n\n\n

As Amulet Protocol<\/a><\/strong> approaches a year since the project was first announced, we’re delighted to confirm the addition of two new social media networks! <\/p>\n\n\n\n

Despite two major crises within our industry over the last 12 months, Amulet has seen significant consistent social growth monthly. We want to become the biggest web3 cover protocol while also creating opportunities for users away from our field to find us. <\/p>\n\n\n\n

We’ve launched our Link3 account to increase our exposure to the crypto community, while also launching Instagram as a way of creating opportunities for Amulet within web2 while encouraging mass adoption of blockchain technology.<\/p>\n\n\n\n

It’s an exciting time for our project and the team is forever grateful to the AmuNation for supporting us on our journey so far.<\/p>\n\n\n\n

Both these networks have been launched at time of writing and have both been included on our linktree: https:\/\/linktr.ee\/amuletprotocol<\/a><\/strong><\/p>\n\n\n\n


\n\n\n\n

Link3:<\/strong><\/p>\n\n\n\n

Link3 is a Web3 native social platform which will enable users to find Amulet and our cover solution easily.<\/p>\n\n\n\n

We will use this to start posting our major news and also to announce our AMA’s to a new audience. <\/p>\n\n\n\n