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
The FA issues further Social Media warnings to clubs - Digital-Football.com - Football Social Media & Digital Sports news

The FA issues further Social Media warnings to clubs

Less than a week after the Premier League issued Social Media guidelines, it has been revealed that the Football Association of England (The FA) have given member clubs further warnings about “social networking sites”. In a letter to clubs sent two weeks ago (and subsequently leaked on Twitter so we can’t confirm it is 100% authentic), the FA provides clubs with several bullet points outlining what players shouldn’t be doing on the likes of Twitter and Facebook.

The FA state in the document that it was in response to an increased level of complaints and incidents on social networking sites from football players – the letter even goes as far as to exclusively name Twitter.

The letter – written more as a series of warnings rather than guidelines – covers the usual range of topics such as:

  • – improper comments may bring the game into disrepute
  • – references on personal ethnicity, race, faith, disability, sexual orientation etc. will be punished at a higher level
  • – players accept responsibility for their own accounts
  • – all comments are considered public by the FA

However, what is more interesting is that the document also refers to a number of issues that are less obvious and perhaps the FA has experienced more in the past few months. For example, players are warned that they may receive disciplinary action for simply retweeting improper content – thereby removing the excuse that somebody else had made the comment. Other interesting warnings include the potential repercussions for comments about match officials that imply bias, questioning integrity or personal abuse. Players are also advised that simply deleting a social media posting will not prevent disciplinary action.

The warning comes two weeks before Rio Ferdinand was charged by the FA for Twitter comments he made about Chelsea defender Ashley Cole. Clearly, the FA are worried about the growing adoption rate of social media amongst football players and are keen to ensure that players do not bring the “beautiful game” into the social media battlefield. Whilst the FA should be commended for ensuring players have clear guidelines regarding what they can and cannot do, this only solves half of the problem.

If the FA, and it’s member clubs, were serious about ensuring best practice and using social media to improve the game, then they would combine these guidelines with education. Simply laying out rules is not enough.

Instead, the FA (or clubs) should host social workshops or training for players so that they can understand everything from how to use social media, what the regulations are (both club, league and nationally) and provide examples of both good and bad social media practice. This is a difficult task and one that will continue to be challenging for clubs, however, some clubs are already seeing signs of success. Birmingham City told Digital-Football.com in an interview that they educate their players from their academy upwards.

The Midlands side go as far as hosting staged press interviews where the interviewer will have previously looked at the players social media channels in order to find anything that can be used against them. The lesson teaches players to be protective of their channels and what they say, as well as help them experience and cope with the modern day techniques of journalists.

Source: Image of the letter came from Daniel Taylor (Chief Football Writer for the Guardian) who tweeted it 30/7/2012)

Sean Walsh

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

You may also like...

Leave a Reply

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