<br><br><div class="gmail_quote">On Tue, Aug 28, 2012 at 3:30 PM, <span dir="ltr"><<a href="mailto:slackdocs-request@alienbase.nl" target="_blank">slackdocs-request@alienbase.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Send Slackdocs mailing list submissions to<br>
<a href="mailto:slackdocs@alienbase.nl">slackdocs@alienbase.nl</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.alienbase.nl/mailman/listinfo/slackdocs" target="_blank">http://lists.alienbase.nl/mailman/listinfo/slackdocs</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:slackdocs-request@alienbase.nl">slackdocs-request@alienbase.nl</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:slackdocs-owner@alienbase.nl">slackdocs-owner@alienbase.nl</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Slackdocs digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: images slackware:install (Gerardo Zamudio)<br>
2. fr:slackware:xfce need re-read (asteroid)<br>
3. fr:slackware:desktop_environment need re-read (asteroid)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 27 Aug 2012 18:32:37 -0500<br>
From: Gerardo Zamudio <<a href="mailto:gerardo@gerardozamudio.net">gerardo@gerardozamudio.net</a>><br>
To: Eric Hameleers <<a href="mailto:eric.hameleers@alienbase.nl">eric.hameleers@alienbase.nl</a>><br>
Cc: <a href="mailto:slackdocs@alienbase.nl">slackdocs@alienbase.nl</a><br>
Subject: Re: [Slackdocs] images slackware:install<br>
Message-ID:<br>
<<a href="mailto:CAJwL4y_U0qF1eKmLFku9dBkcaAo%2Bk-uBGXPEEXRyEyiUtdg8LQ@mail.gmail.com">CAJwL4y_U0qF1eKmLFku9dBkcaAo+k-uBGXPEEXRyEyiUtdg8LQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
On Mon, Aug 27, 2012 at 6:08 PM, Eric Hameleers <<a href="mailto:eric.hameleers@alienbase.nl">eric.hameleers@alienbase.nl</a><br>
> wrote:<br>
<br>
> On 08/27/2012 08:42 PM, Gerardo Zamudio wrote:<br>
> > On Mon, Aug 27, 2012 at 10:51 AM, Nocturnal Slacker<br>
> > <<a href="mailto:nocturnal.slacker@hotmail.com">nocturnal.slacker@hotmail.com</a> <mailto:<a href="mailto:nocturnal.slacker@hotmail.com">nocturnal.slacker@hotmail.com</a>>><br>
> > wrote:<br>
> ><br>
> > Yes. I agree that this would be a better way to utilize video on<br>
> > this site. We're not here to make money and provide free tracking<br>
> > data for Google (Youtube). We should probably avoid Flash, anyway. ;)<br>
> ><br>
> > ~V. T. Eric Layton, Nocturnal Slacker<br>
> ><br>
> ><br>
> > I do agree with not using Flash. .mkv or another container is fine<br>
> > with me. The reason I lightly suggested YouTube was for hosting. I<br>
> > don't know if Eric's server will be able to serve video (resources and<br>
> > bandwidth costs) but if it is then I see no problem with hosting it on<br>
> > <a href="http://docs.slackware.com" target="_blank">docs.slackware.com</a> <<a href="http://docs.slackware.com" target="_blank">http://docs.slackware.com</a>>.<br>
> ><br>
> My searver will not be able to host and stream video's. That is a whole<br>
> different category of bandwidth demand.<br>
> The wiki has a video plugin which understands many of the common video<br>
> hosting sites such as (but not limited to) Youtube and Vimeo. See<br>
> <a href="http://docs.slackware.com/wiki:user:alienbob" target="_blank">http://docs.slackware.com/wiki:user:alienbob</a> for an example of embedded<br>
> Youtube video.<br>
><br>
> Eric<br>
> _______________________________________________<br>
> Slackdocs mailing list<br>
> <a href="mailto:Slackdocs@alienbase.nl">Slackdocs@alienbase.nl</a><br>
> <a href="http://lists.alienbase.nl/mailman/listinfo/slackdocs" target="_blank">http://lists.alienbase.nl/mailman/listinfo/slackdocs</a><br>
><br>
<br>
Since some have voiced concerns with Flash, we can record video in WebM<br>
(supported by Chrome, Firefox, and Opera) and use the YouTube HTML5 player.<br>
<br>
We still need to figure out how translations will be handled. Here are some<br>
options that come to mind:<br>
<br>
1. Each translator records their own video (time consuming)<br>
2. Each video has different audio streams, you merely select which audio<br>
you want to use through the player. (most desirable option)<br>
3. YouTube supports captions, so each translator can just add new captions<br>
to each video. (simplest and quickest option)<br>
3. Each video has different versions uploaded. Same content but different<br>
narration (harder to keep track of videos)<br>
<br>
What are your thoughts?<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.alienbase.nl/pipermail/slackdocs/attachments/20120827/d5ef6a0b/attachment-0001.html" target="_blank">http://lists.alienbase.nl/pipermail/slackdocs/attachments/20120827/d5ef6a0b/attachment-0001.html</a>><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
End of Slackdocs Digest, Vol 1, Issue 30<br>
****************************************<br></blockquote><div>Instead of hosting videos in the site itself, why not made them as just files. The user can download the video file [using wget, no need to open the browser itself, there by avoiding more of flashing ads and saving bandwidth ] , and play it in their own/favorite players. No need to worry about flash and all. The user also , no need to install any plug-ins to download the video, in case they want. And they can watch anywhere, anytime with out worrying about the Internet availability. <br>
</div></div><br>