Deprecated: Optional parameter $function declared before required parameter $page is implicitly treated as a required parameter in /home/swalsh/public_html/wp-content/plugins/cron-view/plugin.php on line 201

Deprecated: Creation of dynamic property autoptimizeImages::$lazyload_counter is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php on line 34

Deprecated: Creation of dynamic property autoptimizeCompatibility::$conf is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeCompatibility.php on line 18

Deprecated: Creation of dynamic property autoptimizeCriticalCSSCore::$criticalcss is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeCriticalCSSCore.php on line 20

Deprecated: Creation of dynamic property autoptimizeImages::$lazyload_counter is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php on line 34

Deprecated: Creation of dynamic property Smush\Core\Modules::$webp is deprecated in /home/swalsh/public_html/wp-content/plugins/wp-smushit/core/class-modules.php on line 109

Deprecated: Creation of dynamic property Jetpack_Publicize::$modules is deprecated in /home/swalsh/public_html/wp-content/plugins/jetpack/modules/publicize.php on line 38

Deprecated: Creation of dynamic property Automattic\Jetpack\Publicize\Publicize_UI::$in_jetpack is deprecated in /home/swalsh/public_html/wp-content/plugins/jetpack/modules/publicize.php on line 101

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
Walsall FC tweets Wolves are "inbred bastards" - Digital-Football.com - Football Social Media & Digital Sports news

Walsall FC tweets Wolves are “inbred bastards”

League One side Walsall FC received huge backlash last night after their official Twitter account with over 11,920 followers tweeted out a string of angry abuse to the official Wolverhampton Wolves Twitter account. The person behind the account tweeted,

“@OfficialWoves Better look next time you six fingered, inbred, dingle bastards. YOU’VE LET US DOWN AGAIN!!!!”

Walsall Football Club however stated that the tweet appeared after their account was hacked at 22:36. In an official statement posted on their Facebook Page, the Walsall Communications Team stated:

“We would like to apologise unreservedly to Wolverhampton Wanderers and their supporters for the offensive Tweet that appeared on the club’s Official Twitter Page – @WFCOfficial – last night.

Our Official account was hacked at 22:36 last night and a derogative and frankly disgusting Tweet was published. As soon as the club’s Communications Team, who were at Molineux for the fixture, were made aware of the Tweet, it was deleted and an apology issued.

Walsall Football Club are taking this matter very, very seriously. A full investigation will be launched.

Walsall FC do not condone this type of behaviour and when the culprit is identified the club will be taking the strongest course of action.”

1187009_10153263200855584_1325468397_nThe event highlights just how important it is to ensure the security of all Social Media accounts are regularly maintained and checked. With so many different staff and departments increasingly wanting access to club accounts, Social Media managers need to either have a rolling password or ensure that all communications come through a compliance process to ensure that these types of embarrassing situations don’t crop up.

A single mishap or disgruntled former employee can cause havoc with a club’s reputation in an instant. Ensuring that passwords are changed every time staff leave the company and encouraging a vigilant security policy for Social Media are great and easy ways to ensure safety for club, players and brand.

Particularly with many clubs using mobile devices to manage their Social Media channels, they need to be extra careful their devices don’t fall into the wrong hands and additional security measures (such as phone PIN codes) are put in place.

It’s no wonder we’re starting to see specialised tools like Social Pundit – to help aid, monitor and advise on protecting against Social Media embarrassments.

Sean Walsh

Founder of Digital-Football.com and leading Football Social Media expert.

You may also like...

3 Responses

Leave a Reply

Your email address will not be published. Required fields are marked *