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

Groups > comp.misc > #9969 > unrolled thread

Let's compile a list of ways to annoy the user.

Back to article view | Back to comp.misc

Contents

  Let's compile a list of ways to annoy the user. Sylvia Else <sylvia@not.at.this.address> - 2016-01-14 11:42 +1100
    Re: Let's compile a list of ways to annoy the user. Larry Sheldon <lfsheldon@gmail.com> - 2016-01-13 19:30 -0600
      Re: Let's compile a list of ways to annoy the user. Bob Eager <news0006@eager.cx> - 2016-01-14 01:39 +0000
        Re: Let's compile a list of ways to annoy the user.     wje@acm.org (Bill Evans) - 2016-01-13 18:06 -0800
          Re: Let's compile a list of ways to annoy the user. Larry Sheldon <lfsheldon@gmail.com> - 2016-01-13 21:30 -0600
            Re: Let's compile a list of ways to annoy the user. Huge <Huge@nowhere.much.invalid> - 2016-01-14 15:26 +0000
              Re: Let's compile a list of ways to annoy the user. Rich <rich@example.invalid> - 2016-01-14 15:42 +0000
                Re: Let's compile a list of ways to annoy the user. Paul Sture <nospam@sture.ch> - 2016-01-29 10:33 +0100
          Re: Let's compile a list of ways to annoy the user. Hils <hils@saynotospam.net> - 2016-01-14 19:32 +0000
          Re: Let's compile a list of ways to annoy the user. Michael Black <et472@ncf.ca> - 2016-01-14 14:51 -0500
            Re: Let's compile a list of ways to annoy the user. Mike Spencer <mds@bogus.nodomain.nowhere> - 2016-01-15 01:42 -0400
              Re: Let's compile a list of ways to annoy the user. Rich <rich@example.invalid> - 2016-01-15 13:08 +0000
                Re: Let's compile a list of ways to annoy the user. Mike Spencer <mds@bogus.nodomain.nowhere> - 2016-01-15 15:47 -0400
                  Re: Let's compile a list of ways to annoy the user. Rich <rich@example.invalid> - 2016-01-15 19:57 +0000
                    Re: Let's compile a list of ways to annoy the user. Michael Black <et472@ncf.ca> - 2016-01-15 15:36 -0500
                  Re: Let's compile a list of ways to annoy the user. Paul Sture <nospam@sture.ch> - 2016-01-29 10:43 +0100
                    Re: Let's compile a list of ways to annoy the user. scott@alfter.diespammersdie.us (Scott Alfter) - 2016-01-29 17:08 +0000
          Re: Let's compile a list of ways to annoy the user. Paul Sture <nospam@sture.ch> - 2016-01-17 16:21 +0100
        Re: Let's compile a list of ways to annoy the user. Huge <Huge@nowhere.much.invalid> - 2016-01-14 15:26 +0000
          Re: Let's compile a list of ways to annoy the user. Rich <rich@example.invalid> - 2016-01-14 15:44 +0000
        Re: Let's compile a list of ways to annoy the user. Anssi Saari <as@sci.fi> - 2016-01-15 14:25 +0200
        Re: Let's compile a list of ways to annoy the user. Paul Sture <nospam@sture.ch> - 2016-01-17 16:09 +0100
      Re: Let's compile a list of ways to annoy the user. Huge <Huge@nowhere.much.invalid> - 2016-01-14 15:25 +0000
      Re: Let's compile a list of ways to annoy the user. Paul Sture <nospam@sture.ch> - 2016-01-17 16:04 +0100
        Re: Let's compile a list of ways to annoy the user. Huge <Huge@nowhere.much.invalid> - 2016-01-17 16:07 +0000
          Re: Let's compile a list of ways to annoy the user. Paul Sture <nospam@sture.ch> - 2016-01-29 10:51 +0100
        Re: Let's compile a list of ways to annoy the user. Sylvia Else <sylvia@not.at.this.address> - 2016-01-18 11:59 +1100
          Re: Let's compile a list of ways to annoy the user. Michael Black <et472@ncf.ca> - 2016-01-17 22:55 -0500
          Re: Let's compile a list of ways to annoy the user. Bob Eager <news0006@eager.cx> - 2016-01-18 08:55 +0000
            Re: Let's compile a list of ways to annoy the user. Sylvia Else <sylvia@not.at.this.address> - 2016-01-18 23:25 +1100
            Re: Let's compile a list of ways to annoy the user. Paul Sture <nospam@sture.ch> - 2016-01-29 11:09 +0100
    Re: Let's compile a list of ways to annoy the user. Rich <rich@example.invalid> - 2016-01-14 02:36 +0000
    Re:Let's compile a list of ways to annoy the user. RS Wood <rsw@therandymon.com> - 2016-01-14 09:20 +0400
      Re: Re:Let's compile a list of ways to annoy the user. Rich <rich@example.invalid> - 2016-01-14 11:11 +0000
        Re: Let's compile a list of ways to annoy the user. "Dirk T. Verbeek" <dverbeek@xs4all.nl> - 2016-01-14 12:58 +0100
          Re: Let's compile a list of ways to annoy the user. Rich <rich@example.invalid> - 2016-01-14 15:19 +0000
      Re: Let's compile a list of ways to annoy the user. Huge <Huge@nowhere.much.invalid> - 2016-01-14 15:31 +0000
        Re: Let's compile a list of ways to annoy the user. Paul Sture <nospam@sture.ch> - 2016-01-29 11:50 +0100
      Re: Let's compile a list of ways to annoy the user. Paul Sture <nospam@sture.ch> - 2016-01-29 11:24 +0100
    Re: Let's compile a list of ways to annoy the user. Marko Rauhamaa <marko@pacujo.net> - 2016-01-14 08:38 +0200
      Re: Let's compile a list of ways to annoy the user. Sylvia Else <sylvia@not.at.this.address> - 2016-01-14 18:12 +1100
        Re: Let's compile a list of ways to annoy the user. Paul Sture <nospam@sture.ch> - 2016-01-24 10:45 +0100
          Re: Let's compile a list of ways to annoy the user. Sylvia Else <sylvia@not.at.this.address> - 2016-01-24 22:47 +1100
            Re: Let's compile a list of ways to annoy the user. Marko Rauhamaa <marko@pacujo.net> - 2016-01-24 14:07 +0200
      Re: Let's compile a list of ways to annoy the user. Paul Sture <nospam@sture.ch> - 2016-01-18 00:15 +0100
    Re: Let's compile a list of ways to annoy the user. Huge <Huge@nowhere.much.invalid> - 2016-01-14 15:18 +0000
    Re: Let's compile a list of ways to annoy the user. Anssi Saari <as@sci.fi> - 2016-01-15 14:16 +0200
      Re: Let's compile a list of ways to annoy the user. Huge <Huge@nowhere.much.invalid> - 2016-01-15 12:17 +0000
      Re: Let's compile a list of ways to annoy the user. Larry Sheldon <lfsheldon@gmail.com> - 2016-01-15 18:56 -0600
        Re: Let's compile a list of ways to annoy the user. Larry Sheldon <lfsheldon@gmail.com> - 2016-01-15 23:53 -0600
      Re: Let's compile a list of ways to annoy the user. Sylvia Else <sylvia@not.at.this.address> - 2016-01-16 17:16 +1100
        Re: Let's compile a list of ways to annoy the user. Michael Black <et472@ncf.ca> - 2016-01-16 18:03 -0500
    Re: Let's compile a list of ways to annoy the user. Batchman <batchman@fastmail.fm> - 2016-01-16 11:01 +1100
      Re: Let's compile a list of ways to annoy the user. Michael Black <et472@ncf.ca> - 2016-01-15 23:38 -0500
        Re: Let's compile a list of ways to annoy the user. Larry Sheldon <lfsheldon@gmail.com> - 2016-01-15 23:51 -0600
          Re: Let's compile a list of ways to annoy the user. Huge <Huge@nowhere.much.invalid> - 2016-01-16 10:40 +0000
          Re: Let's compile a list of ways to annoy the user. Michael Black <et472@ncf.ca> - 2016-01-16 17:59 -0500
    Re: Let's compile a list of ways to annoy the user. Sylvia Else <sylvia@not.at.this.address> - 2016-01-22 19:23 +1100
      Re: Let's compile a list of ways to annoy the user. Paul Sture <nospam@sture.ch> - 2016-01-22 10:53 +0100
        Re: Let's compile a list of ways to annoy the user. Huge <Huge@nowhere.much.invalid> - 2016-01-22 17:23 +0000
    Re: Let's compile a list of ways to annoy the user. Paul Sture <nospam@sture.ch> - 2016-01-22 13:12 +0100
      Re: Let's compile a list of ways to annoy the user. polygonum <rmoudndgers@vrod.co.uk> - 2016-01-22 18:38 +0000
        Re: Let's compile a list of ways to annoy the user. "G. Paul Ziemba" <unp@ziemba.us> - 2016-01-24 18:14 +0000
      Re: Let's compile a list of ways to annoy the user. "Dirk T. Verbeek" <dverbeek@xs4all.nl> - 2016-01-24 16:31 +0100
        Re: Let's compile a list of ways to annoy the user. Paul Sture <nospam@sture.ch> - 2016-01-24 19:52 +0100
          Re: Let's compile a list of ways to annoy the user. "Dirk T. Verbeek" <dverbeek@xs4all.nl> - 2016-01-24 22:07 +0100
        Re: Let's compile a list of ways to annoy the user. Michael Black <et472@ncf.ca> - 2016-01-24 21:36 -0500
    Re: Let's compile a list of ways to annoy the user. Sylvia Else <sylvia@not.at.this.address> - 2016-01-29 15:29 +1100
      Re: Let's compile a list of ways to annoy the user. Sylvia Else <sylvia@not.at.this.address> - 2016-01-29 16:38 +1100
      Re: Let's compile a list of ways to annoy the user. Kara M'bola <maxupixu@in.val.it> - 2016-01-29 10:19 +0000
      Re: Let's compile a list of ways to annoy the user. Paul Sture <nospam@sture.ch> - 2016-01-29 11:57 +0100
        Re: Let's compile a list of ways to annoy the user. Huge <Huge@nowhere.much.invalid> - 2016-01-29 11:00 +0000
        Re: Let's compile a list of ways to annoy the user. Michael Black <et472@ncf.ca> - 2016-01-29 13:22 -0500
          Re: Let's compile a list of ways to annoy the user. Rich <rich@example.invalid> - 2016-01-29 19:49 +0000
            Re: Let's compile a list of ways to annoy the user. Michael Black <et472@ncf.ca> - 2016-01-29 23:30 -0500
        Re: Let's compile a list of ways to annoy the user. Bob Eager <news0006@eager.cx> - 2016-01-29 22:36 +0000
      Re: Let's compile a list of ways to annoy the user. Sylvia Else <sylvia@not.at.this.address> - 2016-01-30 12:25 +1100
        Re: Let's compile a list of ways to annoy the user. Michael Black <et472@ncf.ca> - 2016-01-29 23:33 -0500
    Re: Let's compile a list of ways to annoy the user. Sylvia Else <sylvia@not.at.this.address> - 2016-02-03 19:02 +1100
      Re: Let's compile a list of ways to annoy the user. Paul Sture <nospam@sture.ch> - 2016-02-03 11:45 +0100
      Re: Let's compile a list of ways to annoy the user. Rich <rich@example.invalid> - 2016-02-03 11:30 +0000
        Re: Let's compile a list of ways to annoy the user. Sylvia Else <sylvia@not.at.this.address> - 2016-02-03 23:18 +1100
          Re: Let's compile a list of ways to annoy the user. Rich <rich@example.invalid> - 2016-02-03 12:55 +0000
    Re: Let's compile a list of ways to annoy the user. Sylvia Else <sylvia@not.at.this.address> - 2017-12-02 11:23 +1100
      Re: Let's compile a list of ways to annoy the user. Rich <rich@example.invalid> - 2017-12-02 01:37 +0000
        Re: Let's compile a list of ways to annoy the user. Sylvia Else <sylvia@not.at.this.address> - 2017-12-02 13:12 +1100
        Re: Let's compile a list of ways to annoy the user. Huge <Huge@nowhere.much.invalid> - 2017-12-02 09:39 +0000
          Re: Let's compile a list of ways to annoy the user. Rich <rich@example.invalid> - 2017-12-02 18:02 +0000
            Re: Let's compile a list of ways to annoy the user. The Real Bev <bashley101@gmail.com> - 2017-12-02 12:44 -0800
              Re: Let's compile a list of ways to annoy the user. Huge <Huge@nowhere.much.invalid> - 2017-12-03 09:31 +0000
            Re: Let's compile a list of ways to annoy the user. Huge <Huge@nowhere.much.invalid> - 2017-12-03 09:43 +0000
      Re: Let's compile a list of ways to annoy the user. Eric Pozharski <whynot@pozharski.name> - 2017-12-02 15:31 +0200
      Re: Let's compile a list of ways to annoy the user. Sylvia Else <sylvia@not.at.this.address> - 2017-12-14 12:50 +1100
        Re: Let's compile a list of ways to annoy the user. Rich <rich@example.invalid> - 2017-12-14 02:06 +0000
          Re: Let's compile a list of ways to annoy the user. Sylvia Else <sylvia@not.at.this.address> - 2017-12-21 13:52 +1100

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

#9983

On 14/01/2016 5:38 PM, Marko Rauhamaa wrote:
>
> Have an easy way to subscribe to a paid service but make it virtually
> impossible to find a way to unsubscribe or contact customer service.
>
>
> Marko
>

Though we know that that's deliberate, and not just the result of 
incompetence.

Sylvia.

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

#10105

On 2016-01-14, Sylvia Else <sylvia@not.at.this.address> wrote:
> On 14/01/2016 5:38 PM, Marko Rauhamaa wrote:
>>
>> Have an easy way to subscribe to a paid service but make it virtually
>> impossible to find a way to unsubscribe or contact customer service.
>>
>>
>> Marko
>>
>
> Though we know that that's deliberate, and not just the result of 
> incompetence.

Yes it's deliberate, and telcos and ISPs also have a nasty habit of
ignoring valid cancellation requests and continuing to bill for services
no longer required.  They get vicious when you refuse to pay, and freely
use debt collectors to do their dirty work for them.

There's a lot of money at stake here:

<http://www.huffingtonpost.com/2011/01/21/aols-dirty-little-secret-_n_812307.html>

"AOL's "Dirty Little Secret": 60% of AOL's Profits Come From Misinformed
Customers [UPDATE]"

<http://www.businessinsider.com/how-to-cancel-aol>

"AOL's "Dirty Secret": Email This Post To Your Parents And Grandparents
To Make Sure They Aren't Paying AOL When They Don't Have To

...

Editor's note: This post originally referred to AOL's subscription
business as a "scam." It does raise some interesting ethical questions,
but it is not a scam.  We have apologzed to AOL and our readers for
describing it as such here."

Well fine not a scam, this is a tax on the stupid/uninformed you might
say, but they also make it difficult to leave.

Ar least there appears to be an option to cancel online, which is more
than can be said for various other providers.

<https://intoolate.wordpress.com/2009/12/30/how-to-cancel-your-free-or-paid-aol-account-with-aols-online-cancel-form/>

But a little digging on that site and we come across this kind of
behaviour:

<https://intoolate.wordpress.com/2009/11/19/how-yet-another-reader-got-over-400-back-from-aol-by-complaining-to-the-bbb/>

"In July I got a bill from AOL saying that I owed $51.80. I sent another
letter explaining the situation again, and both letters have included my
work and cell numbers where I can be reached. I have yet to hear from
them. Now today I received another letter saying that it is now going to
collections. AOL owes me between $300-400 dollars. I have accepted the
fact that I will probably never see a cent of this money, however now I
have something that I don’t even owe going on my credit report. What
advice can you give me?"

This pattern emerges with other telcos and ISPs.  For example:

<http://www.bbc.co.uk/news/business-14569918>

"TalkTalk and its Tiscali UK subsidiary have been fined £3m for
incorrectly billing more than 65,000 customers for services they had not
received."

They also paid compensation:

<http://www.bbc.co.uk/news/business-12595391>

"Compensation

Ofcom said that the two firms, who together have 4.2 million customers,
had taken steps to fix the problem.

An average of about £40 has been paid to thousands of customers in
refunds or compensation payments.

People must be refunded if, since 1 January 2010, they have paid bills
that should not have been levied.

And credit ratings agencies must be told to repair any damaged credit
histories."

That last line is I suspect the tip of the iceberg.  They are way too
happy to "resolve complaints" by handing customers over to debt
collection agencies.  As we move towards a cashless society, this is
increasingly dangerous behaviour; they really can wreck folks' lives in
pursuit of fraudulent charges and quite clearly don't give a shit about
doing so.


-- 
An invention needs to make sense in the world in which it's finished,
not the world in which it's started.                  -- Ray Kurzweil

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

#10107

On 24/01/2016 8:45 PM, Paul Sture wrote:
> On 2016-01-14, Sylvia Else <sylvia@not.at.this.address> wrote:
>> On 14/01/2016 5:38 PM, Marko Rauhamaa wrote:
>>>
>>> Have an easy way to subscribe to a paid service but make it virtually
>>> impossible to find a way to unsubscribe or contact customer service.
>>>
>>>
>>> Marko
>>>
>>
>> Though we know that that's deliberate, and not just the result of
>> incompetence.
>
> Yes it's deliberate, and telcos and ISPs also have a nasty habit of
> ignoring valid cancellation requests and continuing to bill for services
> no longer required.  They get vicious when you refuse to pay, and freely
> use debt collectors to do their dirty work for them.

Well, two can play that game. When an ISP here made it difficult for me 
to cancel my account (only cancel by phone, indefinite waiting), I sent 
them an email telling them to cancel it. When they continued to bill my 
credit card, I showed up at their head office with the relevant court 
documents completed, and asked whether someone would like to discuss it 
with me before I filed them.

All sorted, that same day.

Sylvia.

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

#10108

Sylvia Else <sylvia@not.at.this.address>:

> On 24/01/2016 8:45 PM, Paul Sture wrote:
>> Yes it's deliberate, and telcos and ISPs also have a nasty habit of
>> ignoring valid cancellation requests and continuing to bill for
>> services no longer required. They get vicious when you refuse to pay,
>> and freely use debt collectors to do their dirty work for them.
>
> Well, two can play that game. When an ISP here made it difficult for
> me to cancel my account (only cancel by phone, indefinite waiting), I
> sent them an email telling them to cancel it. When they continued to
> bill my credit card, I showed up at their head office with the
> relevant court documents completed, and asked whether someone would
> like to discuss it with me before I filed them.
>
> All sorted, that same day.

You surely made them change their ways...

Anyway, I've noticed that a paper letter is much more effective than
email in such correspondence.


Marko

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

#10048

On 2016-01-14, Marko Rauhamaa <marko@pacujo.net> wrote:
>
> Have an easy way to subscribe to a paid service but make it virtually
> impossible to find a way to unsubscribe or contact customer service.

It's worth checking for exit routes before signing up for anything.

-- 
An invention needs to make sense in the world in which it's finished,
not the world in which it's started.                  -- Ray Kurzweil

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

#9987

On 2016-01-14, Sylvia Else <sylvia@not.at.this.address> wrote:
> We should probably limit it to things people have actually seen.
>
> 1. Limits that are not stated up front.
>
> 2. If the user tries to submit a form with invalid data, clear the form, 
> and make the user fill it all in again.

And don't tell them what & where the invalid data is.

-- 
Today is Prickle-Prickle, the 14th day of Chaos in the YOLD 3182
                  I don't have an attitude problem.
    If you have a problem with my attitude, that's your problem.

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

#9999

Sylvia Else <sylvia@not.at.this.address> writes:

> We should probably limit it to things people have actually seen.
>
> 1. Limits that are not stated up front.

My favorite: web-based job application system that has multiple pages
and a hidden timeout. So that it wipes out your painstakingly input data
if you take too long (and all that was in your CV anyways...)

> 2. If the user tries to submit a form with invalid data, clear the
> form, and make the user fill it all in again.

Or at least clear *some* field and have the user find it themselves.
I think password field is typical and really annoying.

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

#10000

On 2016-01-15, Anssi Saari <as@sci.fi> wrote:
> Sylvia Else <sylvia@not.at.this.address> writes:
>
>> We should probably limit it to things people have actually seen.
>>
>> 1. Limits that are not stated up front.
>
> My favorite: web-based job application system that has multiple pages
> and a hidden timeout. So that it wipes out your painstakingly input data
> if you take too long (and all that was in your CV anyways...)

Yes, PeopleSoft, that's you, that is.

-- 
Today is Setting Orange, the 15th day of Chaos in the YOLD 3182
                  I don't have an attitude problem.
    If you have a problem with my attitude, that's your problem.

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

#10012

On 1/15/2016 06:16, Anssi Saari wrote:
> Sylvia Else <sylvia@not.at.this.address> writes:
>
>> We should probably limit it to things people have actually seen.
>>
>> 1. Limits that are not stated up front.
>
> My favorite: web-based job application system that has multiple pages
> and a hidden timeout. So that it wipes out your painstakingly input data
> if you take too long (and all that was in your CV anyways...)

Amazon's mystery browser has an especially virulent version of 
that--while reading Facebook, if you have temerity to actually READ some 
lengthy item (after (if) the vertigo-inducing ad-flashing stops), it 
will give a message the the effect that the scrip has died and gives you 
a "pull the trigger when you are ready to die" message.
-- 
sed quis custodiet ipsos custodes? (Juvenal)

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

#10015

On 1/15/2016 18:56, Larry Sheldon wrote:
> On 1/15/2016 06:16, Anssi Saari wrote:
>> Sylvia Else <sylvia@not.at.this.address> writes:
>>
>>> We should probably limit it to things people have actually seen.
>>>
>>> 1. Limits that are not stated up front.
>>
>> My favorite: web-based job application system that has multiple pages
>> and a hidden timeout. So that it wipes out your painstakingly input data
>> if you take too long (and all that was in your CV anyways...)
>

Clarifying:

> Amazon's mystery browser ^ has an especially virulent version of
                            ^ used on Kindle

> that--while reading Facebook, if you have temerity to actually READ some
> lengthy item (after (if) the vertigo-inducing ad-flashing stops), it
> will give a message the the effect that the scrip has died and gives you
> a "pull the trigger when you are ready to die" message.


-- 
sed quis custodiet ipsos custodes? (Juvenal)

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

#10016

On 15/01/2016 11:16 PM, Anssi Saari wrote:
> Sylvia Else <sylvia@not.at.this.address> writes:
>
>> We should probably limit it to things people have actually seen.
>>
>> 1. Limits that are not stated up front.
>
> My favorite: web-based job application system that has multiple pages
> and a hidden timeout. So that it wipes out your painstakingly input data
> if you take too long (and all that was in your CV anyways...)
>
>> 2. If the user tries to submit a form with invalid data, clear the
>> form, and make the user fill it all in again.
>
> Or at least clear *some* field and have the user find it themselves.
> I think password field is typical and really annoying.
>

I cam across one today, that left most of the from alone, including the 
password, but which, for some unfathomable reason, cleared my name so 
that I had to enter it again.

Of course, the really fun forms are those that clear two, unrelated 
fields, so that one fixes one, then the other, only to discover that now 
the first one needs to be fixed again. I've been through several 
iterations of such before realising what was happening.

Sylvia.

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

#10039

On Sat, 16 Jan 2016, Sylvia Else wrote:

> On 15/01/2016 11:16 PM, Anssi Saari wrote:
>> Sylvia Else <sylvia@not.at.this.address> writes:
>> 
>>> We should probably limit it to things people have actually seen.
>>> 
>>> 1. Limits that are not stated up front.
>> 
>> My favorite: web-based job application system that has multiple pages
>> and a hidden timeout. So that it wipes out your painstakingly input data
>> if you take too long (and all that was in your CV anyways...)
>> 
>>> 2. If the user tries to submit a form with invalid data, clear the
>>> form, and make the user fill it all in again.
>> 
>> Or at least clear *some* field and have the user find it themselves.
>> I think password field is typical and really annoying.
>> 
>
> I cam across one today, that left most of the from alone, including the 
> password, but which, for some unfathomable reason, cleared my name so that I 
> had to enter it again.
>
> Of course, the really fun forms are those that clear two, unrelated fields, 
> so that one fixes one, then the other, only to discover that now the first 
> one needs to be fixed again. I've been through several iterations of such 
> before realising what was happening.
>
I was given a magazine subscription for Christmas, just digital 
subscription.  SO I get the email, and use the link to set things up.  But 
there's a field that isn't marked.  I assume it's for email since that has 
to be a key component of my identifying me as the actual receiver of the 
gift.  But that's a guess.  I had some problems, maybe I didn't copy the 
password right or what, but each time they'd show the page and say 
something is wrong, but not what. I can see that being a security thing, 
if I was just guessing at usernames and passwords not knowing which was 
which means I can't work on the one that's wrong, but I was just setting 
this up and I didn't know what the wrong variable was.

I still don't know what happened, clearing things and signing in was fine.

   Michael

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

#10011

Sylvia Else wrote:

> 2. If the user tries to submit a form with invalid data, clear the form,
> and make the user fill it all in again.
> 
Encountered that on a website recently when attempting to make a donation.
The page returned an error message advising that it REQUIRED data in a 
specified field (I had filled all others) and then returned the original 
BLANK form.

I sent them a message to advise that they had a problem and that it was 
probably costing them $$$.

--- news://freenews.netfront.net/ - complaints: news@netfront.net ---

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

#10013

On Sat, 16 Jan 2016, Batchman wrote:

> Sylvia Else wrote:
>
>> 2. If the user tries to submit a form with invalid data, clear the form,
>> and make the user fill it all in again.
>>
> Encountered that on a website recently when attempting to make a donation.
> The page returned an error message advising that it REQUIRED data in a
> specified field (I had filled all others) and then returned the original
> BLANK form.
>
> I sent them a message to advise that they had a problem and that it was
> probably costing them $$$.
>
If it takes too much trouble, it probably does lose people.

   Michael

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

#10014

On 1/15/2016 22:38, Michael Black wrote:
> On Sat, 16 Jan 2016, Batchman wrote:
>
>> Sylvia Else wrote:
>>
>>> 2. If the user tries to submit a form with invalid data, clear the form,
>>> and make the user fill it all in again.
>>>
>> Encountered that on a website recently when attempting to make a
>> donation.
>> The page returned an error message advising that it REQUIRED data in a
>> specified field (I had filled all others) and then returned the original
>> BLANK form.
>>
>> I sent them a message to advise that they had a problem and that it was
>> probably costing them $$$.
>>
> If it takes too much trouble, it probably does lose people.

I give up instantly when something like that happens.  And some 
for-profits have lost my business that way too.


-- 
sed quis custodiet ipsos custodes? (Juvenal)

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

#10017

On 2016-01-16, Larry Sheldon <lfsheldon@gmail.com> wrote:
> On 1/15/2016 22:38, Michael Black wrote:
>> On Sat, 16 Jan 2016, Batchman wrote:
>>
>>> Sylvia Else wrote:
>>>
>>>> 2. If the user tries to submit a form with invalid data, clear the form,
>>>> and make the user fill it all in again.
>>>>
>>> Encountered that on a website recently when attempting to make a
>>> donation.
>>> The page returned an error message advising that it REQUIRED data in a
>>> specified field (I had filled all others) and then returned the original
>>> BLANK form.
>>>
>>> I sent them a message to advise that they had a problem and that it was
>>> probably costing them $$$.
>>>
>> If it takes too much trouble, it probably does lose people.
>
> I give up instantly when something like that happens.  And some 
> for-profits have lost my business that way too.

<AOL>

-- 
Today is Sweetmorn, the 16th day of Chaos in the YOLD 3182
                  I don't have an attitude problem.
    If you have a problem with my attitude, that's your problem.

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

#10038

On Fri, 15 Jan 2016, Larry Sheldon wrote:

> On 1/15/2016 22:38, Michael Black wrote:
>> On Sat, 16 Jan 2016, Batchman wrote:
>> 
>>> Sylvia Else wrote:
>>> 
>>>> 2. If the user tries to submit a form with invalid data, clear the form,
>>>> and make the user fill it all in again.
>>>> 
>>> Encountered that on a website recently when attempting to make a
>>> donation.
>>> The page returned an error message advising that it REQUIRED data in a
>>> specified field (I had filled all others) and then returned the original
>>> BLANK form.
>>> 
>>> I sent them a message to advise that they had a problem and that it was
>>> probably costing them $$$.
>>> 
>> If it takes too much trouble, it probably does lose people.
>
> I give up instantly when something like that happens.  And some for-profits 
> have lost my business that way too.
>
ANd that's the sad part.  Non-profits have more purpose on the internet 
than business, yet they often don't use  the internet effectively, too 
often using business as the model they approach the internet with.

   Michael

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

#10074

On 14/01/2016 11:42 AM, Sylvia Else wrote:
> We should probably limit it to things people have actually seen.
>
> 1. Limits that are not stated up front.
>
> 2. If the user tries to submit a form with invalid data, clear the form,
> and make the user fill it all in again.
>
> 3. Have an on-line support chat page that offers the option to print-out
> the chat so far, but when the chat ends, go immediately to another page,
> without letting the user print out the whole thing.
>
> (I got that just the other day, and the page I got sent too was a
> feedback page so that I could rate the experience I'd just had).
>
> Sylvia.
>
>
>

Labyrinthine menu hierarchies to obtain support that lead to a set of 
options that do not encompass all possibilities, and do not offer an 
"anything else" category. Particularly exasperating when contacting 
support by phone.

Sylvia

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

#10078

On 2016-01-22, Sylvia Else <sylvia@not.at.this.address> wrote:
>
> Labyrinthine menu hierarchies to obtain support that lead to a set of 
> options that do not encompass all possibilities, and do not offer an 
> "anything else" category. Particularly exasperating when contacting 
> support by phone.

Moving back to computers, menuing systems which take you down several
levels then when you exit what you went to do, dump you back at the top
level.  At its worst, ask for a password somewhere along the way, which
will need to be re-entered as you navigate back to where you had just
been.

-- 
An invention needs to make sense in the world in which it's finished,
not the world in which it's started.                  -- Ray Kurzweil

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

#10085

And from a website mere moments ago, one that reports you already have
an account, then when you try and recover the password, that you do not
have an account.

Schroedinger's Logon?


-- 
Today is Boomtime, the 22nd day of Chaos in the YOLD 3182
                  I don't have an attitude problem.
    If you have a problem with my attitude, that's your problem.

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

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

Back to top | Article view | comp.misc

csiph-web