public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Brent Harding <bharding@doorpi.net>
To: blinux-list@redhat.com
Subject: Re: Digital Talking Book Standard
Date: Mon, 19 Nov 2001 11:06:39 -0600	[thread overview]
Message-ID: <3.0.6.32.20011119110639.00a9f100@mail.doorpi.net> (raw)
In-Reply-To: <200111191500.fAJF0Qa69940@dc.cis.okstate.edu>

I don't think the drm will work in the long run. It has to be proprietary
to not allow hacking, anyone who has the source code can hack a program to
undo what the original did. I heard some of the stronger drm's out
interfere with screen reader use, meaning we're stepping backwards in
accessibility, as we'd have to have sighted help to read a book we once
could get in speech on the computer because of this technology, and the way
screen readers access the system.
At 09:00 AM 11/19/01 -0600, you wrote:
>	I certainly hope that players for DTB's will be available
>for Linux when the technology actually begins to bear fruit.
>
>	This truly is a wonderful next step in the Talking Book
>program. Just think of the logistical problems of moving and
>caring for physical materials that this solves.  There will still
>need to be traditional Talking Books for many years to come, but
>I think this is the future and it may get to a point where there
>won't need to be as many physical recordings produced as there
>are now.
>
>	The one thing I see as holding things up is the one
>artificial technical issue and that is DRM or Digital Rights
>Management.
>
>	How is that going to be accomplished?  The standards
>document simply says that digital rights management will be
>supported but probably wisely does not prescribe exactly what
>sort of mechanism will be used.
>
>	Hopefully, being eligible to receive traditional Talking
>Books and Braille materials will enable one to also receive any
>DTB's they are entitled to receive.
>
>	In the main-stream consumer world, digital rights
>management has not been doing too well.  Some systems are hacked
>almost before they are released.  Other systems tend to do the
>opposite and malfunction in ways their developers never thought
>of to cause honest users of the technology to be denied service.
>
>	Some rights management systems have even gained the
>distinction of suffering from both maladies.  The crackers
>de fang the protection and the honest users discover that the
>software thinks they are thieves because of something their
>equipment or they accidentally did.
>
>	This issue, not technology, has held up everything from
>digital audio tape a decade or so ago to present-day high-definition
>television systems.
>
>	Linux and FreeBSD should actually be good test beds for
>this technology because it is based on open-source models and any
>hanky panky mechanisms such as back doors or scripting
>applications are a little easier to police than they are in
>proprietary operating systems.
>
>Martin McCormick WB5AGZ  Stillwater, OK 
>OSU Center for Computing and Information Services Network Operations Group
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>




  parent reply	other threads:[~ UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Martin G. McCormick
 ` Saqib Shaikh
   ` Peter Toneby
     ` Janina Sajka
       ` Peter Toneby
         ` Nicolas Pitre
           ` Peter Toneby
             ` Lloyd G. Rasmussen
             ` Nicolas Pitre
     ` Nicolas Pitre
       ` Peter Toneby
       ` Janina Sajka
         ` Nicolas Pitre
           ` Janina Sajka
             ` Nicolas Pitre
           ` Brent Harding
             ` Nicolas Pitre
     [not found]           ` <Pine.LNX.4.33.0111191409370.3206-100000@toccata.grg.afb.ne t>
             ` Brent Harding
     [not found]       ` <Pine.LNX.4.33.0111191147560.2815-100000@toccata.grg.afb.ne t>
         ` Brent Harding
           ` Nicolas Pitre
             ` Joel Zimba
               ` Brent Harding
             ` Brent Harding
               ` Nicolas Pitre
   ` philwh
 ` Janina Sajka
 ` Brent Harding [this message]
   ` Buddy Brannan
     ` Brent Harding
     [not found] ` <Pine.LNX.4.33.0111191114500.2815-100000@toccata.grg.afb.ne t>
   ` Brent Harding
     ` Luke Davis
       ` cbowman
         ` ssh A. R. Vener
           ` ssh cbowman
           ` ssh Luke Davis
             ` ssh Andor Demarteau
               ` ssh Luke Davis
               ` ssh Fredrik Larsson
                 ` ssh Luke Davis
                   ` ssh Fredrik Larsson
             ` ssh cbowman
               ` ssh A. R. Vener
             ` ssh A. R. Vener
               ` ssh Luke Davis
         ` Digital Talking Book Standard Brent Harding
           ` cbowman
         ` Luke Davis
           ` cbowman
       ` Janina Sajka
     ` Pratik Patel
       ` Brent Harding
  -- strict thread matches above, loose matches on Subject: below --
 Janina Sajka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3.0.6.32.20011119110639.00a9f100@mail.doorpi.net \
    --to=bharding@doorpi.net \
    --cc=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).