Re: good reason to not read emails from this list, was...Re: Fw: youtube video, jaws versus NVDA

  • From: Alex Midence <alex.midence@xxxxxxxxx>
  • To: programmingblind@xxxxxxxxxxxxx
  • Date: Fri, 15 Oct 2010 04:43:44 -0500

David,

Please calm yourself.  I assure you that my intention was not to crash
your screen reader if you did not want it crashed.  This is a list of
programmers.  We were discussing an odd bug.  Several messages prior
to  mine talked about it.  My first message actually warned people on
this list about the fact that someone else had put this word in a
comment on the video in youtube and didn't warn others that it would
crash their Jaws.  It crashed mine. I found out the hard way and
figured out what had happened only when I brought up NVDA and read the
page for myself.  I then said, hmm, maybe I'd better warn the listers
that this person did this so they don't fall into the same trap I did.
 I went so far as the separate the word in dashes the first time.
This was so that, programmers that we are, everyone could see what I
was talking about in a controled, deliberate manner and see for
themselves if the bug would cause their synthesizer to crash.  This
would also appear on google, actuallly.  Naturally, programmers that
we are, someone tried it and didn't get the same result.  This is the
sort of thing that intrigues people who code.  Why did it happen for
you and not for me?  Hmmh, hum, you think.  Maybe you typed it wrong,
someone said.  There followed the sort of discussion one naturally
assumes would ensue from this point.  Eventually, inevitably, someone
would have posted the word in its hideous nakedness; sans dashes;
utterly exposed for all to swear at.  I figured that if this was to be
the case, I'd better do it since I brought it up.  But, I would do it
in such a way as to let people know what was coming.  When I wrote the
second message which caused your reaction, I warned everyone I was
about to type the word.  I then put in a blank line or two to pause
your speech for you since this usually causes eloquence to pause for
a tiny bit.   I then put a bunch of equal signs and yet another blank
line before the word.  All of this was so that you would have time to
hit your control key to silence speech.  I am working under the
impression that you, (and when I write you here, I'm talking in
generalities and not about you personally, David), that you, I say,
are exercising some caution after reading posts on a list that talk
about something that crashes jaws.  "surely," I thought, "noone is
going to have their speech going a hundred miles a minute while they
are reclining in their chair drinking a martini and munching on potato
chips after hearing that there's a word out there that crashes Jaws
when encountered.  Someone might post the word."  Now then, please
explain to me how taking the precautions I did was irresponsible or
inconsiderate?

If your Jaws crashed when you did not want it to while reading my
message, I am truly sorry.  It was not my intention for this to happen
to anyone.  I do, however, take issue with you if you think that I
posted this word in an irresponsible manner.  Short of putting it in
an attachment labled:  "Danger will Robinson.txt", I am quite at a
loss for how I might have handled this otherwise.

Thanks.
Alex M

On 10/15/10, prateek aggarwal <prateekagarwal99@xxxxxxxxx> wrote:
> just an advice:
> please make adjustments in your jaws dictionary manager against this
> bugging word, and change the pronunciation to something else.
>
> it works that way, and won't stop next time it will encounter  the word.
>
>
> cheers!
> prateek agarwal.
>
>
>
> On 10/15/10, David Engebretson Jr. <d.engebretson@xxxxxxxxxxx> wrote:
>> Ha!  I've limited my reading to very few lists since I've become a parent.
>> And I've set up quick keystrokes to restart my screen readers that I use,
>> that's not the issue.  It's not about me, it's about the community at
>> large.
>>
>> The issue is that it is irresponsible for us to pass on the flagrant
>> passing
>> of the offending words over public lists.  Especially those lists designed
>> to help people.  I realize there are communities where this might be
>> condoned.  It doesn't seem an appropriate place to condone such here where
>> we try and help eachother learn.
>>
>> Personally I think the name of this list obviates the need for further
>> discussion.  We are here as people who want to learn about programming,
>> and
>> we are blind.  It doesn't matter which screen reader we use, we should not
>> disrupt the workflow of people who are blind programmers; it should be a
>> credo of this list.
>>
>> Funny audio/video/text clips are by no means a problem with me but the
>> thing
>> is that i am only one member in this community.  i speak for myself and
>> maybe others that it is obtrusive to have your workflow interrupted by
>> flagrant passing of words onto public lists that people might be reading
>> with screen readers that might crash.  hence, prepare all future screen
>> reader users to not have their messages automatically read to them as they
>> proceed through their day.
>>
>> I've got a lot more to say about this because I think it is silly that
>> there
>> needs to be so much discussion on a programming list, but i'll just sit
>> back
>> now and delete this thread until the threat is gone.
>>
>> Wake up people.  Find peace within yourself so you can give it to others.
>>
>> No need to pass what is basically a virus to your fellow folk.
>>
>>
>> ----- Original Message -----
>> From: "Johannes Grib" <johannesg@xxxxxxxxx>
>> To: <programmingblind@xxxxxxxxxxxxx>
>> Sent: Thursday, October 14, 2010 9:56 PM
>> Subject: RE: good reason to not read emails from this list, was...Re: Fw:
>> youtube video, jaws versus NVDA
>>
>>
>> Why not log a complaint with your screen reader manufacturer, are you
>> going
>> to complain on all publick lists with words your screen reader cannot
>> handle?  What about dictionaries and books, will the authors get it too?
>>
>> For your education, perhaps start keeping a backup screen reader like
>> NVDA,
>> every time jaws crash you can just hit alt+ctrl+n and you have speech
>> again!
>> You can close the error messages and restart your jaws.
>>
>> HTH
>>
>>
>> -----Original Message-----
>> From: programmingblind-bounce@xxxxxxxxxxxxx
>> [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of David
>> Engebretson Jr.
>> Sent: Friday, October 15, 2010 6:44 AM
>> To: programmingblind@xxxxxxxxxxxxx
>> Subject: good reason to not read emails from this list, was...Re: Fw:
>> youtube video, jaws versus NVDA
>>
>> You know, I've enjoyed emails from this list for a lot of years.
>> Sometimes
>> the enjoyment has been more educational than others.  Sometimes the
>> education has been painful due to lots of brain stretching and patience.
>>
>> Placing words in email messages that go to public lists that will crash
>> peoples screen readers is almost blasphemous to me after all of these
>> years.
>>
>> Please respect other peoples time and do not place such strings in these
>> listservs that may someday become public to all (wait, are these lists
>> googlefied?  do they have the google bot that makes all of these messages
>> public to everyone?). Either way, I'm sure we all have much better things
>> to
>> do than reboot our screen readers.
>>
>> If you enjoy disrupting peoples workflow, do it on a list that isn't
>> designed for "helping" people, please.
>>
>> __________
>> View the list's information and change your settings at
>> //www.freelists.org/list/programmingblind
>>
>> __________
>> View the list's information and change your settings at
>> //www.freelists.org/list/programmingblind
>>
>>
>>
>> --------------------------------------------------------------------------------
>>
>>
>>
>>
>> Checked by AVG - www.avg.com
>> Version: 8.5.448 / Virus Database: 271.1.1/3197 - Release Date: 10/14/10
>> 18:34:00
>>
>> __________
>> View the list's information and change your settings at
>> //www.freelists.org/list/programmingblind
>>
>>
> __________
> View the list's information and change your settings at
> //www.freelists.org/list/programmingblind
>
>
__________
View the list's information and change your settings at 
//www.freelists.org/list/programmingblind

Other related posts:

  1. Home
  2. programmingblind
  3. Archive
  4. 10-2010