Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #76066 > unrolled thread

Hey, Nospam

Back to article view | Back to comp.sys.mac.system

Contents

  Hey, Nospam Michelle Steiner <michelle@michelle.org> - 2015-06-03 08:32 -0700
    Re: Hey, Nospam android <here@there.was> - 2015-06-03 17:44 +0200
    Re: Hey, Nospam awoolmeyer@gmail.com - 2015-06-03 10:42 -0700
    Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-04 06:47 +1000
      Re: Hey, Nospam BobbyK <bknight@Conramp.net> - 2015-06-03 17:01 -0500
        Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-04 14:13 +1000
          Re: Hey, Nospam BobbyK <bknight@Conramp.net> - 2015-06-04 06:44 -0500
            Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-05 07:13 +1000
              Re: Hey, Nospam BobbyK <bknight@Conramp.net> - 2015-06-04 17:55 -0500
                Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-05 11:45 +1000
                  Re: Hey, Nospam BobbyK <bknight@Conramp.net> - 2015-06-04 21:37 -0500
                    Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-05 14:36 +1000
        Re: Hey, Nospam Aldo Raine <apache@scalpem.net> - 2015-06-04 08:55 -0400
        Re: Hey, Nospam gtr <xxx@yyy.zzz> - 2015-06-04 10:00 -0700
          Re: Hey, Nospam Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-06-05 07:51 +0000
        Re: Hey, Nospam George Kerby <ghost_topper@hotmail.com> - 2015-06-06 08:37 -0500
    Re: Hey, Nospam Barry Margolin <barmar@alum.mit.edu> - 2015-06-03 17:57 -0400
      Re: Hey, Nospam Michelle Steiner <michelle@michelle.org> - 2015-06-03 16:12 -0700
        Re: Hey, Nospam nospam <nospam@nospam.invalid> - 2015-06-03 23:11 -0400
          Re: Hey, Nospam Michelle Steiner <michelle@michelle.org> - 2015-06-03 20:42 -0700
            Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-04 14:17 +1000
              Re: Hey, Nospam Michelle Steiner <michelle@michelle.org> - 2015-06-03 21:34 -0700
                Re: Hey, Nospam jamiekg@wizardling.geek.nz (Jamie Kahn Genet) - 2015-06-04 16:41 +1200
                Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-05 07:09 +1000
              Re: Hey, Nospam me@home.spamsucks.ca (Király) - 2015-06-04 13:12 +0000
            Re: Hey, Nospam News <News@Group.Post> - 2015-06-04 07:20 -0400
              Re: Hey, Nospam Aldo Raine <apache@scalpem.net> - 2015-06-04 09:00 -0400
        Re: Hey, Nospam "Lee Waun" <leewaun@telus.net> - 2015-06-05 20:04 -0700
      Re: Hey, Nospam nospam <nospam@nospam.invalid> - 2015-06-03 23:11 -0400
        Re: Hey, Nospam Michelle Steiner <michelle@michelle.org> - 2015-06-03 20:41 -0700
          Re: Hey, Nospam nospam <nospam@nospam.invalid> - 2015-06-03 23:53 -0400
            Re: Hey, Nospam Michelle Steiner <michelle@michelle.org> - 2015-06-03 21:30 -0700
              Re: Hey, Nospam me@home.spamsucks.ca (Király) - 2015-06-04 13:14 +0000
                Re: Hey, Nospam nospam <nospam@nospam.invalid> - 2015-06-04 12:52 -0400
                  Re: Hey, Nospam Király <ggrandish@gmail.com> - 2015-06-04 10:08 -0700
                    Re: Hey, Nospam nospam <nospam@nospam.invalid> - 2015-06-04 13:58 -0400
                  Re: Hey, Nospam Tim Streater <timstreater@greenbee.net> - 2015-06-04 18:45 +0100
                    Re: Hey, Nospam nospam <nospam@nospam.invalid> - 2015-06-04 13:58 -0400
                      Re: Hey, Nospam Tim Streater <timstreater@greenbee.net> - 2015-06-04 21:20 +0100
                      Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-05 07:24 +1000
                        Re: Hey, Nospam nospam <nospam@nospam.invalid> - 2015-06-04 18:09 -0400
                          Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-05 11:37 +1000
                            Re: Hey, Nospam nospam <nospam@nospam.invalid> - 2015-06-04 22:02 -0400
                              Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-05 14:19 +1000
                  Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-05 07:18 +1000
                    Re: Hey, Nospam nospam <nospam@nospam.invalid> - 2015-06-04 18:09 -0400
                      Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-05 11:39 +1000
                        Re: Hey, Nospam nospam <nospam@nospam.invalid> - 2015-06-04 22:02 -0400
                          Re: Hey, Nospam BobbyK <bknight@Conramp.net> - 2015-06-04 21:39 -0500
                            Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-05 14:37 +1000
                              Re: Hey, Nospam BobbyK <bknight@Conramp.net> - 2015-06-05 08:07 -0500
                                Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-06 13:04 +1000
                          Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-05 14:21 +1000
                        Re: Hey, Nospam JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-06-04 22:13 -0400
                          Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-05 14:36 +1000
                            Re: Hey, Nospam JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-06-05 01:07 -0400
                              Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-05 15:49 +1000
                                Re: Hey, Nospam JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-06-05 16:46 -0400
                                  Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-06 15:17 +1000
                Re: Hey, Nospam JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-06-04 13:44 -0400
                  Re: Hey, Nospam ggrandish@gmail.com - 2015-06-04 10:51 -0700
                    Re: Hey, Nospam nospam <nospam@nospam.invalid> - 2015-06-04 13:58 -0400
                    Re: Hey, Nospam JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-06-04 14:51 -0400
                  Re: Hey, Nospam "Rod Speed" <rod.speed.aaa@gmail.com> - 2015-06-05 07:22 +1000
        Re: Hey, Nospam George Kerby <ghost_topper@hotmail.com> - 2015-06-06 08:38 -0500
      Re: Hey, Nospam George Kerby <ghost_topper@hotmail.com> - 2015-06-06 08:36 -0500
    Re: Hey, Nospam ggrandish@gmail.com - 2015-06-03 15:44 -0700
      Re: Hey, Nospam Michelle Steiner <michelle@michelle.org> - 2015-06-03 16:14 -0700
        Re: Hey, Nospam Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-06-04 03:36 +0000
          Re: Hey, Nospam Michelle Steiner <michelle@michelle.org> - 2015-06-03 20:46 -0700
            Re: Hey, Nospam Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-06-05 07:38 +0000
          Re: Hey, Nospam Tim Streater <timstreater@greenbee.net> - 2015-06-04 08:50 +0100
      Re: Hey, Nospam jamiekg@wizardling.geek.nz (Jamie Kahn Genet) - 2015-06-04 16:38 +1200
    Re: Hey, Nospam George Kerby <ghost_topper@hotmail.com> - 2015-06-06 08:35 -0500

Page 4 of 4 — ← Prev page 1 2 3 [4]

#76122

On Thursday, June 4, 2015 at 10:44:07 AM UTC-7, JF Mezei wrote:
> No carrier offers subsidized phones without a contract.

I am afraid you are mistaken.
I am on a pay-as-you-go plan.
I bought enough minutes in advance that they gave me a credit that paid for the
phone.
I did this the same day I took the phone out of the box.
I have never been on a contract and I can walk away at any time without owing 
the carrier anything, because I have never owed them anything.

-- 
K.

Lang may your lum reek.

[toc] | [prev] | [next] | [standalone]

#76125

In article <0792a085-8f5a-4a5a-841e-aeafcf7663aa@googlegroups.com>,
<ggrandish@gmail.com> wrote:

> > No carrier offers subsidized phones without a contract.
> 
> I am afraid you are mistaken.

he is not. you are.

> I am on a pay-as-you-go plan.
> I bought enough minutes in advance that they gave me a credit that paid for
> the
> phone.

which means it's not subsidized.

> I did this the same day I took the phone out of the box.
> I have never been on a contract and I can walk away at any time without owing 
> the carrier anything, because I have never owed them anything.

again, it's not subsidized. you are mistaken.

[toc] | [prev] | [next] | [standalone]

#76127

On 15-06-04 13:51, ggrandish@gmail.com wrote:

> I bought enough minutes in advance that they gave me a credit that paid for the
> phone.

More like: you paid for the phone in whole, and carrier used remaining
funds to give you the advertised minutes.  The deal was on the cost per
minute, not on the phone.


You can have contracts with prepaid service that involve a subsidized
phone. In canada they call them "tabs" but they are still contracts.

[toc] | [prev] | [next] | [standalone]

#76140

JF Mezei <jfmezei.spamnot@vaxination.ca> wrote
> Király wrote

>> There's also subsidized without a contract, which I'm on.

> No carrier offers subsidized phones without a contract.

Wrong, ALL of ours do.

> When the lend you money to get the handset,
> they want to make sure you will pay it back.

That is just one way to do subsidized phones.

The other obvious way is to lock the phone to their
system and sell it to you for a lower price than you
would pay for a phone which is not locked.

> They may have used euphemisms instead of "contract" but there is
> something you agreed to which ensures you pay back the subsidy.

No there is not if they charge you a lower price for the phone and
lock it to their system so its no use on anything but their system.

> If you end service before the subsidy has been
> repaid, I bet you have termination penalty.

There isn't with phones that are bought up front at a lower
price than the same phone not locked to any carrier. 

[toc] | [prev] | [next] | [standalone]

#76345

On 6/3/15 10:11 PM, in article 030620152311565661%nospam@nospam.invalid,
"nospam" <nospam@nospam.invalid> wrote:

> In article <barmar-A718CF.17575903062015@88-209-239-213.giganet.hu>,
> Barry Margolin <barmar@alum.mit.edu> wrote:
> 
>>> Capitalization is important.  Most people would write, "...helping your
>>> Uncle Jack off a horse."  But you would write, "...helping your uncle
>>> jack off a horse."
>> 
>> Are those of us who don't read every thread supposed to know what this
>> refers to? To me it seems to be totally out of the blue.
> 
> it's nothing more than a personal attack because i showed her to be
> wrong about something.

And, you want to be "different".

[toc] | [prev] | [next] | [standalone]

#76343

On 6/3/15 4:57 PM, in article
barmar-A718CF.17575903062015@88-209-239-213.giganet.hu, "Barry Margolin"
<barmar@alum.mit.edu> wrote:

> In article <030620150832466218%michelle@michelle.org>,
>  Michelle Steiner <michelle@michelle.org> wrote:
> 
>> Capitalization is important.  Most people would write, "...helping your
>> Uncle Jack off a horse."  But you would write, "...helping your uncle
>> jack off a horse."
> 
> Are those of us who don't read every thread supposed to know what this
> refers to? To me it seems to be totally out of the blue.

Yes. A blue one...

[toc] | [prev] | [next] | [standalone]

#76076

On Wednesday, June 3, 2015 at 8:32:49 AM UTC-7, Michelle Steiner wrote:
> Capitalization is important.  Most people would write, "...helping your
> Uncle Jack off a horse."  But you would write, "...helping your uncle
> jack off a horse."

nospam's [sic] lack of capitalization doesn't bother me nearly as much as
people who put double spaces after sentences. That practice is as obsolete
as the typewriter.

The one that grates on my nerves the most is people who insert an apostrophe
in the word "its". I see "it's" used in place of "its" more often than I see
correct usage.

-- 
K.

Lang may your lum reek.

[toc] | [prev] | [next] | [standalone]

#76079

In article <8df95275-bf89-449a-b837-4b02067e86f2@googlegroups.com>,
<ggrandish@gmail.com> wrote:

> nospam's [sic] lack of capitalization doesn't bother me nearly as much as
> people who put double spaces after sentences. That practice is as obsolete
> as the typewriter.

Considering that usenet is a text-only medium, readers should be using
fixed-width fonts, and those read better with a double space after a
period and colon.

[toc] | [prev] | [next] | [standalone]

#76082

In message <030620151614288455%michelle@michelle.org> 
  Michelle Steiner <michelle@michelle.org> wrote:
> In article <8df95275-bf89-449a-b837-4b02067e86f2@googlegroups.com>,
> <ggrandish@gmail.com> wrote:

>> nospam's [sic] lack of capitalization doesn't bother me nearly as much as
>> people who put double spaces after sentences. That practice is as obsolete
>> as the typewriter.

> Considering that usenet is a text-only medium,

Yes...

> readers should be using fixed-width fonts,

Um... no, that doesn't follow.

> and those read better with a double space after a period and colon.

I look at it as an antiquated convention. If I have two spaces after a
period, it is an accident. There is no reason for it other than someone
100 years ago or so thought it looked better. I disagree, and I find it
is very likely to lead to very bad 'rivers' through extended paragraphs.

However, that is as nothing compared to Moron Number One putting a space
before question marks.

-- 
In Genua, stories came to life. In Genua, someone set out to make dreams
come true. Remember some of your dreams?

[toc] | [prev] | [next] | [standalone]

#76085

In article <slrnmmvi0b.265t.g.kreme@amelia.local>, Lewis
<g.kreme@gmail.com.dontsendmecopies> wrote:

> I look at it as an antiquated convention. If I have two spaces after a
> period, it is an accident. There is no reason for it other than someone
> 100 years ago or so thought it looked better. I disagree, and I find it
> is very likely to lead to very bad 'rivers' through extended paragraphs.

It was developed because single-spacing after a period made typewritten
text harder to parse.  However, with proportional text, such as with
typeset material, it's always been a single space.

The spacing is, or should be, dependent upon the medium.  Before the
Macintosh, personal computers all used fixed-width text, and
double-spacing after a period was the norm.

[toc] | [prev] | [next] | [standalone]

#76204

In message <030620152046351808%michelle@michelle.org> 
  Michelle Steiner <michelle@michelle.org> wrote:
> In article <slrnmmvi0b.265t.g.kreme@amelia.local>, Lewis
> <g.kreme@gmail.com.dontsendmecopies> wrote:

>> I look at it as an antiquated convention. If I have two spaces after a
>> period, it is an accident. There is no reason for it other than someone
>> 100 years ago or so thought it looked better. I disagree, and I find it
>> is very likely to lead to very bad 'rivers' through extended paragraphs.

> It was developed because single-spacing after a period made typewritten
> text harder to parse.  However, with proportional text, such as with
> typeset material, it's always been a single space.

It was a stylistic choice made when a period was centered in the
font-space, which is not the case now, there the period (and comma) are
on the left size of the font. Even so, on my Dad's Smith Corona text was
perfectly readable with a single space after a period.

> The spacing is, or should be, dependent upon the medium.  Before the
> Macintosh, personal computers all used fixed-width text, and
> double-spacing after a period was the norm.

It's certainly what typing teachers taught, but there was never any
reason for it. It's a lot like the "never end a sentence with a
preposition" 'rule' that has nothing to do with English.

-- 
Ninety percent of true love is acute, ear-burning embarrassment. --Wyrd
Sisters

[toc] | [prev] | [next] | [standalone]

#76098

In article <slrnmmvi0b.265t.g.kreme@amelia.local>, Lewis
<g.kreme@gmail.com.dontsendmecopies> wrote:

>In message <030620151614288455%michelle@michelle.org> 
>  Michelle Steiner <michelle@michelle.org> wrote:
>> In article <8df95275-bf89-449a-b837-4b02067e86f2@googlegroups.com>,
>> <ggrandish@gmail.com> wrote:
>
>>> nospam's [sic] lack of capitalization doesn't bother me nearly as much as
>>> people who put double spaces after sentences. That practice is as obsolete
>>> as the typewriter.
>
>> Considering that usenet is a text-only medium,
>
>Yes...
>
>> readers should be using fixed-width fonts,
>
>Um... no, that doesn't follow.
>
>> and those read better with a double space after a period and colon.
>
>I look at it as an antiquated convention. If I have two spaces after a
>period, it is an accident. There is no reason for it other than someone
>100 years ago or so thought it looked better.

People still tend to do it even when using Word - this defeating the
ability of word processors to make the correct judgement about such
spacing after a full-stop. Interestingly, FrameMaker (at least when I
was using it) ignored the second and any subsequent spaces. You could
type them after a full-stop, but it ignored them.

-- 
New Socialism consists essentially in being seen to have your heart in 
the right place whilst your head is in the clouds and your hand is in 
someone else's pocket.

[toc] | [prev] | [next] | [standalone]

#76091

<ggrandish@gmail.com> wrote:

> On Wednesday, June 3, 2015 at 8:32:49 AM UTC-7, Michelle Steiner wrote:
> > Capitalization is important.  Most people would write, "...helping your
> > Uncle Jack off a horse."  But you would write, "...helping your uncle
> > jack off a horse."
> 
> nospam's [sic] lack of capitalization doesn't bother me nearly as much as
> people who put double spaces after sentences. That practice is as obsolete
> as the typewriter.
> 
> The one that grates on my nerves the most is people who insert an apostrophe
> in the word "its". I see "it's" used in place of "its" more often than I see
> correct usage.

I'm guilty of the latter from time to time :-\ But at least if I stop to
think and proofread, I do actually know when an apostrophe ought to be
used (in place of missing letters or possessively).

What bothers me is people who clearly have no understanding. It's not
just sloppy writing as occasionally in my case. It's ignorance and zero
willingness to learn better. You should see some of the punctuation-free
wall of texts I have to deal with from even older people one would think
might know better...
-- 
If you're not part of the solution, you're part of the precipitate.

[toc] | [prev] | [next] | [standalone]

#76342

On 6/3/15 10:32 AM, in article 030620150832466218%michelle@michelle.org,
"Michelle Steiner" <michelle@michelle.org> wrote:

> Capitalization is important.  Most people would write, "...helping your
> Uncle Jack off a horse."  But you would write, "...helping your uncle
> jack off a horse."

BFG!!!!

;-)

[toc] | [prev] | [standalone]

Page 4 of 4 — ← Prev page 1 2 3 [4]

Back to top | Article view | comp.sys.mac.system

csiph-web