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":1742,"date":"2023-06-02T07:56:38","date_gmt":"2023-06-02T07:56:38","guid":{"rendered":"https:\/\/ap-wa-blog-admin-2.azurewebsites.net\/?p=1742"},"modified":"2023-06-02T07:56:40","modified_gmt":"2023-06-02T07:56:40","slug":"amulet-social-media-report-may-2023","status":"publish","type":"post","link":"https:\/\/amulet.org\/blog\/amulet-social-media-report-may-2023\/","title":{"rendered":"Amulet Social Media Report – May 2023"},"content":{"rendered":"\n
Amulet is officially into its second year since announcing our project to protect digital assets in DeFi. We have grown our socials at a fast pace over the previous 12 months and we’re only seeing a drop in follower numbers due to old\/non-active accounts being removed.<\/p>\n\n\n\n
Amulet is tweeting daily and our community use Discord as their main form of communication. On August 30th 2022, we launched the\u00a0AmuNation app<\/mark><\/a><\/strong>, our fun loyalty campaign to engage our community through daily rewards and tasks which has still been ongoing throughout May 2023<\/p>\n\n\n\n Our April Social Media report is available here:\u00a0https:\/\/amulet.org\/blog\/amulet-social-media-report-april-2023\/<\/strong><\/p>\n\n\n\n Instagram and Link3:<\/strong><\/p>\n\n\n\n As revealed in last month’s report, we launched our Link3 and Instagram accounts. We’ve continued to implement these socials as part of our regular messaging along with Linkedin and Telegram Announcements (Twitter and Discord to be taken for granted!).<\/p>\n\n\n\n These are growing organically and we’re continuing to post our news and events on both platforms.<\/p>\n\n\n\n These two socials and all the socials that we post on can be followed or subscribed to here: https:\/\/linktr.ee\/amuletprotocol<\/mark><\/strong><\/a><\/p>\n\n\n\n May Twitter Highlights:<\/strong><\/p>\n\n\n\n May was another month of being active on Twitter with a major cleanup of our followers happening on 5 occasions, removing any bots or falsified accounts from our following. Here are some cool stats:<\/p>\n\n\n\n May Twitter Special Moments:<\/strong><\/p>\n\n\n\n We launched our very successful Protect and Stake for a MetaBear campaign:<\/p>\n\n\n\n
\n\n\n\n
<\/figure>\n\n\n\n
<\/figure>\n<\/figure>\n\n\n\n
\n\n\n\n
\n\n\n\n