<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I'm not sure, but here are some guesses:<br>
<br>
1. Broadcasters send their signals to the ether and they do not know
who is actually watching. Thus, services like Nielsen figure this out
and sell their results. With the internet, publishers know who is
viewing each file and can gather marketing data on viewers. This is
valuable data which they want to maximize.<br>
<br>
2. Early experiences with digital media being pirated on the internet
created a big challenge for the content publisher's revenues. It's
very easy for just about anyone to set up a web site to share
bootlegged files compared to setting up a pirate broadcasting station.
The FCC takes a very dim view of pirate broadcasting stations, so there
are relatively few pirate broadcasting stations and they do not present
a problem for content publishers.<br>
<br>
3. Most (all?) modern consumer DVRs are essentially controlled by the
cable or media companies, so they still control our experience and can
gather viewer data. (I've not built a mythTV set yet although it might
be one of my projects for the year).<br>
<br>
My $0.02.<br>
<br>
Steve<br>
<br>
Angelo McComis wrote:
<blockquote cite="mid:7241477096900959305@unknownmsgid" type="cite">
<pre wrap="">This almost seems to raise a consumer rights question: if you send
something to my machine, do I have the right to save it to retrieve it
later? Do I have the right to decode and leave the content viewable
later? At what point do you draw the line here?
We DVR broadcast and cable content. Why do Internet types try to make
online content so much more difficult to do the equivalent with?
- Angelo
On Jan 9, 2011, at 5:56 PM, William Yang <a class="moz-txt-link-rfc2396E" href="mailto:wyang@gcfn.net"><wyang@gcfn.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Sat, 2011-01-08 at 18:25 -0500, Matt Meinwald wrote:
</pre>
<blockquote type="cite">
<pre wrap="">My guess is it is not on the hard drive at all. I have seen flash store regular
videos in /tmp. In more recent versions they seem to be deleting this file
immediately after creating it, but it is still accessible somewhere in
/proc/<PID>/fd/.
</pre>
</blockquote>
<pre wrap="">That's a secure coding technique to prevent data leakage.
... stuff deleted
</pre>
</blockquote>
<pre wrap=""><!---->_______________________________________________
colug-432 mailing list
<a class="moz-txt-link-abbreviated" href="mailto:colug-432@colug.net">colug-432@colug.net</a>
<a class="moz-txt-link-freetext" href="http://lists.colug.net/mailman/listinfo/colug-432">http://lists.colug.net/mailman/listinfo/colug-432</a>
</pre>
</blockquote>
</body>
</html>