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":1782,"date":"2023-07-05T08:43:33","date_gmt":"2023-07-05T08:43:33","guid":{"rendered":"https:\/\/ap-wa-blog-admin-2.azurewebsites.net\/?p=1782"},"modified":"2023-07-05T08:45:20","modified_gmt":"2023-07-05T08:45:20","slug":"amulet-social-media-report-june-2023","status":"publish","type":"post","link":"https:\/\/amulet.org\/blog\/amulet-social-media-report-june-2023\/","title":{"rendered":"Amulet Social Media Report – June 2023"},"content":{"rendered":"\n
\n\n\n\n

Amulet Protocol was announced as a project in April 2022, kicking off the start of our community building and creating a social media strategy with consistent growth. We implement social media as a core component within our marketing plan as it helps promote our activity and innovative work behind the scenes.<\/p>\n\n\n\n

Our community grew at an incredible pace throughout the last 12 months despite turbulent market conditions and 2 of the biggest crises to have hit our industry in recent years.<\/p>\n\n\n\n

Amulet is here to protect digital assets and continue to BUIDL the create the catalyst needed for mass global web3 adoption. This report provides you with some of our key highlights on Social Media throughout the month of June.<\/p>\n\n\n\n

To follow and see a list of all our social media, please refer to our linktree: https:\/\/linktr.ee\/amuletprotocol<\/a><\/strong><\/p>\n\n\n\n

To read our Social Media report for May, please click here.<\/a><\/strong><\/p>\n\n\n\n

\n\n\n\n

New in June:<\/strong><\/p>\n\n\n\n

Following on from the recent launches of our Instagram and Link3 in May, we’ve taken advantage of the recent (and radical!) changes by Twitter. We launched our Twitter community only days after Twitter launched this feature. This community is now 300+ strong and continuing to grow at a steady pace with people tweeting daily. <\/p>\n\n\n\n

We’ve continued to stick to our colour theme for Instagram too and we’re very close to hitting 500 followers! All the followers here are completely organic and we haven’t conducted any specific marketing activity to promote these away from our own standard announcement processes. <\/p>\n\n\n\n

We will continue to implement and improve on these platforms throughout the month of July. We’re always open to community feedback and suggestions regarding new platforms and expanding our reach.<\/p>\n\n\n\n

\n
\"\"
AmuNation Twiter Community<\/figcaption><\/figure>\n\n\n\n
\"\"
Users within the community<\/figcaption><\/figure>\n\n\n\n
\"\"
Instagram continuing to stick to theme<\/figcaption><\/figure>\n<\/figure>\n\n\n\n
\n\n\n\n

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

Twitter has always been our main announcement channel (while Discord is our main communication hub) and as always, we usually give statistics regarding Twitter. As many of you will be aware, lots of activity and changes have been taking place on Twitter since Elon Musk’s takeover. Amulet is always keen to adapt and embrace situations and despite it stunting our growth over the last couple of months, we’ll be taking advantage of all new features by Twitter and seeing how we can utilise them to continue to grow Amulet and protect more users!<\/p>\n\n\n\n

We’ll also be utilising alternatives (while continuing to implement Twitter). Threads by Instagram is due to launch tomorrow (July 7th 2023) and we’ll look into becoming one of the first big players of Facebook’s “Twitter alternative”. We’ll reveal more news here once our plan is finalised. This will not affect our usage of Twitter which will still be a minimum of 2-3 tweets per day, 365 days per year!<\/p>\n\n\n\n

If you were unaware, Twitter has also implemented rate limits for users for data protection purposes. This could affect unverified Twitter users heavily and the BEST way to prevent missing out on news is by setting notifications to our tweets. This means that the tweet will go directly to your notifications without affecting your rate limit. <\/p>\n\n\n\n

Due to recent changes by Twitter themselves, our Twitter feed on Discord is currently down but the team is working hard to manually implement this until the tool is fixed. <\/p>\n\n\n\n

It also states on Twitter analytics that some statistics below may NOT be as accurate as usual as they’re working on improvements currently.<\/p>\n\n\n\n

Stats:<\/p>\n\n\n\n