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":1632,"date":"2023-04-03T09:04:30","date_gmt":"2023-04-03T09:04:30","guid":{"rendered":"https:\/\/ap-wa-blog-admin-2.azurewebsites.net\/?p=1632"},"modified":"2023-04-06T06:13:54","modified_gmt":"2023-04-06T06:13:54","slug":"amulet-social-media-report-march-2023","status":"publish","type":"post","link":"https:\/\/amulet.org\/blog\/amulet-social-media-report-march-2023\/","title":{"rendered":"Amulet Social Media Report – March 2023"},"content":{"rendered":"\n
\n\n\n\n

Amulet Protocol was announced as a project in April 2022. We have been working on growing our social channels organically and here is our lowdown of what went on during the month of March 2023! The 11th month since we started posting on Social Media.<\/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 AmuNation app<\/mark><\/a><\/strong>, our fun loyalty campaign to engage our community through daily rewards and tasks which has still been ongoing throughout March.<\/p>\n\n\n\n

March also saw the implementation of a new social media with our TG events notification channel. Follow here.<\/a><\/strong><\/p>\n\n\n\n

Make sure to follow our socials here:<\/strong><\/p>\n\n\n\n

Linktree (For all!):  https:\/\/linktr.ee\/amuletprotocol<\/mark><\/a><\/strong><\/p>\n\n\n\n

Access our Twitter here:  https:\/\/twitter.com\/AmuletProtocol<\/mark><\/strong><\/a><\/p>\n\n\n\n

Join our Discord server here: https:\/\/discord.gg\/AmuletProtocol<\/mark><\/strong><\/a><\/p>\n\n\n\n

Follow our Telegram Announcements: https:\/\/t.me\/amulet_announcement<\/mark><\/strong><\/a><\/p>\n\n\n\n

Subscribe to our YouTube channel here: https:\/\/www.youtube.com\/@AmuletProtocol<\/mark><\/a><\/strong><\/p>\n\n\n\n

Follow our Linkedin company profile here: https:\/\/www.linkedin.com\/company\/amuletprotocol\/<\/mark><\/a><\/strong><\/p>\n\n\n\n

Subscribe to our Soundcloud here: https:\/\/soundcloud.com\/amuletprotocol<\/mark><\/a><\/strong><\/p>\n\n\n\n

Follow our Amulet TikTok fun account: https:\/\/www.tiktok.com\/@amulet_protocol_fun<\/mark><\/strong><\/p>\n\n\n\n

Follow our BRAND NEW<\/strong> Telegram events notication channel: https:\/\/t.me\/+HPJJJYpsZkwzNGY9<\/strong><\/p>\n\n\n\n

If you want to read our February Social Media report, just click here<\/mark><\/mark><\/strong>.<\/a><\/mark><\/p>\n\n\n\n

\n\n\n\n

We also have socials set up for our CIS-language community!<\/strong><\/p>\n\n\n\n

TG Announcement (CIS language) \u2013 https:\/\/t.me\/AmuletProtocolCIS<\/mark><\/a><\/strong><\/p>\n\n\n\n

Medium (Blog in CIS) \u2013 https:\/\/medium.com\/@amuletprotocol_ru<\/mark><\/a><\/strong><\/p>\n\n\n\n

\n\n\n\n

March Twitter Highlights:<\/strong><\/p>\n\n\n\n

In our 11th month of being active on Twitter, we’ve seen another solid month of organic growth. There was also a Twitter cleanup with bot followers which saw us lose 3k followers. Although this hurt our numbers initially, we’ve managed to grow continiously and make up for this chunk of lost followers. It was important to mention as we’ve actually grown further than our numbers initially suggest due to this bot cleanup.<\/p>\n\n\n\n

Below are some awesome stats from Twitter in March:<\/p>\n\n\n\n