Unnerving braking experiences; sudden braking increase.



ddog <[email protected]> wrote:
>
> Are you playing teacher by an unknown web source as your authority?
> Not to say anything is right or wrong, because except for math,
> everything is variable.


Well, I find top posting refreshing personally. It's an almost certain
sign that the poster has a poor grasp of nettiquette and additionally
probably has nothing useful to impart. It certainly speeds up the
decision process of whether to killfile someone or not.

--
Dane Buson - [email protected]
"Besides, I think [Slackware] sounds better than 'Microsoft,' don't you?"
(By Patrick Volkerding)
 
Andrew Muzi writes:

>>> Do not top post. I fixed it for you. In the cases reported I
>>> spent _less_ time with the brakes on. I was not dragging the
>>> brakes as you say.


>> I am curious about the "top post" comment. It appears that bottom
>> posting encourages bandwidth waste and the inclusion of way too
>> much verbiage, especially in longer threads. Since all prior
>> occurances in the thread would likely contain the same stuff, seems
>> redundant.


>> I realize that some folks use readers that make this desirable, and
>> I'm not flaming. Just curious about why this became the "way" to
>> do it on usenet?


> Secondly, it is possible to edit or 'snip' quoted material to
> enhance readability while retaining the prior writer's point. (It's
> also possible to chop up another's words into a twisted version
> unlike his intent but that's another topic)


> .backwards running is conversation of flow the if as, oddly reads
> posting Top .annoying posting top find ,me including ,people Some


Well said. I suspect another aversion to sequential (bottom) posting
is that the writer has made up his mind what he wants to say and
doesn't care what the previous writer(s) have offered that might
conflict with his views.

A reason for not including all previous author's names is that the
response is to what the last person wrote which obviously covers what
went before. If a response to those is intended, one can scroll back
to do that directly. Besides, a stack of names at the top or even
interspersed makes unclear what transpired. the > >> >>> >>>> are
there to make clear from how far back the citations are.

Jobst Brandt
 
On Jan 26, 1:03 pm, "ddog" <[email protected]> wrote:
> Starting to understand better now?


You're still struggling with the emotional aspect of it, but you've
successfully bottom-posted a couple of times now.

You feel better, but you don't like it.

Hang in there, ddog, we're pulling for you. --D-y
 
On Jan 26, 4:03 pm, [email protected] wrote:
> A reason for not including all previous author's names is that the
> response is to what the last person wrote which obviously covers what
> went before. If a response to those is intended, one can scroll back
> to do that directly. Besides, a stack of names at the top or even
> interspersed makes unclear what transpired. the > >> >>> >>>> are
> there to make clear from how far back the citations are.
>
> Jobst Brandt- Hide quoted text -- Show quoted text -


True, True, ... But that is there to see who said what before and in
what order they edited,
as if that makes a difference. It wasn't the real chronological order
of events.
And who's the 'Truth Monitor' to verify every statement in context and
facts, GW Bush - The Decider?
And what exactly does it prove anyway? So and so objected here and
there
and took it out of context here and there?
Its someone hacking a continuous thought and manipulating it into
their own faulty meanings that couldn't stand on the idea's own merit:
period.

You are assuming ideas and verbage are discrete identical independent
entities that can be manipulated like numbers. They are not!

I write in the 'Hear and Now', and don't offer proofs as to what who
said
in what sequence on which thread. That's meaningless. Facts don't have
anything to do with illogical uniform rules. In effect you are arguing
that it is better to have 20 cut up and hacked ideas in 'the format
rule'
rather than one solid continuous idea. Albert Einstein didn't think so.
He shot for
one useful idea out of 20. And he didn't get that one by shotgunning
and hacking up others'
letters in irrelevant thought sequences. Those were 20 uniformly
focused ideas he wanted
5% success rate.

If you consider the combinational effects of who said what in what
order then
you are wasting too much time, and not discovering anything near your
potential otherwise. Your facts would inherently multitask and evolve
into irrelevant minutia.
Talk about leading a horse to a stream, and can't make him drink!
 
In article
<[email protected]>,
"ddog" <[email protected]> wrote:
> Michael Press wrote:
> >
> > You can read about it here.
> >
> > <http://oakroadsystems.com/genl/unice.htm>


[...]


This is a technical newsgroup. Technical discussions
are best understood and followed when the written
response follows the written matter to which the
response is directed.

--
Michael Press
 
On 26 Jan 2007 11:03:22 -0800, "ddog" <[email protected]> wrote:

>Top posting always has reference below IF needed; instead of wasting
>100% of time of 100% of readers.


You don't get it. Bottom posting promotes cutting of extraneous info.
Bottom posting "me too" at the end of a hundre lines of text is lame.
But most of it, leave teh thing to which you're commenting on, and add
your comment below.

In general, if you're writing something that will be read by many
people, it makes sense for you to spend a little extra time editing to
save the many readers each time in reading or glancing around the
extra stuff.

If you are writing to just one or just a handful of people, then that
principle isn't so strong: a reasonable argument could be made that
it doesnt' matter so much who spends the extra time -- the reader or
the writer.


--
JT
****************************
Remove "remove" to reply
Visit http://www.jt10000.com
****************************
 
In article <[email protected]>,
"Mamba" <[email protected]> wrote:

> "Michael Press" <[email protected]> wrote in message
> news:[email protected]...
> > In article
> > <[email protected]>
> > ,
> > "ddog" <[email protected]> wrote:
> >> Michael Press wrote:

> <snip>
>
> > Do not top post. I fixed it for you.
> >
> > In the cases reported I spent _less_ time with the
> > brakes on. I was not dragging the brakes as you say.

>
> I am curious about the "top post" comment. It appears that bottom posting
> encourages bandwidth waste and the inclusion of way too much verbiage,
> especially in longer threads. Since all prior occurances in the thread
> would likely contain the same stuff, seems redundant.
>
> I realize that some folks use readers that make this desirable, and I'm not
> flaming. Just curious about why this became the "way" to do it on usenet?


USENET is a protocol on port 119. It was invented by
the elders who built the internet to propagate
technical news about the network. This requires an easy
to follow thread format so folks could easily identify
what was important for them in maintaining their
connection and holding up their end in maintaining the
network at large.

Naturally enough the channel expanded into tangential
discussions, as any group of like minded folk are wont
to do.

On technical newsgroups bottom posting is a necessity
for ease of understanding. We often need to go back in
a discussion to see exactly where a sub-thread took a
particular turn.

It is easy to top post. The top poster knows what he
has to say and its relevance to what was previously
written. Those who read the top post later,
particularly two or three articles later do not have
the benefit of knowing what the top poster was
thinking.

--
Michael Press
 
In article
<[email protected]>,
"ddog" <[email protected]> wrote:

> On Jan 26, 4:03 pm, [email protected] wrote:
> > A reason for not including all previous author's names is that the
> > response is to what the last person wrote which obviously covers what
> > went before. If a response to those is intended, one can scroll back
> > to do that directly. Besides, a stack of names at the top or even
> > interspersed makes unclear what transpired. the > >> >>> >>>> are
> > there to make clear from how far back the citations are.
> >
> > Jobst Brandt- Hide quoted text -- Show quoted text -

>
> True, True, ... But that is there to see who said what before and in
> what order they edited,
> as if that makes a difference. It wasn't the real chronological order
> of events.
> And who's the 'Truth Monitor' to verify every statement in context and
> facts, GW Bush - The Decider?
> And what exactly does it prove anyway? So and so objected here and
> there
> and took it out of context here and there?
> Its someone hacking a continuous thought and manipulating it into
> their own faulty meanings that couldn't stand on the idea's own merit:
> period.
>
> You are assuming ideas and verbage are discrete identical independent
> entities that can be manipulated like numbers. They are not!
>
> I write in the 'Hear and Now', and don't offer proofs as to what who
> said
> in what sequence on which thread. That's meaningless. Facts don't have
> anything to do with illogical uniform rules. In effect you are arguing
> that it is better to have 20 cut up and hacked ideas in 'the format
> rule'
> rather than one solid continuous idea. Albert Einstein didn't think so.
> He shot for
> one useful idea out of 20. And he didn't get that one by shotgunning
> and hacking up others'
> letters in irrelevant thought sequences. Those were 20 uniformly
> focused ideas he wanted
> 5% success rate.
>
> If you consider the combinational effects of who said what in what
> order then
> you are wasting too much time, and not discovering anything near your
> potential otherwise. Your facts would inherently multitask and evolve
> into irrelevant minutia.
> Talk about leading a horse to a stream, and can't make him drink!


Pure poetry.

--
Michael Press
 
In article <[email protected]>,
"Bill Sornson" <[email protected]> wrote:

> Does this help?


Yes, I finally get it. Took me a while.

> Mamba wrote:
> > "Michael Press" <[email protected]> wrote in message
> > news:[email protected]...
> >> In article
> >> <[email protected]>
> >> ,
> >> "ddog" <[email protected]> wrote:
> >>> Michael Press wrote:

> > <snip>
> >
> >> Do not top post. I fixed it for you.
> >>
> >> In the cases reported I spent _less_ time with the
> >> brakes on. I was not dragging the brakes as you say.

> >
> > I am curious about the "top post" comment. It appears that bottom
> > posting encourages bandwidth waste and the inclusion of way too much
> > verbiage, especially in longer threads. Since all prior occurances
> > in the thread would likely contain the same stuff, seems redundant.
> >
> > I realize that some folks use readers that make this desirable, and
> > I'm not flaming. Just curious about why this became the "way" to do
> > it on usenet?


--
Michael Press
 
[email protected] wrote:
> Andrew Muzi writes:
>
>>>> Do not top post. I fixed it for you. In the cases reported I
>>>> spent _less_ time with the brakes on. I was not dragging the
>>>> brakes as you say.

>
>>> I am curious about the "top post" comment. It appears that bottom
>>> posting encourages bandwidth waste and the inclusion of way too
>>> much verbiage, especially in longer threads. Since all prior
>>> occurances in the thread would likely contain the same stuff, seems
>>> redundant.

>
>>> I realize that some folks use readers that make this desirable, and
>>> I'm not flaming. Just curious about why this became the "way" to
>>> do it on usenet?

>
>> Secondly, it is possible to edit or 'snip' quoted material to
>> enhance readability while retaining the prior writer's point. (It's
>> also possible to chop up another's words into a twisted version
>> unlike his intent but that's another topic)

>
>> .backwards running is conversation of flow the if as, oddly reads
>> posting Top .annoying posting top find ,me including ,people Some

>
> Well said. I suspect another aversion to sequential (bottom) posting
> is that the writer has made up his mind what he wants to say and
> doesn't care what the previous writer(s) have offered that might
> conflict with his views.


Okay, it's time for a rant. That is exactly at the heart of it.

Prior to about 1995 ALL email/usenet used bottom posting, or
interspersed posting, writing the reply directly below that which
you're replying to, because the vast majority of internet email/usenet
users were highly intellegent people, and it just made sense. Nobody
questioned it. And the internet was solely the domain of elite
universities and UNIX. Everyone had access to so-called "bulletin
boards" that you could connect to with a modem, but the discussion
groups were small, and populated by many uninteresting people. The
early '90's saw some corporatations desiring to "connect" to this
wonderful internet (at great expense), mainly pushed by people fresh
out of the universities, but this met with a lot of resistance from
the established middle managers with "mainframe" mentality,
middle-aged mainframe programmers, and the stereotype that these young
techno-geeks couldn't possibly have anything useful to add to any
debate. First a few corporations connect relatively inexpensively via
modem, then some got leased lines, and started putting real money into
it. If you were involved in "research", or putting together a large
group of programmers, they would allow it. But they were the new kids
on the block, and they threatened the power of the established elite.
This corresponds to the downgrading of the engineer, e.g. in NYT the
engineers who designed and built the bridges were hero's early in the
20'th century, but were largely forgotten and ingored by the '60's,
when the non-technical manager and politician took credit for
everything.

Come 1995, the internet was getting pretty well established in the
fortune 50/100/500, and the middle managers felt "forced" into using
this medium when TONS of money started getting funneled into the
"internet", primarily from dictates from above, wishing to replace the
extravagant spending on mainframe and their programmers with so-called
mid-range systems, with potential saving beyond comprehension. Most of
my jobs in the '90's were involved in efforts to displace the
established elite, and the mainframers. But god forbid some young
technically minded person manage efforts of this sort, so these
old-timers were in charge, and they usually managed to bring about
failure, due to their incompentence. Many times these established
middle managers had their secretaries print out the email, or screen
it. One told me once that he didn't think he was obligated to even
look at it.

Meanwhile, more friendly interfaces (apple/windoze) became
email/internet capable, because there ain't no way these non-tech
managers were going to use a UNIX box, e.g. Sun/HP/etc, or, god
forbid, an ascii terminal, so common in the universities, although a
grad student and the profs always had their own Sun workstations,
courtesy of NSF. Also, because of the TONS of corporate money getting
poured into the internet, lots of real morons got jobs working with
computers. They just couldn't find enough people to fill all the
jobs. So these 2 groups flourished, and established top posting, to
the horror of those with years of hard work and experience. Usually
though, the top posts were only one or two lines, at most, so it was
somewhat managable. Many times the top-post is "call me".

The reasons for topposting are simple: They don't care about what
others techies have to say; they don't understand it and are too lazy
to learn because they know they can never compete on that playing
field, and they are too incompetent to edit text, or even move the
cursor. It's hard enough just typing complete sentences. Forget
about paragraphs.

Bill Westphal

>
> A reason for not including all previous author's names is that the
> response is to what the last person wrote which obviously covers what
> went before. If a response to those is intended, one can scroll back
> to do that directly. Besides, a stack of names at the top or even
> interspersed makes unclear what transpired. the > >> >>> >>>> are
> there to make clear from how far back the citations are.
>
> Jobst Brandt
 
ddog wrote:
-snip-
> If you haven't caught on yet, 'rules' and 'procedures' for those who
> can't differentiate and
> make decisions on their own OR critical safety/quality issues (which
> this is not).

-snip-

I got run over by a girl in a truck who felt the same way about traffic
rules

--
Andrew Muzi
www.yellowjersey.org
Open every day since 1 April, 1971
 
Safety issue always number one. There are always exceptions.
Like stop signs in parking lots. Don't worry about them unless other
vehicles are around.

On Jan 27, 1:47 am, A Muzi <[email protected]> wrote:
> ddog wrote:-snip-> If you haven't caught on yet, 'rules' and 'procedures' for those who
> > can't differentiate and
> > make decisions on their own OR critical safety/quality issues (which
> > this is not).-snip-

>
> I got run over by a girl in a truck who felt the same way about traffic
> rules
>
> --
> Andrew Muziwww.yellowjersey.org
> Open every day since 1 April, 1971
 
On 2007-01-27, ddog <[email protected]> wrote:
> The Adult ego state is the only ego state that does not utilize
> psychological games, whichoften involve 'Tragic life scripts'; and is
> purely intellectual like Spock on Star Trek.


You're right that people's ego states sometimes turn threads into Tragic
Life Scripts.

But it's not all bad. You and I are motivated only by the pursuit of
total logic, but sometimes it's people's egotistical desire to prove
each other wrong at all costs that's what drives them to spend the
effort to write clear and well-researched posts.
 
On Jan 27, 2:04 am, "ddog" <[email protected]> wrote:
> Safety issue always number one. There are always exceptions.
> Like stop signs in parking lots. Don't worry about them unless other
> vehicles are around.
>
> On Jan 27, 1:47 am, A Muzi <[email protected]> wrote:
>
> > ddog wrote:-snip-> If you haven't caught on yet, 'rules' and 'procedures' for those who
> > > can't differentiate and
> > > make decisions on their own OR critical safety/quality issues (which
> > > this is not).-snip-

>
> > I got run over by a girl in a truck who felt the same way about traffic
> > rules


Just for the record, "ddog":

I'm reading this on Google Groups. I had the discussion sorted by
date, so one post didn't necessarily follow the one it responded to.

Even with your little top posted comment above, I had to ask myself
"What the hell is he referring to?"

Get with the program. If _everyone_ is telling you you're doing it
wrong, why persist? Learn to do it right. It works.

- Frank Krygowski
 
On Jan 27, 11:58 am, [email protected] wrote:
> Get with the program. If _everyone_ is telling you you're doing it
> wrong, why persist? Learn to do it right. It works.
>
> - Frank Krygowski


Can I be Frank with you?
Because everyone does it and gives no more valid reasoning than that,
it does not come close to better logic and integrity.

When it is applicable, it will be done. Otherwise there are NO
absolute rules
in form no matter what you 'bark'. Minutia and human factor
engineering is
ignored by the ones who act like a 'standard' is the only measure of
their worth.
You can't see the big picture for being overly concerned about minor
insignificant details.
 
Ben C wrote:
>
> ddog wrote:
> >
> > The Adult ego state is the only ego state that does not utilize
> > psychological games, whichoften involve 'Tragic life scripts'; and
> > is purely intellectual like Spock on Star Trek.You're right that
> > people's ego states sometimes turn threads into Tragic Life
> > Scripts.

>
> But it's not all bad. You and I are motivated only by the pursuit of
> total logic, but sometimes it's people's egotistical desire to prove
> each other wrong at all costs that's what drives them to spend the
> effort to write clear and well-researched posts.


Hmm. Perhaps y'all could spin this thread off to alt.crackpot-
notions.psychological?

Chalo
 
On Sat, 27 Jan 2007 04:49:12 +0100, Bill Westphal wrote:

> Okay, it's time for a rant. That is exactly at the heart of it.

[rantsnip]
>[Usenet history and jargon goes here]

[snip]

It's also good to change the title when the topic changes. :p

/me puts on nomex underpants.
 
On Jan 26, 3:30 pm, Michael Press <[email protected]> wrote:
> In article <[email protected]>,
>
>
>
> "Mamba" <[email protected]> wrote:
> > "Michael Press" <[email protected]> wrote in message
> >news:[email protected]...
> > > In article
> > > <[email protected]>
> > > ,
> > > "ddog" <[email protected]> wrote:
> > >> Michael Press wrote:

> > <snip>

>
> > > Do not top post. I fixed it for you.

>
> > > In the cases reported I spent _less_ time with the
> > > brakes on. I was not dragging the brakes as you say.

>
> > I am curious about the "top post" comment. It appears that bottom posting
> > encourages bandwidth waste and the inclusion of way too much verbiage,
> > especially in longer threads. Since all prior occurances in the thread
> > would likely contain the same stuff, seems redundant.

>
> > I realize that some folks use readers that make this desirable, and I'm not
> > flaming. Just curious about why this became the "way" to do it on usenet?USENET is a protocol on port 119. It was invented by

> the elders who built the internet to propagate
> technical news about the network.


I thought Al Gore started the internet....he's not that old.....

This requires an easy
> to follow thread format so folks could easily identify
> what was important for them in maintaining their
> connection and holding up their end in maintaining the
> network at large.
>
> Naturally enough the channel expanded into tangential
> discussions, as any group of like minded folk are wont
> to do.
>
> On technical newsgroups bottom posting is a necessity
> for ease of understanding. We often need to go back in
> a discussion to see exactly where a sub-thread took a
> particular turn.
>
> It is easy to top post. The top poster knows what he
> has to say and its relevance to what was previously
> written. Those who read the top post later,
> particularly two or three articles later do not have
> the benefit of knowing what the top poster was
> thinking.
>
> --
> Michael Press
 
Check both the rim and pads for signs of unusual wear; specifically,
if the
> rim is significantly worn, you can end up with a lip near the top and
> bottom. As the brake pads wear, pressure is at first applied to the very
> small surface area of the lip, after which it drops down into the main
> section... which can suddenly increase the braking forces.
>
> --Mike Jacoubowsky
> Chain Reaction Bicycleswww.ChainReaction.com
> Redwood City & Los Altos, CA USA


No Mike, I don't think this is the way it works. I have also
experience this phenomena with KoolStop pads (I haven't experienced it
with other pads purely because I have used Koostops for a while now
and have not had the chance to try and repeat the phenomena with other
pads) and the effect is repeatable. Ride the brake and suddenly brake
force increases. Cool it down a bit, ride it again and it does the
same all over again. On inspection, you don't see any noticeable
change in the pad appearance.

I believe it is temperature related and that something happens at a
critical temperature at the interface of rim and pad.

I also remember once that after applying using the brakes for a
specific period of time, they suddenly blew off debris which landed on
and stuck to on my thighs - little shavings of black rubber
grindings. This was before I used Koolstop pads. I remember
distinctly that this only happened a while into braking, not
immediately. I'm pretty certain that I applied continuous pressure to
the levers throughout, in both cases cited above.

Johan Bornman