Sharing the excitement from floor of OSCON 2014, Kaltura’s Director of Playback Experience and Video Monetization, Michael Dale talks about Kaltura, open source and his OSCON talk about what’s happening with web video standards and html5.
Be sure to visit Michael’s OSCON 2014 talk – HTML5 Video Part Deux; New Opportunities and New Challenges and come by our booth (#P1).
Sharing the excitement from floor of OSCON 2014, Kaltura’s Director of Playback Experience and Video Monetization, Michael Dale talks about Kaltura, open source and his OSCON talk about what’s happening with web video standards and html5.
Like most developers, I was approached by my management to “Make Something Work” without having any prior experience. The job was to connect our Plone/Zope content management system to Kaltura, so web content editors could seamlessly upload and edit video content and metadata that is managed by the KMC. It wasn’t hard to find the Kaltura Python API Client Library, but once you have the Client Library, you have to learn how to use it – and at the same time, learn the features that the KMC provides (see:
Kaltura Management Console Training Track).
I can read through the many docs from cover to cover (I usually don’t) and still have the uncomfortable, lost feeling of having no clue what’s going on. And then there’s always the pressure of overcoming the learning curve in a reasonable amount of time.
So I begin by writing “Playground Code”. A directory that will be filled with useless, proof-of-concept code that helps me get the hang of a language, an API, or a new concept. This code will never be used in production, which gives me the permission to write really bad code while I climb up the learning curve.
Being able to become unattached to code, throw it all away and start over, was an important step for me. You learn the ‘right way’ to do things by doing them the ‘wrong way’ first. It also helped me figure out where exactly I should be reading in the docs to get done what needs to be done.
In the past few years, I’ve been working a lot with the concept of Test-Driven-Development. In TDD you write very small, encapsulated tests before you actually code the functionality or patch you are implementing. You are, in fact, intentionally writing failing test cases. I found this method very useful for isolating and fixing bugs, but not so much for new large projects or new enhancement development. The requirement that the tests should be atomic and very specific does not lend itself to complicated projects with many moving parts. Until now.
When I found myself having to learn the Kaltura Python Client Library – having no prior experience, I found the concept of “Playground Code” and Test Driven Development coming together. I simply took my proof of concept, put together some code and threw an assert() statement at the end, and viola – it’s now a test case!
“How do I connect to a Kaltura Server with the Python API”
The answer was “testConnect()” - that was easily incorporated into a test suite using python’s excellent testing framework ‘unittest‘ (Then, assert that something like client.media.list() returns something that looks like a response. Or, at the very least, not an exception).
I developed the trivial, but important test case at the same time I learned how to connect to the Kaltura server! My code doesn’t have to be thrown away, nor does it have to be perfect. However, it can now serve the purpose of being a proof of concept, a unittest, and a code example for the next developer all at the same time.
When I got confused with something, I could easily take my entire test case, which was an atomic, very specific exercise/problem, and post it to the forums as is – and quickly get a direct answer on what was confusing me – instead of submitting a link to my entire application with the “xxxx not working” title, which would have made it harder for others to review and help.
And then it got even better. The proof of concept code grew as I learned more about the API. A large tests module started forming. I started coming finding small bugs in the Kaltura Python Client Library, nothing critical, but important to my application – And I was able to patch, test and contribute my code upstream to the Kaltura project.
Through my humble experience (from complete newbie state) with Kaltura’s API and Python Client Library, I was able to submit and contribute a more polished and complete Python Test suite for the Kaltura API Client Library!
Want to join the Kaltura project and become an active contributor? Start Here.
Being open source provides users of the Kaltura platform many advantages. Amongst which, the ability to shape and influence the platform and its roadmap by contributing code to the project.
More often, when building a new integration or a publishing workflow, it’s a bit too much to dive into the platform code. That’s why you don’t have to!
Kaltura is a RESTful API driven platform.
This means that all features, user facing or internal, are all based on the same unified API.
From upload to through transcoding to playback, is all controlled via the API.
A RESTful API follows the following concepts:
- It’s uniform – in Kaltura, every service represents an object, and actions represents its methods . For example: the media service represents the KalturaMediaEntry object. The media.delete action deletes a given KalturaMediaEntry object.
- It’s stateless – In every API call you must provide a valid session key (dubbed KS). You can also create as many sessions as you need at the same time.
- It’s cacheable – Scale is a make or break with video applications. We cache more than 95% of API calls in Kaltura, once in memory and then even on the CDN.
- Layered System – Client have a single end point. This encapsulates whether the client connect to the end server, or to an intermediary along the way. Intermediary servers improve system scalability by enabling load-balancing and shared caches. Layers also enforce security policies and enhance system resilience.
A lot of projects offer a RESTful API. But what I believe makes the Kaltura API special are -
It’s API from the inside out!
The platform’s own components also use the same APIs to get their job done. This means core developers build and test using the same APIs that App developers use. Which in turn test and improves the APIs daily.
Always up-to-date SDKs
See the Kaltura.com client libraries page for complete list and downloads.
It’s Robust, Allowing Complete Control
As an outcome, the API is capable of controlling pretty much any operation the platform’s core components. From ingesting content through management and transcoding, to playback, delivery, distribution and analytics.
To further explain point A, lets dive further in to the Kaltura architecture:
The API and Client Libraries, are used across the platform’s components, both in external applications such as Kaltura MediaSpace or various modules to 3rd party systems such as Drupal or WordPress, as well as internally, within core Kaltura components such as transcoding batch servers or the platform Admin Console.
For example, the batch daemon, responsible for performing roles such as: media import, media info extraction, transcoding and server notifications, triggers these APIs the same way any other party, for example, your application, would: using the Kaltura API Client libraries.
Here is a short example of how the APIs (in this particular case, the PHP client libs) can be used to upload a new video entry to the system:
// require the Kaltura PHP5 client libs:
// generate a KS and return a client to work with:
function generate_ks($service_url,$partnerId,$secret,$type=KalturaSessionType::ADMIN,$userId=null,$expiry = null,$privileges = null)
$config = new KalturaConfiguration($partnerId);
$config->serviceUrl = $service_url;
$client = new KalturaClient($config);
$ks = $client->session->start($secret, $userId, $type, $partnerId, $expiry, $privileges);
$uploadToken = new KalturaUploadToken();
$result = $client->uploadToken->add($uploadToken);
$resume = null;
$finalChunk = null;
$resumeAt = null;
$result = $client->uploadToken->upload($tok, $fileData, $resume, $finalChunk, $resumeAt);
$entry = new KalturaBaseEntry();
$entry->name = $title;
$entry->conversionProfileId = $conv_profile;
$type = KalturaEntryType::AUTOMATIC;
$result = $client->baseEntry->addfromuploadedfile($entry, $tok, $type);
// call generate_ks() to instantiate a Kaltura client and start a session
// pass $client object and $video_file to upload() function to upload and create the new entry
Having an API driven architecture enables complete control and freedom with how you desire your application workflows and UI to be. From creating different publishing workflows to exposing sets of functionalities.
In addition, the API inside-out approach opens up many opportunities for adapting, controlling and extending beyond the simple UI workflows and apps, important examples are with platform automation and monitoring tools.
Playing with the API:
As mentioned, Kaltura provides client libs generated for various programming languages. In addition, API calls can be made using a testing tool dubbed the Kaltura TestMe console.
The first thing you would want to do is create a Kaltura Session – KS:
- Select ‘session’ as service and ‘start’ as action.
- In session type, select ‘USER’.
- The secret field corresponds to one of two strings that are saved in Kaltura for each partner and are available in your KMC under the Settings>Integration Settings tab. Note that there are two types of secrets, one that can be used to start an end-USER session and one to start an ADMIN session.
If you look at the screen shot above, you will see that, in the right frame, we have the returned XML which includes:
- The result tag with the KS ‘N2E1NGE1NGIxOGFlNWI3MDU1NWY4YTNmMTRjM2QwZDg2ZDA1YjM0MHwyNDk7MjQ5OzEzOTkyODc1OTA7MDsxMzk5MjAxMTkwLjM1NDs7Ozs=’ as value
- The executionTime tag with 3.71932983398 as value
In the bottom of the page, you can see the code our selections in the input form generated.
Notice that while the default displayed code is in PHP, you can click on one of the other languages to see the code generated for any other.
Next for a second example using the Test Me Console, we will list the entries our partner owns. Doing so by using the baseEntry service and calling its listAction() function.
As you can see, the generated code reads:
$config = new KalturaConfiguration($partnerId);
$config->serviceUrl = 'http://ce-lb.dev.kaltura.com:8001/';
$client = new KalturaClient($config);
$filter = new KalturaBaseEntryFilter();
$filter->statusEqual = KalturaEntryStatus::READY;
$result = $client->baseEntry->listAction($filter, $pager);
If you run this code and add:
You will get a result very similar to the XML outputted in the right frame of the page in the screenshot above.
The Test Me Console is a useful method of starting to work with the Kaltura API. Simply browse through available services and see what actions can be made.
Then, you can copy the code snippet and shape it into something useful within your scripts.
Hopefully this article will help you get started with the Kaltura APIs.
Browse the Kaltura API Documentation Set to learn more and explore more Kaltura APIs.
For any questions, leave a comment below, or start a thread in the forums.
Join us for the upcoming Video Experience Hackathon on June 13-5 in NYC. Polish your Kaltura API skills with the mentoring of experts and Kaltura core maintainers, and take a chance at winning the $50,000 prize!
The installation of Kaltura, just like the platform itself, went through a lot of metamorphosis over the years.
Over the years, we invested many resources at making Kaltura the best media management platform. Featuring grand batch system, complex metadata engine, robust entitlements, simplified video transcoding and more.
Alas, built on many different technologies, the installation of the platform became a bit of a complex task. Requiring many pre-install steps and several tricky pit-falls, even for the expert Linux engineers.
Announcing “KIPP” – Kaltura’s Install Packages Project!
Putting in place the resources to simplify and standardize the installation of Kaltura.
To enable the use of standard Linux package managers (e.g. yum, aptitude) to deploy the Kaltura platform with ease.
It was important for us to create an open and collaborative project from day 1. Enabling community users to take part in defining, testing and developing the project.
Open repository and packaging tools -
All RPM and deb specs are accessible on an open GitHub repository.
Also available a chrooted ready-to-go build environment to allow experienced package developers to get started with ease and contribute packages for other CPU architectures or other operating systems.
Many dependancies, many challenges.
Kaltura requires many 3rd party components. Some of which are available via official Linux repositories. Many are in different versions or compilation options than what Kaltura requires. And other are missing altogether from official repositories.
Most packages are available from supplementary repositories such as EPEL and RPMForge. But, relying on unofficial repositories would force a list of pre-install steps that KIPP was set to avoid. And it would also introduce the challenge of keeping up with updates from these repositories.
Clean & Simple!
To meet our simplicity goal, we’ve chosen a few project guidelines.
All packages will have the ‘kaltura-’ prefix.
This ensures a no-conflict with other packages the machine may already have installed.
It would also provide a simple approach to handling updates -
# yum update "*kaltura*"
All files go under
Apart from standard init scripts:
/etc/init.d and symlinks to Apache and logroate configurations. If the user runs the un-install script – everything gets removed.
Release notes matter.
Every package contains project metadata, that includes the project’s github repository and changes log. The changes-log contain all changes or patches for each version as well as links to Knowledge Center release notes.
Simple single-server without compromising cluster installs.
A single call to the ‘kaltura-server’ meta-package will install a complete all-in-one Kaltura server. But, as you grow your usage, so should your network grow into a smarter cluster of dedicated servers.
Modular packages structure.
A key characteristic of Kaltura is its ability to scale and deploy across any size cluster. The install packages should allow for the same level of modularity in deployment:
- You only install what you need.
- You should always know exactly what you have installed and of which version.
- You should have full control over which parts to update or patch.
- You should deploy packages based on desired server-role by calling its role. E.g. front, batch, sphinx, DB, etc.
Automated, silent installs.
Repurposing and adding new servers in your network should be a painless and automatic task.
Post-install script for each server role, allows for an easy deploy or repurpose of Kaltura servers.
Utilizing answers-file, preconfigured server-role templates allow for automatic deployment of new servers.
Admins can use Chef scripts with preconfigured answers-file to deploy complete clusters with ease.
Building for today, designing for long-term.
The short-term goal is to solve deployment of Kaltura on Fedora and Debian based Linux systems. Utilizing simple shell post-install scripts we maintain a common code base whenever possible. That allows for reuse in future packages, reducing time to package for other systems such BSD variants or even OSX.
Also, if we add new directives or variables in the future, all we need to update is the answer file template.
Support the project:
- Kaltura Admins – Follow the new install guide (http://bit.ly/kipp-rpm). Help test the installation and upgrade flows.
- Packagers / Package Developers – If you’re experienced with Linux packaging (or brew/macports on OSX) drop us a line!
- Tech writers, translators and anyone who cares – Let’s reach everyone who cares about online video, anywhere!
To stay updated and learn more, visit the project page!
This is a guest blog post written by Shannon K. Murphy. Shannon is the Content Marketing Manager for 3Play Media, an online video captioning and transcription service located in Cambridge, MA. Prior to 3Play Media, Shannon worked as a Marketing Consultant at HubSpot and Dow Jones Local Media. Shannon has been passionate about SEO, inbound marketing and content creation since 2008.
Video is the gateway to a conversation with your next customer. This brilliant content medium appeals to internet audiences because it utilizes both auditory and visual senses, translating into higher engagement and a quicker recall. According to Forbes, 50 percent of executives look for more information after seeing a product or service in a video. The growing popularity of animated “explainer videos” exemplify how audiences desire dynamic videos paired with easy-to-remember text and facts. While video messages are becoming more refined, this is only one aspect of video marketing. How to get these videos discovered? Again, a powerhouse combination of text and video. Transcripts vastly improve the chance of discoverability and lift your video SEO strategy.
Why Video Transcripts Boost SEO
It’s no secret that search engines love video. Depending on the keywords entered into a search query, Google may automatically produce video search results. For example, the words “how to” will often generate search results with videos demonstrations. Google rewards video content in blended results because video is often more time consuming to produce, post, and curate.
While Google attempts to select the most appropriate media format for our searches, video search technology is still lacking. This is where words still have their place. Because the success of SEO hinges on keywords and text queries, video transcripts add valuable spoken content to your site, furthering your site’s presence with search engines.
Because search bots cannot “watch” a video, they rely on limited text information like video tags and meta-descriptions to understand the content and context of videos. As described in the video below, publishing a video on your site with only a heading and short summary paragraph is akin to a newspaper article missing the most important part—the story! A transcript allows search engines to understand video on a deeper level and index it appropriately.
More Ways Video Transcripts Amplify SEO
Keyword Strategy/Keyword Density: Video SEO best practices call for one video per page, each with a unique title, header and tags. Transcripts can aid in discovering the most desirable and relevant keyword phrasings, but also add to overall keyword density. Unlike “keyword stuffing,” placing a transcript on your video landing page is a way to integrate a keyword phrase into a site, naturally.
Content Marketing: In 2012, more than 90 percent of marketers utilized video for content marketing. Video transcripts assist in the development of additional content pieces. After a video is transcribed, that text file can be used to create blog articles, whitepapers, slide share presentations, and support documentation.
Mobile Consumption: Captioned video is accessible anywhere and everywhere. Video is expected to make up two-thirds of mobile consumption by 2017.
Additional Benefits of Online Video Captions and Transcripts
Video captions and transcripts provide the flexibility necessary when audiences need to consume video content in public places like the gym, cafe or subway.
UX: Video conveys information faster than almost any other medium. Even then, we can sometimes feel video is lagging behind our own pace. A 3 minute video can feel like 15 minutes when paired with a slow-paced narrator. If users can’t find an effective away to accelerate the pace or find the desired content another way, they will click away. The 3Play Media interactive transcript gives audiences back control. Users can scan search the spoken content of a video for keywords and then click through to any moment where that word was uttered. This feature can speed up the research and evaluation of products and services.
Global Branding: International websites are the first company ambassadors for potential customers oversees. Greet site visitors in their native language. Translating English transcripts and adding multilingual subtitles to Kaltura videos is an effective way to communicate globally. Furthermore, translation will enhance foreign language keyword tactics, augmenting site presence on search engines abroad.
Video SEO is a practice focused on delivering your video content to a well-targeted audience. Video transcripts assist in this process by adding to a site’s keyword relevance and perceived authority. Broaden the reach of a site by utilizing transcripts for video SEO as well as mobile, UX and global marketing strategies.
Article by Katie Drossos, reposted from the Blackboard blog
All faculty, whether they admit it or not, are faced with the challenge of keeping students locked into and focused on the lesson at hand. There’s nothing unique about this challenge – a study by Ralph Burns found that the impact of a lecture is greatest in its first five minutes—after that, learners’ attention wanes and the effectiveness of the lecture drops. You have probably sat through lectures yourself where, despite your best intentions, you became disengaged mid-way through.
This reality begs the question: How can you combat student disengagement with your classroom material? Take a look at the five tips below, based on how Vrije Universiteit (VU) tackled this challenge with video.
- Give Students Control. One way to increase student engagement is to have students influence what (and how) they learn. Rob Van Leeuwen, Educational Technologist at VU, offers, “We have a group of professors that are planning to use Kaltura, an open source online video platform that allows faculty and students to easily create, edit and upload videos, to have students assist with the creation of curriculum and become producers of class materials. In essence, the students will be in control of determining how they learn best.”
- Make it easy for faculty and students. Find a solution that will allow students and faculty to post videos with as few clicks as possible, and allows them to be viewed from any device in any location once uploaded.
- Train Your Users. Implementing new technology doesn’t mean anything unless faculty and students use the solution. At VU, the university’s library used an online video to demonstrate how to use the platform. They also added a FAQ page and allowed faculty to add their own questions.
- Look at the Analytics. To get the most out of your video solution, monitor usage on campus. This will allow you to highlight the power-users whom you can then tap as “video evangelists” or ask them to train other faculty. VU staff use the administrative tools within their solution to gain visibility into what is happening down to a granular level.
- Integrate your video solution with your LMS. Meet students where they are every day – in Blackboard Learn – and make it easier for them to access the myriad of solutions available to them without having to remember all the various URLs, usernames, and passwords. By choosing a solution that integrates seamlessly with your LMS, you can open up a new set of engaging teaching possibilities from integration of lecture capture and video materials to enabling video assignments and sharing of student-and faculty-contributed video content.
Hear more about VU’s experience using video as a more intuitive way to teach students. Join us for a live webinar on October 24th to hear firsthand from Rob Van Leeuwen about online video projects that have been deployed at VU.
You can watch the full episode on this post below, or at the official show episode page, where you can also subscribe to future shows and watch some of the awesome previously recorded shows. You can also review the episode notes on FLOSS Weekly Wiki – Episode 261.
If you don’t know FLOSS Weekly already, Randal’s lightning intro below explains it best. Randal does a fantastic job at bringing exciting and interesting Open Source projects to the online [Video] Radio show.
Short summary of what we chatted about (and you can read more at FLOSS Weekly Wiki – Episode 261) -
- What Kaltura is and why you should care.
- Cover history and future of the Kaltura project, from making video a first class citizen of the web to world domination!
- The recent move of the Kaltura Server repository from closed SVN to a fully open repository on GitHub.com/kaltura/server .
- Wikipedia + Kaltura and bringing video step closer to becoming as easy as text.
- How to get involved with the Kaltura project, fork and contribute.
- The upcoming Kaltura Connect 2013 conference that will take place on September 30 – October 1st in NYC.
To watch the full episode of FLOSS Weekly 261 – Kaltura, press play below, or visit the FLOSS Weekly episode page.
DRM (Digital Rights Management) is an important tool for premium and private content. The need for enforcing content license terms and for ensuring control over content monetization is of major concern when coming to provide an online media service that is available in an over-the-top / multi-platform environment. To help clients delivery to these multiple devices Kaltura has enhanced its native application developer tools ( SDKs ) for iOS and Android to support secured delivery.
Significant attention and effort must be invested to make sure that content is protected for preventing unauthorized content distribution and enforcing corporate and educational viewing licenses.
Kaltura provides multiple layers of content security: from a strictly secured infrastructure, through secured API sessions, a robust set of conditional access controls and multiple secured content delivery options. The addition of DRM technology to this security stack enables maximum protection of content by encrypting media assets, and by relying on a per-session license for playback. Playback is enabled only upon receiving this dedicated license which can be obtained only as part of a controlled environment through pre-defined rules.
Kaltura’s video platform is integrated today with Google Widevine’s DRM technology for content protection and with a near-term plan to enable a multi-DRM service as part of its video platform.
Kaltura’s integrated DRM service enables:
- Media Encryption as an integral part of the content ingestion process.
- License protected playback flow from multiple devices.
- Integrating with standard policy setting, license issuing flows and client-side protections provided by the DRM technology provider.
- Utilizing Kaltura’s Access Controls as an out-of-the-box authorization system integrated within the DRM license issuing flow.
- Enabling service-specific business logic for authorizing user/content entitlements as part of the DRM license issuing flow through Kaltura Access Control’s authorized session (KS) validation.
- Integrated Content Management – Encrypted content is seamlessly managed along-side with non-encrypted content from the same KMC account.
More details on Kaltura’s integrated service for DRM with Google Widevine are provided in this article on Kaltura’s Knowledge Center
In addition to the out-of-the-box support for DRM protected playback in PC environments using flash and the widevine extension, Kaltura recently introduced DRM support to its mobile reference applications and SDKs. These enhancements enable developers to secure content in the iOS and Android platforms. These tools have been integrated with the kaltura reference apps for easy integration into your native app projects. Here Eliza and Josh share how to get DRM up and running for iOS.
In 2011, the social medium of images was the new hot thing with Instagram established and Snapchat in its infant stages. Despite the popularity of these apps, many people were still wondering: what’s next?
Fast forward two years, with the world experiencing Vine-fever and the recent launch of Instagram Video, video, now more than ever, is king. But what is it that makes apps like Vine so popular? Can a six second video truly be a work of art or is it just a reflection of our generation’s shortened attention spans? Perhaps, just like mainstream media, it is a bit of both. As Vine becomes decreasingly recognized as just another internet gimmick, it evolves into a form of expression that greatly mimics traditional media (or, perhaps, it is also the other way around). Consequently, Vine, like digital media in general, has started occupying six different realms of mainstream media.
1. Vine Awards at Film Festivals
Yes, Vines are being awarded at film festivals. The Tribeca Film Festival, cofounded by Robert Deniro, created #6SecondFilms to honor Vines. Seriously, what more artistic validation could Vines need than that from the Godfather himself. The Vines were separated into four categories: genre, series, animate, and auteur (Described as “[Vines that]told a story or script that was truly unique. A tiny, concentrated expression of the filmaker’s vision”) and were judged by an esteemed panel that included the King himself, Goldberg.
Here is this year’s winner in the “auteur” category titled “There is No Sunny Side to this Story”:
2. Celebrity Stars
Just like Twitter and Facebook, celebrities from Tyra Banks to Terminator have adopted Vine. However, what differentiates Vine from the other social media platforms is that celebrities have adopted it as a way to express art. Sure, there are some stars that prefer to just shoot a six second clip of whatever they are currently doing or an inane video that has little substance, but there is a large number of them, like Goldberg, that actually use Vine to tell stories. These artists see Vine as a challenge. They recognize what Vine truly is (or can really be): the haiku of digital media. Like a haiku, a Vine is simple, short and restricted, yet, paradoxically complicated, beautiful, and free for those same reasons. Take a look at one of Goldberg’s Vines, “Latency.”
3. Instructional Promotions
We’ve recently covered the use cases instructional videos and Vine provides another unique method. Companies are using Vine to promote their products while giving nifty tips. Lowe’s has launched their “#lowesfixinsix” campaign that illustrates simple life hacks. Lowe’s has achieved a marketer’s dream by compressing incredibly useful information into one absurdly brief, yet engaging clip. For example, you can learn how to prep your grill for the summer in six quick seconds.
The vast majority of companies that use social media do it for promotional purposes. However, one of the main concerns with publishing video is making sure that your content is engaging. Companies do not want to invest a substantial amount of money into an advertisement and see that viewers are tuning out. Vine, similarly to twitter, solves this problem by accepting our attention spans for what they are: weak. Many companies, like Microsoft, have gotten creative and found ways to use Vine to create short yet informative content. Take a look at this episode from Microsoft’s Internet Explorer advertisement campaign “Not Your Father’s Browser” for IE 10.
Now, much more than ever, we are linked to the news in an almost inescapable fashion. Twitter has helped revolutionize modern journalism by providing instantaneous coverage of events around the world. Any action, catastrophe, election result is immediately uploaded to our feeds. Vine, similarly, provides the swift impact of twitter but also allows the viewer to survey what’s happening. The most famous example of Vine broadcast journalism was done by the Turkish Pulse, who captured the immediate aftermath of the tragic bombing of the U.S. embassy in Turkey. The Vine not only provides the viewer with the information of what happened (that there was a bombing at the U.S. Embassy in Turkey) but also gives the user a sense of the moment, similarly to traditional news coverage.
Vine is still in its early stages with broadcasting sports entertainment. Due to the legal ramifications of distributing content that is protected and owned by various leagues, there are not any Vines of actual games or matches. This is extremely unfortunate because Vine would be the perfect medium to relay a thunderous dunk, game winning goal, last-second touchdown, or any important athletic play. However, there have been some breeches into the sports industry with Vines capturing pre-game warm-ups. Look at this one from the Brooklyn Nets.
Vine is often dubbed as the “Twitter of video”, which is not far from the truth (Vine is even owned by Twitter). However, the impact of Vine can be so much more. With a 140 character limit, Twitter, like Vine, limits its users. But if a picture is truly worth a thousand words, then at 30 frames per second, Vine is worth at least 180,000 of them.