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

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

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: http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated in /home/swalsh/public_html/wp-includes/Requests/Transport/cURL.php on line 345

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

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758
{"id":6176121680,"date":"2012-03-08T21:28:25","date_gmt":"2012-03-08T21:28:25","guid":{"rendered":"http:\/\/digital-football.com\/?p=6176121680"},"modified":"2012-03-08T21:28:25","modified_gmt":"2012-03-08T21:28:25","slug":"how-will-social-media-and-sports-tv-work-heres-a-few-ideas","status":"publish","type":"post","link":"http:\/\/digital-football.com\/uncategorized\/how-will-social-media-and-sports-tv-work-heres-a-few-ideas\/","title":{"rendered":"How will social media and sports TV work? Here\u2019s a few ideas\u2026"},"content":{"rendered":"

<\/object><\/p>\n

I recently came across a\u00a0video<\/a>\u00a0by Sports Business blogger,\u00a0Russell Scibetti<\/a>\u00a0at the Global Sports Forum in Barcelona. Russell gave an example of how very soon we can expect to see social media (more specifically online audience participation) working alongside\u00a0sports broadcasting<\/a>. It\u2019s something that I predict will become immensely huge within the next 2 years. Sports fans love statistics, and they love opinions, that\u2019s why so many read blogs or the papers. However, there\u2019s an increasing trend to micro-blog during live sports events via\u00a0Facebook<\/a>\u00a0and\u00a0Twitter<\/a>. This goldmine of fan created content is waiting to be tapped into and there is massive potential for how broadcasters can be creative in delivering the very latest \u201cbuzz\u201d across social media. Here are a few ideas:<\/p>\n

Hashtag co-ordination<\/strong><\/p>\n

A simple enough concept but this will be the first step for sports broadcasters to motivate their audience to create conversations in-play. It only takes a prompt somewhere on the screen, or a presenter to explain that fans can follow what\u2019s being said by contributing to a game specific\u00a0hashtag<\/a>. Whilst this is easy to do on Twitter, on Facebook it is a little more complex. Sports broadcasters could integrate their own Facebook page into their official website and use the\u00a0social plugins available<\/a>\u00a0so the audience could leave their opinions in the commentary box. With all this data in one easy to find hashtag, broadcasters could then select appropriate comments and show them on screen.<\/p>\n

Sky Sports<\/a>\u00a0Fanzone<\/a>\u00a0used to show fans\u00a0SMS messages<\/a>, so why not bring this back but enhance it with social media?<\/p>\n

Retweet\/Like competition for match decisions<\/strong><\/p>\n

This idea involves simplifying how broadcasters can compile opinion, and also exploit the competitive nature of sport rivalry. Rather than ask for comments, broadcasters could simply offer A or B answers to a questions via individual tweets, and then urge their followers to retweet\/Like whichever answer they think is best. This could be used for matters such as:<\/p>\n