Friam

Just sent this to the Google Device Support Team

Classic

List

Threaded

15 messages Options

Douglas Roberts-2

Just sent this to the Google Device Support Team

Hi, Google Device Support Team.

It's been a while since we spoke, but I recently discovered that someone in your organization has been (I hope inadvertently) disseminating inaccurate information about this Nexus 4 bug, and I thought you'd want to know about it right away.

Here's the deal: you see, we all know that the Nexus 4 was not designed on purpose to prevent wifi and bluetooth from being used at the same time. We all know that it is a bug. Well, all of us except for Steve, apparently. Here, read for yourselves:

http://things-linux.blogspot.com/2013/03/translated.html

Now, we all have the utmost confidence that someone in your organization will immediately take Steve aside for a private little counselling session about the inappropriateness of, shall we say, bending the truth regarding this particular flaw in the Nexus 4 product.

Thanks for your prompt attention to this matter.

Best,

--Doug

Doug Roberts
[hidden email]

http://parrot-farm.net/Second-Cousins

505-455-7333 - Office
505-672-8213 - Mobile

============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com

Nick Thompson

Re: Just sent this to the Google Device Support Team

Now you all know, that, ever since Owen first used the word “top bit” in my presence, nearly a decade ago, I have followed, with rapt attention, the use of language on this list. So, you guys. I need to understand this better. Can a “bug” be “on purpose”? It sounds to me like Google has sabotaged its own product, right. Therefore, if I understand the language, any Nexus phone thatactually worked, would be “buggy”., by definition. I am sorry to bother you about this, but these are the kinds of things that keep me awake at night. N

From: Friam [mailto:[hidden email]] On Behalf Of Douglas Roberts
Sent: Sunday, March 24, 2013 1:44 PM
To: The Friday Morning Applied Complexity Coffee Group
Subject: [FRIAM] Just sent this to the Google Device Support Team

Hi, Google Device Support Team.

http://things-linux.blogspot.com/2013/03/translated.html

Thanks for your prompt attention to this matter.

Best,

--Doug

Doug Roberts
[hidden email]

http://parrot-farm.net/Second-Cousins

505-455-7333 - Office
505-672-8213 - Mobile

Douglas Roberts-2

Re: Just sent this to the Google Device Support Team

Nick's counselling session will be scheduled shortly...

--Doug (Who can tell when his chain is being yanked.)

On Sun, Mar 24, 2013 at 2:53 PM, Nicholas Thompson <[hidden email]> wrote:

Now you all know, that, ever since Owen first used the word “top bit” in my presence, nearly a decade ago, I have followed, with rapt attention, the use of language on this list. So, you guys. I need to understand this better. Can a “bug” be “on purpose”? It sounds to me like Google has sabotaged its own product, right. Therefore, if I understand the language, any Nexus phone thatactually worked, would be “buggy”., by definition. I am sorry to bother you about this, but these are the kinds of things that keep me awake at night. N

From: Friam [mailto:[hidden email]] On Behalf Of Douglas Roberts
Sent: Sunday, March 24, 2013 1:44 PM
To: The Friday Morning Applied Complexity Coffee Group
Subject: [FRIAM] Just sent this to the Google Device Support Team

Hi, Google Device Support Team.

It's been a while since we spoke, but I recently discovered that someone in your organization has been (I hope inadvertently) disseminating inaccurate information about this Nexus 4 bug, and I thought you'd want to know about it right away.

Here's the deal: you see, we all know that the Nexus 4 was not designed on purpose to prevent wifi and bluetooth from being used at the same time. We all know that it is a bug. Well, all of us except for Steve, apparently. Here, read for yourselves:

http://things-linux.blogspot.com/2013/03/translated.html

Now, we all have the utmost confidence that someone in your organization will immediately take Steve aside for a private little counselling session about the inappropriateness of, shall we say, bending the truth regarding this particular flaw in the Nexus 4 product.

Thanks for your prompt attention to this matter.

Best,

--Doug

--
Doug Roberts
[hidden email]
http://parrot-farm.net/Second-Cousins

<a href="tel:505-455-7333" value="+15054557333" target="_blank">505-455-7333 - Office
<a href="tel:505-672-8213" value="+15056728213" target="_blank">505-672-8213 - Mobile

============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com

Doug Roberts
[hidden email]

http://parrot-farm.net/Second-Cousins

505-455-7333 - Office
505-672-8213 - Mobile

Joshua Thorp

Re: Just sent this to the Google Device Support Team

Also I doubt Owen ever said "top bit", I imagine it was probably "high-order bit"…

I like the question though, can a bug be on purpose. Seems like it would be in the eye of the beholder, one person's bug might be another's feature.

--joshua

On Mar 24, 2013, at 2:57 PM, Douglas Roberts <[hidden email]> wrote:

Nick's counselling session will be scheduled shortly...

--Doug (Who can tell when his chain is being yanked.)

On Sun, Mar 24, 2013 at 2:53 PM, Nicholas Thompson <[hidden email]> wrote:

Now you all know, that, ever since Owen first used the word “top bit” in my presence, nearly a decade ago, I have followed, with rapt attention, the use of language on this list. So, you guys. I need to understand this better. Can a “bug” be “on purpose”? It sounds to me like Google has sabotaged its own product, right. Therefore, if I understand the language, any Nexus phone thatactually worked, would be “buggy”., by definition. I am sorry to bother you about this, but these are the kinds of things that keep me awake at night. N

From: Friam [mailto:[hidden email]] On Behalf Of Douglas Roberts
Sent: Sunday, March 24, 2013 1:44 PM
To: The Friday Morning Applied Complexity Coffee Group
Subject: [FRIAM] Just sent this to the Google Device Support Team

Hi, Google Device Support Team.

It's been a while since we spoke, but I recently discovered that someone in your organization has been (I hope inadvertently) disseminating inaccurate information about this Nexus 4 bug, and I thought you'd want to know about it right away.

Here's the deal: you see, we all know that the Nexus 4 was not designed on purpose to prevent wifi and bluetooth from being used at the same time. We all know that it is a bug. Well, all of us except for Steve, apparently. Here, read for yourselves:

http://things-linux.blogspot.com/2013/03/translated.html

Now, we all have the utmost confidence that someone in your organization will immediately take Steve aside for a private little counselling session about the inappropriateness of, shall we say, bending the truth regarding this particular flaw in the Nexus 4 product.

Thanks for your prompt attention to this matter.

Best,

--Doug

--
Doug Roberts
[hidden email]
http://parrot-farm.net/Second-Cousins

<a href="tel:505-455-7333" value="+15054557333" target="_blank">505-455-7333 - Office
<a href="tel:505-672-8213" value="+15056728213" target="_blank">505-672-8213 - Mobile

============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com

--
Doug Roberts
[hidden email]
http://parrot-farm.net/Second-Cousins

505-455-7333 - Office
505-672-8213 - Mobile

============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com

Gillian Densmore

Re: Just sent this to the Google Device Support Team

In reply to this post by Nick Thompson

Well you see it depends on the kind of bug. During summer chirpy bugs are pleasant think the chirping bugs do so on purpose. :P

On Sun, Mar 24, 2013 at 2:53 PM, Nicholas Thompson <[hidden email]> wrote:

Now you all know, that, ever since Owen first used the word “top bit” in my presence, nearly a decade ago, I have followed, with rapt attention, the use of language on this list. So, you guys. I need to understand this better. Can a “bug” be “on purpose”? It sounds to me like Google has sabotaged its own product, right. Therefore, if I understand the language, any Nexus phone thatactually worked, would be “buggy”., by definition. I am sorry to bother you about this, but these are the kinds of things that keep me awake at night. N

From: Friam [mailto:[hidden email]] On Behalf Of Douglas Roberts
Sent: Sunday, March 24, 2013 1:44 PM
To: The Friday Morning Applied Complexity Coffee Group
Subject: [FRIAM] Just sent this to the Google Device Support Team

Hi, Google Device Support Team.

It's been a while since we spoke, but I recently discovered that someone in your organization has been (I hope inadvertently) disseminating inaccurate information about this Nexus 4 bug, and I thought you'd want to know about it right away.

Here's the deal: you see, we all know that the Nexus 4 was not designed on purpose to prevent wifi and bluetooth from being used at the same time. We all know that it is a bug. Well, all of us except for Steve, apparently. Here, read for yourselves:

http://things-linux.blogspot.com/2013/03/translated.html

Now, we all have the utmost confidence that someone in your organization will immediately take Steve aside for a private little counselling session about the inappropriateness of, shall we say, bending the truth regarding this particular flaw in the Nexus 4 product.

Thanks for your prompt attention to this matter.

Best,

--Doug

--
Doug Roberts
[hidden email]
http://parrot-farm.net/Second-Cousins

<a href="tel:505-455-7333" value="+15054557333" target="_blank">505-455-7333 - Office
<a href="tel:505-672-8213" value="+15056728213" target="_blank">505-672-8213 - Mobile

============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com

Tom Johnson

Re: Just sent this to the Google Device Support Team

In reply to this post by Douglas Roberts-2

Doug:

I have a Nexus S 4G from Sprint. FWIW, the Bluetooth audio does not work with the audio directions for the Google Navigator nor any other audio, e.g. listening to online radio.

-tom

On Sun, Mar 24, 2013 at 1:43 PM, Douglas Roberts <[hidden email]> wrote:

Hi, Google Device Support Team.

It's been a while since we spoke, but I recently discovered that someone in your organization has been (I hope inadvertently) disseminating inaccurate information about this Nexus 4 bug, and I thought you'd want to know about it right away.

Here's the deal: you see, we all know that the Nexus 4 was not designed on purpose to prevent wifi and bluetooth from being used at the same time. We all know that it is a bug. Well, all of us except for Steve, apparently. Here, read for yourselves:

http://things-linux.blogspot.com/2013/03/translated.html

Now, we all have the utmost confidence that someone in your organization will immediately take Steve aside for a private little counselling session about the inappropriateness of, shall we say, bending the truth regarding this particular flaw in the Nexus 4 product.

Thanks for your prompt attention to this matter.

Best,

--Doug

--
Doug Roberts
[hidden email]
http://parrot-farm.net/Second-Cousins

<a href="tel:505-455-7333" value="+15054557333" target="_blank">505-455-7333 - Office
<a href="tel:505-672-8213" value="+15056728213" target="_blank">505-672-8213 - Mobile

============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com

==========================================
J. T. Johnson
Institute for Analytic Journalism -- Santa Fe, NM USA
505.577.6482(c) 505.473.9646(h)
Twitter: jtjohnson

http://www.jtjohnson.com [hidden email]
==========================================

Robert J. Cordingley

Re: Just sent this to the Google Device Support Team

In reply to this post by Nick Thompson

Nick,

Here's my take on the language...

There are bugs that escape quality assurance and remain in a product when it is shipped. QA is not foolproof and as some wag said: 'You must ship your product (software) with bugs.' For anything but the smallest projects eliminating *all* bugs is usually seen as a pointless and hugely time consuming task. It's often a real combinatorial problem to completely test every possibility. A huge customer base is a more efficient way of finding them any way, so long as you keep the huge customer base in the process.

There are missing features that were never meant to be designed into the product in the first place. These can be captured and kept on wish lists for future releases. Some users may believe them to be bugs.

And then rarely, there are unexpected features that were discovered by the customer base that were never meant to be designed into the product. 'You found it could do what?'

From the engineering side no bug is on purpose - they are errors of omission not commission. How marketing/customer support puts their spin on it is another matter. Whether or not developers fix the customer identified bugs will probably be an economic decision or cost-benefit analysis using something like ($cost to fix C/no. customers affected N) - the lower the ratio the more likely action will be taken. I suspect for Google if N is close to 1 nothing will happen regardless.

What do others on the list think?

Thanks
Robert C

On 3/24/13 2:53 PM, Nicholas Thompson wrote:

Now you all know, that, ever since Owen first used the word “top bit” in my presence, nearly a decade ago, I have followed, with rapt attention, the use of language on this list. So, you guys. I need to understand this better. Can a “bug” be “on purpose”? It sounds to me like Google has sabotaged its own product, right. Therefore, if I understand the language, any Nexus phone thatactually worked, would be “buggy”., by definition. I am sorry to bother you about this, but these are the kinds of things that keep me awake at night. N

From: Friam [[hidden email]] On Behalf Of Douglas Roberts
Sent: Sunday, March 24, 2013 1:44 PM
To: The Friday Morning Applied Complexity Coffee Group
Subject: [FRIAM] Just sent this to the Google Device Support Team

Hi, Google Device Support Team.

It's been a while since we spoke, but I recently discovered that someone in your organization has been (I hope inadvertently) disseminating inaccurate information about this Nexus 4 bug, and I thought you'd want to know about it right away.

Here's the deal: you see, we all know that the Nexus 4 was not designed on purpose to prevent wifi and bluetooth from being used at the same time. We all know that it is a bug. Well, all of us except for Steve, apparently. Here, read for yourselves:

http://things-linux.blogspot.com/2013/03/translated.html

Now, we all have the utmost confidence that someone in your organization will immediately take Steve aside for a private little counselling session about the inappropriateness of, shall we say, bending the truth regarding this particular flaw in the Nexus 4 product.

Thanks for your prompt attention to this matter.

Best,

--Doug

--

Doug Roberts
[hidden email]

http://parrot-farm.net/Second-Cousins

505-455-7333 - Office
505-672-8213 - Mobile
============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com

Nick Thompson

Re: Just sent this to the Google Device Support Team

In reply to this post by Douglas Roberts-2

Doug,

No. No! Honest. No chains jerked. Promise. Just want to know how the language works. Remember, I am the guy who thinks that language and metaphor lie at the core of science (even tho I am also the guy who thinks that Rorty is a schmuck). I follow the blogs of noaa weather forecasters with the same intense interest. I may be nuts, but I don’t think I am devious.

My favorite term of art in weather forecasting is “least-regret forecast”, which explains why, if a forecaster makes a mistake early, that mistake tends to get compounded later because the “least-regret forecast” is the one that involves the fewest changes of mind. If you don’t change your original bad forecast, at least you have only been wrong once.

Nick

From: Friam [mailto:[hidden email]] On Behalf Of Douglas Roberts
Sent: Sunday, March 24, 2013 2:58 PM
To: The Friday Morning Applied Complexity Coffee Group
Subject: Re: [FRIAM] Just sent this to the Google Device Support Team

Nick's counselling session will be scheduled shortly...

--Doug (Who can tell when his chain is being yanked.)

On Sun, Mar 24, 2013 at 2:53 PM, Nicholas Thompson <[hidden email]> wrote:

Hi, Google Device Support Team.

http://things-linux.blogspot.com/2013/03/translated.html

Thanks for your prompt attention to this matter.

Best,

--Doug

Doug Roberts
[hidden email]

http://parrot-farm.net/Second-Cousins

<a href="tel:505-455-7333" target="_blank">505-455-7333 - Office
<a href="tel:505-672-8213" target="_blank">505-672-8213 - Mobile

Doug Roberts
[hidden email]

http://parrot-farm.net/Second-Cousins

505-455-7333 - Office
505-672-8213 - Mobile

Douglas Roberts-2

Re: Just sent this to the Google Device Support Team

Well in that case, Nick, it's pretty simple. Google fucked up either the radio design of the Nexus 4, or LG fucked up its manufacture, because you are supposed to be able to use wifi and bluetooth at the same time.

And you can't. On the Google Nexus 4. You can with other Android phones. But not with the Google Nexus 4. Google's Android. Google's phone. Broken.

--Doug

On Sun, Mar 24, 2013 at 6:07 PM, Nicholas Thompson <[hidden email]> wrote:

Doug,

No. No! Honest. No chains jerked. Promise. Just want to know how the language works. Remember, I am the guy who thinks that language and metaphor lie at the core of science (even tho I am also the guy who thinks that Rorty is a schmuck). I follow the blogs of noaa weather forecasters with the same intense interest. I may be nuts, but I don’t think I am devious.

My favorite term of art in weather forecasting is “least-regret forecast”, which explains why, if a forecaster makes a mistake early, that mistake tends to get compounded later because the “least-regret forecast” is the one that involves the fewest changes of mind. If you don’t change your original bad forecast, at least you have only been wrong once.

Nick

From: Friam [mailto:[hidden email]] On Behalf Of Douglas Roberts
Sent: Sunday, March 24, 2013 2:58 PM

To: The Friday Morning Applied Complexity Coffee Group
Subject: Re: [FRIAM] Just sent this to the Google Device Support Team

Nick's counselling session will be scheduled shortly...

--Doug (Who can tell when his chain is being yanked.)

On Sun, Mar 24, 2013 at 2:53 PM, Nicholas Thompson <[hidden email]> wrote:

Now you all know, that, ever since Owen first used the word “top bit” in my presence, nearly a decade ago, I have followed, with rapt attention, the use of language on this list. So, you guys. I need to understand this better. Can a “bug” be “on purpose”? It sounds to me like Google has sabotaged its own product, right. Therefore, if I understand the language, any Nexus phone thatactually worked, would be “buggy”., by definition. I am sorry to bother you about this, but these are the kinds of things that keep me awake at night. N

From: Friam [mailto:[hidden email]] On Behalf Of Douglas Roberts
Sent: Sunday, March 24, 2013 1:44 PM
To: The Friday Morning Applied Complexity Coffee Group
Subject: [FRIAM] Just sent this to the Google Device Support Team

Hi, Google Device Support Team.

It's been a while since we spoke, but I recently discovered that someone in your organization has been (I hope inadvertently) disseminating inaccurate information about this Nexus 4 bug, and I thought you'd want to know about it right away.

Here's the deal: you see, we all know that the Nexus 4 was not designed on purpose to prevent wifi and bluetooth from being used at the same time. We all know that it is a bug. Well, all of us except for Steve, apparently. Here, read for yourselves:

http://things-linux.blogspot.com/2013/03/translated.html

Now, we all have the utmost confidence that someone in your organization will immediately take Steve aside for a private little counselling session about the inappropriateness of, shall we say, bending the truth regarding this particular flaw in the Nexus 4 product.

Thanks for your prompt attention to this matter.

Best,

--Doug

--
Doug Roberts
[hidden email]
http://parrot-farm.net/Second-Cousins

<a href="tel:505-455-7333" target="_blank">505-455-7333 - Office
<a href="tel:505-672-8213" target="_blank">505-672-8213 - Mobile

============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com

--
Doug Roberts
[hidden email]

http://parrot-farm.net/Second-Cousins

<a href="tel:505-455-7333" value="+15054557333" target="_blank">505-455-7333 - Office
<a href="tel:505-672-8213" value="+15056728213" target="_blank">505-672-8213 - Mobile

============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com

Doug Roberts
[hidden email]

http://parrot-farm.net/Second-Cousins

505-455-7333 - Office
505-672-8213 - Mobile

Nick Thompson

Re: Just sent this to the Google Device Support Team

In reply to this post by Joshua Thorp

Joshua,

You are absolutely correct. “higher-order bit” it is. Even better. Can you imagine what a former English major’s imagination did with that?

From: Friam [mailto:[hidden email]] On Behalf Of Joshua Thorp
Sent: Sunday, March 24, 2013 3:01 PM
To: The Friday Morning Applied Complexity Coffee Group
Subject: Re: [FRIAM] Just sent this to the Google Device Support Team

Also I doubt Owen ever said "top bit", I imagine it was probably "high-order bit"…

I like the question though, can a bug be on purpose. Seems like it would be in the eye of the beholder, one person's bug might be another's feature.

--joshua

On Mar 24, 2013, at 2:57 PM, Douglas Roberts <[hidden email]> wrote:

Nick's counselling session will be scheduled shortly...

--Doug (Who can tell when his chain is being yanked.)

On Sun, Mar 24, 2013 at 2:53 PM, Nicholas Thompson <[hidden email]> wrote:

Hi, Google Device Support Team.

http://things-linux.blogspot.com/2013/03/translated.html

Thanks for your prompt attention to this matter.

Best,

--Doug

Doug Roberts
[hidden email]

http://parrot-farm.net/Second-Cousins

<a href="tel:505-455-7333" target="_blank">505-455-7333 - Office
<a href="tel:505-672-8213" target="_blank">505-672-8213 - Mobile

Doug Roberts
[hidden email]

http://parrot-farm.net/Second-Cousins

505-455-7333 - Office
505-672-8213 - Mobile

Owen Densmore

Re: Just sent this to the Google Device Support Team

Administrator

On Sun, Mar 24, 2013 at 8:59 PM, Nicholas Thompson <[hidden email]> wrote:

Joshua,

You are absolutely correct. “higher-order bit” it is. Even better. Can you imagine what a former English major’s imagination did with that?

Part of the history of this term is the "big vs little endian" (spelling correct) hardware issue. The hardware can be laid out such that the bits of an integer are are from low-to-hi (little endian) or the reverse (big endian)

http://en.wikipedia.org/wiki/Endianness#Endianness_and_hardware

The reason for little endian is that concatenation of bytes is more natural .. going from a 8 bit integer to a 16 bit integer to a ... is simply laying the bits out in order. It is also the most reasonable for "streaming" a data array such as an image. Most desktop browsers, for example, are little endian. This was a major bug for me in the AgentScript library.

Big endian is more natural when considering the integers themselves, the left-most bit is the MSB .. most significant bit. IIRC, phones tend to use this in their browsers.

JavaScript attempts to mask all this via their typed arrays .. but it still becomes problematic for image/pixel manipulation.

Most libraries depending on pixels now simply create a small, 4-byte array, filling the bytes with 01, 02, 03, 04 and then test for the 32bit value having 01 or 04 at the "high end".

In ether format, the high-order-bit is the bit signifying the highest order of 2 in the bit array.

-- Owen

Russell Standish-2

Re: Just sent this to the Google Device Support Team

In reply to this post by Nick Thompson

On Sun, Mar 24, 2013 at 08:59:39PM -0600, Nicholas Thompson wrote:
> Joshua,
>
>
>
> You are absolutely correct. "higher-order bit" it is. Even better. Can
> you imagine what a former English major's imagination did with that?
>
>
>

Given that "bit" is a slang term for a (possibly young?) woman in some
dialects, the mind boggles. Mind you, according to Urban Dictionary,
it means something entirely different
http://www.urbandictionary.com/define.php?term=bit, but it still fits.

Cheers

--

----------------------------------------------------------------------------
Prof Russell Standish Phone 0425 253119 (mobile)
Principal, High Performance Coders
Visiting Professor of Mathematics [hidden email]
University of New South Wales http://www.hpcoders.com.au
----------------------------------------------------------------------------

============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com

lrudolph

Re: Just sent this to the Google Device Support Team

In reply to this post by Nick Thompson

Nick,

Even a former English major ought to be able to faithfully transcribe a short phrase from the
second line of the first sentence of a two-paragraph, three-sentence e-mail that is actually
included a few inches below the locus of his transcription...

On the other hand, if it weren't for the long history of paleography, scribal errors, and
variorum editions, the structure that for hundreds of years supported the "English major" (and
other "literature majors") might never have existed in the form the former English major may
have encountered stumbling about on its last legs, before it was finally utterly replaced by
the Higher Nonsense.

Lee Rudolph

P.S. No one should forget the old "high-byte"--at least, no one who ever dealt with WordStar.

> You are absolutely correct. "higher-order bit" it is. Even better. Can
> you imagine what a former English major's imagination did with that?
>
>
>
> n
>
>
>
> From: Friam [mailto:[hidden email]] On Behalf Of Joshua Thorp
> Sent: Sunday, March 24, 2013 3:01 PM
> To: The Friday Morning Applied Complexity Coffee Group
> Subject: Re: [FRIAM] Just sent this to the Google Device Support Team
>
>
>
> Also I doubt Owen ever said "top bit", I imagine it was probably
> "high-order bit".
>
>
>
> I like the question though, can a bug be on purpose. Seems like it would be
> in the eye of the beholder, one person's bug might be another's feature.
>
>
>
> --joshua
>
>
>
> On Mar 24, 2013, at 2:57 PM, Douglas Roberts <[hidden email]> wrote:
>
>
>
>
>
> Nick's counselling session will be scheduled shortly...
>
>
>
> --Doug (Who can tell when his chain is being yanked.)
>
>
>
> On Sun, Mar 24, 2013 at 2:53 PM, Nicholas Thompson
> <[hidden email]> wrote:
>
> Now you all know, that, ever since Owen first used the word "top bit" in my
> presence, nearly a decade ago, I have followed, with rapt attention, the use
> of language on this list. So, you guys. I need to understand this better.
> Can a "bug" be "on purpose"? It sounds to me like Google has sabotaged its
> own product, right. Therefore, if I understand the language, any Nexus
> phone thatactually worked, would be "buggy"., by definition. I am sorry to
> bother you about this, but these are the kinds of things that keep me awake
> at night. N
>
>
>
> From: Friam [mailto:[hidden email]] On Behalf Of Douglas Roberts
> Sent: Sunday, March 24, 2013 1:44 PM
> To: The Friday Morning Applied Complexity Coffee Group
> Subject: [FRIAM] Just sent this to the Google Device Support Team
>
>
>
> Hi, Google Device Support Team.
>
>
>
> It's been a while since we spoke, but I recently discovered that someone in
> your organization has been (I hope inadvertently) disseminating inaccurate
> information about this Nexus 4
> <https://productforums.google.com/forum/#!msg/mobile/l4uYRMVHnHY/rHpsXdwNGPc
> J> bug, and I thought you'd want to know about it right away.
>
>
>
> Here's the deal: you see, we all know that the Nexus 4 was not designed on
> purpose to prevent wifi and bluetooth from being used at the same time. We
> all know that it is a bug. Well, all of us except for Steve, apparently.
> Here, read for yourselves:
>
>
>
> http://things-linux.blogspot.com/2013/03/translated.html
>
>
>
> Now, we all have the utmost confidence that someone in your organization
> will immediately take Steve aside for a private little counselling session
> about the inappropriateness of, shall we say, bending the truth regarding
> this particular flaw in the Nexus 4 product.
>
>
>
> Thanks for your prompt attention to this matter.
>
>
>
> Best,
>
>
>
> --Doug
>
>
>
> --
>
> Doug Roberts
> [hidden email]
>
> <http://parrot-farm.net/Second-Cousins>
> http://parrot-farm.net/Second-Cousins
>
>
> 505-455-7333 - Office
> 505-672-8213 - Mobile
>
>
> ============================================================
> FRIAM Applied Complexity Group listserv
> Meets Fridays 9a-11:30 at cafe at St. John's College
> to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com
>
>
>
>
>
>
>
> --
>
> Doug Roberts
> [hidden email]
>
> <http://parrot-farm.net/Second-Cousins>
> http://parrot-farm.net/Second-Cousins
>
>
> 505-455-7333 - Office
> 505-672-8213 - Mobile
>
> ============================================================
> FRIAM Applied Complexity Group listserv
> Meets Fridays 9a-11:30 at cafe at St. John's College
> to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com
>
>
>
>

Douglas Roberts-2

Re: Just sent this to the Google Device Support Team

Nick, I somehow feel that you and I have both been vaguely, yet abstrusely (but delicately) chastised.

--Doug

On Mon, Mar 25, 2013 at 9:04 AM, <[hidden email]> wrote:

Nick,

Even a former English major ought to be able to faithfully transcribe a short phrase from the
second line of the first sentence of a two-paragraph, three-sentence e-mail that is actually
included a few inches below the locus of his transcription...

On the other hand, if it weren't for the long history of paleography, scribal errors, and
variorum editions, the structure that for hundreds of years supported the "English major" (and
other "literature majors") might never have existed in the form the former English major may
have encountered stumbling about on its last legs, before it was finally utterly replaced by
the Higher Nonsense.

Lee Rudolph

P.S. No one should forget the old "high-byte"--at least, no one who ever dealt with WordStar.

> You are absolutely correct. "higher-order bit" it is. Even better. Can
> you imagine what a former English major's imagination did with that?
>
>
>
> n
>
>
>
> From: Friam [mailto:[hidden email]] On Behalf Of Joshua Thorp
> Sent: Sunday, March 24, 2013 3:01 PM
> To: The Friday Morning Applied Complexity Coffee Group
> Subject: Re: [FRIAM] Just sent this to the Google Device Support Team
>
>
>
> Also I doubt Owen ever said "top bit", I imagine it was probably
> "high-order bit".
>
>
>
> I like the question though, can a bug be on purpose. Seems like it would be
> in the eye of the beholder, one person's bug might be another's feature.
>
>
>
> --joshua
>
>
>
> On Mar 24, 2013, at 2:57 PM, Douglas Roberts <[hidden email]> wrote:
>
>
>
>
>
> Nick's counselling session will be scheduled shortly...
>
>
>
> --Doug (Who can tell when his chain is being yanked.)
>
>
>
> On Sun, Mar 24, 2013 at 2:53 PM, Nicholas Thompson
> <[hidden email]> wrote:
>
> Now you all know, that, ever since Owen first used the word "top bit" in my
> presence, nearly a decade ago, I have followed, with rapt attention, the use
> of language on this list. So, you guys. I need to understand this better.
> Can a "bug" be "on purpose"? It sounds to me like Google has sabotaged its
> own product, right. Therefore, if I understand the language, any Nexus
> phone thatactually worked, would be "buggy"., by definition. I am sorry to
> bother you about this, but these are the kinds of things that keep me awake
> at night. N
>
>
>
> From: Friam [mailto:[hidden email]] On Behalf Of Douglas Roberts
> Sent: Sunday, March 24, 2013 1:44 PM
> To: The Friday Morning Applied Complexity Coffee Group
> Subject: [FRIAM] Just sent this to the Google Device Support Team
>
>
>
> Hi, Google Device Support Team.
>
>
>
> It's been a while since we spoke, but I recently discovered that someone in
> your organization has been (I hope inadvertently) disseminating inaccurate
> information about this Nexus 4

> <https://productforums.google.com/forum/#!msg/mobile/l4uYRMVHnHY/rHpsXdwNGPc
> J> bug, and I thought you'd want to know about it right away.

>
>
>
> Here's the deal: you see, we all know that the Nexus 4 was not designed on
> purpose to prevent wifi and bluetooth from being used at the same time. We
> all know that it is a bug. Well, all of us except for Steve, apparently.
> Here, read for yourselves:
>
>
>
> http://things-linux.blogspot.com/2013/03/translated.html
>
>
>
> Now, we all have the utmost confidence that someone in your organization
> will immediately take Steve aside for a private little counselling session
> about the inappropriateness of, shall we say, bending the truth regarding
> this particular flaw in the Nexus 4 product.
>
>
>
> Thanks for your prompt attention to this matter.
>
>
>
> Best,
>
>
>
> --Doug
>
>
>
> --
>
> Doug Roberts
> [hidden email]
>
> <http://parrot-farm.net/Second-Cousins>
> http://parrot-farm.net/Second-Cousins
>
>
> <a href="tel:505-455-7333" value="+15054557333">505-455-7333 - Office
> <a href="tel:505-672-8213" value="+15056728213">505-672-8213 - Mobile
>
>
> ============================================================
> FRIAM Applied Complexity Group listserv
> Meets Fridays 9a-11:30 at cafe at St. John's College
> to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com
>
>
>
>
>
>
>
> --
>
> Doug Roberts
> [hidden email]
>
> <http://parrot-farm.net/Second-Cousins>
> http://parrot-farm.net/Second-Cousins
>
>
> <a href="tel:505-455-7333" value="+15054557333">505-455-7333 - Office
> <a href="tel:505-672-8213" value="+15056728213">505-672-8213 - Mobile
>
> ============================================================
> FRIAM Applied Complexity Group listserv
> Meets Fridays 9a-11:30 at cafe at St. John's College
> to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com
>
>
>
>

============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com

Doug Roberts
[hidden email]

http://parrot-farm.net/Second-Cousins

505-455-7333 - Office
505-672-8213 - Mobile

Barry MacKichan

Re: Just sent this to the Google Device Support Team

In reply to this post by Russell Standish-2

And to think of all the years I described my occupation as "bit diddling"

--Barry
On Mar 24, 2013, at 10:25 PM, Russell Standish <[hidden email]> wrote:

> On Sun, Mar 24, 2013 at 08:59:39PM -0600, Nicholas Thompson wrote:
>> Joshua,
>>
>>
>>
>> You are absolutely correct. "higher-order bit" it is. Even better. Can
>> you imagine what a former English major's imagination did with that?
>>
>>
>>
>
> Given that "bit" is a slang term for a (possibly young?) woman in some
> dialects, the mind boggles. Mind you, according to Urban Dictionary,
> it means something entirely different
> http://www.urbandictionary.com/define.php?term=bit, but it still fits.
>
> Cheers
>
> --
>
> ----------------------------------------------------------------------------
> Prof Russell Standish Phone 0425 253119 (mobile)
> Principal, High Performance Coders
> Visiting Professor of Mathematics [hidden email]
> University of New South Wales http://www.hpcoders.com.au
> ----------------------------------------------------------------------------
>
> ============================================================
> FRIAM Applied Complexity Group listserv
> Meets Fridays 9a-11:30 at cafe at St. John's College
> to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com