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 5 of 5 — ← Prev page 1 2 3 4 [5]

#10260

Sylvia Else <sylvia@not.at.this.address> wrote:
> I'm configuring WiFi access to a printer. Look, I'm not going to be
> doing this while on a bus with people looking over my shoulder. So I
> don't need to enter the password into a field that just displays
> asterisks, and type it twice to check that it's the same (and it
> probably won't be).

https://ostermiller.org/bookmarklets/password.html

Add the "View Passwords" bookmarklet to your bookmarks.  While it does
not toggle the fields 'inline', at least you can verify that what you
thought you typed is indeed what made it into the various fields.

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

#10262

On 3/02/2016 10:30 PM, Rich wrote:
> Sylvia Else <sylvia@not.at.this.address> wrote:
>> I'm configuring WiFi access to a printer. Look, I'm not going to be
>> doing this while on a bus with people looking over my shoulder. So I
>> don't need to enter the password into a field that just displays
>> asterisks, and type it twice to check that it's the same (and it
>> probably won't be).
>
> https://ostermiller.org/bookmarklets/password.html
>
> Add the "View Passwords" bookmarklet to your bookmarks.  While it does
> not toggle the fields 'inline', at least you can verify that what you
> thought you typed is indeed what made it into the various fields.
>

In this case, I was using some software provided by the printer 
manufacturer, specifically for configuring their printer for WiFi. As I 
indicated, the password stuff was absurd in this context.

Sylvia.

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

#10263

Sylvia Else <sylvia@not.at.this.address> wrote:
> On 3/02/2016 10:30 PM, Rich wrote:
> > Sylvia Else <sylvia@not.at.this.address> wrote:
> >> I'm configuring WiFi access to a printer. Look, I'm not going to be
> >> doing this while on a bus with people looking over my shoulder. So I
> >> don't need to enter the password into a field that just displays
> >> asterisks, and type it twice to check that it's the same (and it
> >> probably won't be).
> >
> > https://ostermiller.org/bookmarklets/password.html
> >
> > Add the "View Passwords" bookmarklet to your bookmarks.  While it does
> > not toggle the fields 'inline', at least you can verify that what you
> > thought you typed is indeed what made it into the various fields.

> In this case, I was using some software provided by the printer 
> manufacturer, specifically for configuring their printer for WiFi. As I 
> indicated, the password stuff was absurd in this context.

Ah, local client instead of a 'web UI' (which is what many printers
provide for their configuration now-a-days).  Sorry then, the
bookmarklet won't work for that particular situation.

Your other points are still valid, for that UI, 'hiding' the password
behind asterisks was absurd.

Likely the result of them mindlessly adhering to some checkbox
'standard' for 'security' somewhere.  It has a set of checkboxes that
say:

  password entry fields are obscured

  there are two obscured password entry fields

  the software verifies that the entry in both boxes is identical
      before continuing.

And they checked the boxes, so they were 'secure' (or so they thought).

Sadly, 'security' cannot be reduced to a set of checkboxes on a
standard form and still provide true security.  All doing such does is
remove the most common issues, but does not make it _secure_ in any
way.

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

#15053

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.
> 
> 
> 
Just extending this old thread with a new user annoyance item:

When showing a user their credit card details, so that the user can 
update an expiry date, replace some of the card digits with asterisks as 
a security measure, and then complain about them when the user tries to 
submit the change.

Sylvia.

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

#15054

Sylvia Else <sylvia@not.at.this.address> wrote:
> Just extending this old thread with a new user annoyance item:
> 
> When showing a user their credit card details, so that the user can
> update an expiry date, replace some of the card digits with asterisks
> as a security measure, and then complain about them when the user
> tries to submit the change.

Really?  Wow....  Talk about both developers and testing falling down
there.

One of my annoyances surrounding credit cards is the number of website
developers who don't comprehend that computers are *very* good at
removing characters that match a pattern.

So, when the CC processor takes credit card numbers in the form
123456781234 they then extend this requirement all the way to the end
user form.  I get esp.  annoyed by the ones that include "Enter CC
number ..  no spaces" because when that is there in the label it is
very clear they intentionally and purposefully passed along the
back-end API requirements onto the front.

 

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

#15055

On 2/12/2017 12:37 PM, Rich wrote:
> Sylvia Else <sylvia@not.at.this.address> wrote:
>> Just extending this old thread with a new user annoyance item:
>>
>> When showing a user their credit card details, so that the user can
>> update an expiry date, replace some of the card digits with asterisks
>> as a security measure, and then complain about them when the user
>> tries to submit the change.
> 
> Really?  Wow....  Talk about both developers and testing falling down
> there.
> 

I dare say it didn't occur to any of them that this was silly. After 
all, if they didn't have a mindset that says that the user helps the 
computer, rather than the other way around, then we wouldn't see other 
silly stuff, such as the example you mentioned.

Sylvia.

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

#15059

On 2017-12-02, Rich <rich@example.invalid> wrote:
> Sylvia Else <sylvia@not.at.this.address> wrote:
>> Just extending this old thread with a new user annoyance item:
>> 
>> When showing a user their credit card details, so that the user can
>> update an expiry date, replace some of the card digits with asterisks
>> as a security measure, and then complain about them when the user
>> tries to submit the change.
>
> Really?  Wow....  Talk about both developers and testing falling down
> there.
>
> One of my annoyances surrounding credit cards is the number of website
> developers who don't comprehend that computers are *very* good at
> removing characters that match a pattern.
>
> So, when the CC processor takes credit card numbers in the form
> 123456781234 they then extend this requirement all the way to the end
> user form.  I get esp.  annoyed by the ones that include "Enter CC
> number ..  no spaces" because when that is there in the label it is
> very clear they intentionally and purposefully passed along the
> back-end API requirements onto the front.

*applause* And I would generalise that to any number where some organisation
(your bank, the DMV, whatever) sent it to you in one format, say "99-99-99"
and then get pissy when you type it into their website in that format,
insisting on "999999" - yes, UK banks and sort codes, I'm talking about you.

Can I also add American programmers who don't realise there are formats of
phone numbers other than (999)999-9999? Yes, Google Contacts, that's you,
that is.

The series of "Falsehoods Programmers Believe ..." pages are worth a read.

https://www.google.co.uk/search?q=falsehoods+programmers+believe


-- 
Today is Sweetmorn, the 44th day of The Aftermath in the YOLD 3183
        Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.

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

#15061

Huge <Huge@nowhere.much.invalid> wrote:
> On 2017-12-02, Rich <rich@example.invalid> wrote:
>> Sylvia Else <sylvia@not.at.this.address> wrote:
>>> Just extending this old thread with a new user annoyance item:
>>> 
>>> When showing a user their credit card details, so that the user can
>>> update an expiry date, replace some of the card digits with asterisks
>>> as a security measure, and then complain about them when the user
>>> tries to submit the change.
>>
>> Really?  Wow....  Talk about both developers and testing falling down
>> there.
>>
>> One of my annoyances surrounding credit cards is the number of website
>> developers who don't comprehend that computers are *very* good at
>> removing characters that match a pattern.
>>
>> So, when the CC processor takes credit card numbers in the form
>> 123456781234 they then extend this requirement all the way to the end
>> user form.  I get esp.  annoyed by the ones that include "Enter CC
>> number ..  no spaces" because when that is there in the label it is
>> very clear they intentionally and purposefully passed along the
>> back-end API requirements onto the front.
> 
> *applause* And I would generalise that to any number where some organisation
> (your bank, the DMV, whatever) sent it to you in one format, say "99-99-99"
> and then get pissy when you type it into their website in that format,
> insisting on "999999" - yes, UK banks and sort codes, I'm talking about you.
> 
> Can I also add American programmers who don't realise there are formats of
> phone numbers other than (999)999-9999? Yes, Google Contacts, that's you,
> that is.
> 
> The series of "Falsehoods Programmers Believe ..." pages are worth a read.
> 
> https://www.google.co.uk/search?q=falsehoods+programmers+believe

I plucked this one from the "Old Calculator" thread.  In that thread, 
Paul Sture <nospam@sture.ch> said:

  > b) None of the prices shown was likely to match what I paid when I
  >    take postage, packaging and often-disadvantageous currency
  >    conversion rates into account.

Which reminded me of yet another one of my pet-peeves.  Sales sites
that charge postage and handling, but hide the amount of postage and
handling I'll need to pay until *after* I have entered payment details.

*No*....

I want to know the final price, including postage and handling, before
I decide if I'm going to fork over my payment details.  Reason: Once
I've forked over my payment details, I'm 100% dependent upon the site
properly offering an "abort this purchase" mechanism.

Not going to go there.  If the site keeps the postage and handling
hiddden until after the payment details, I'll simply go to some other
site.

It is also irritating how many sites (Amazon and eBay fall into this
category) where their summary listings of items searched for do not
include a price that is "price plus postage" in the list.  At least you
can learn the postage costs by looking at the item page, but they
already know that value, and could sum it into the price on the summary
listing pages.  But usually don't.

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

#15063

Websites that refuse to allow linux browsers but are perfectly happy if 
you select a windows 'user agent' instead.  These people frequently also 
demand newer versions of flash than are available for linux.

-- 
Cheers,  Bev
    Why is it so hot and what am I doing in this handbasket?

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

#15071

On 2017-12-02, The Real Bev <bashley101@gmail.com> wrote:
> Websites that refuse to allow linux browsers but are perfectly happy if 
> you select a windows 'user agent' instead. 

Grrrrr.   :o)


-- 
Today is Boomtime, the 45th day of The Aftermath in the YOLD 3183
        Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.

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

#15072

On 2017-12-02, Rich <rich@example.invalid> wrote:
> Huge <Huge@nowhere.much.invalid> wrote:

[35 lines snipped]

> I plucked this one from the "Old Calculator" thread.  In that thread, 
> Paul Sture <nospam@sture.ch> said:
>
>  > b) None of the prices shown was likely to match what I paid when I
>  >    take postage, packaging and often-disadvantageous currency
>  >    conversion rates into account.
>
> Which reminded me of yet another one of my pet-peeves.  Sales sites
> that charge postage and handling, but hide the amount of postage and
> handling I'll need to pay until *after* I have entered payment details.

Hear bloody hear. I usually abandon the purchase when this happens.


-- 
Today is Boomtime, the 45th day of The Aftermath in the YOLD 3183
        Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.

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

#15062

with <f8ea3sF4limU1@mid.individual.net> Sylvia Else wrote:
> 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.
>> 
>> 
>> 
> Just extending this old thread with a new user annoyance item:
>
> When showing a user their credit card details, so that the user can 
> update an expiry date, replace some of the card digits with asterisks as 
> a security measure, and then complain about them when the user tries to 
> submit the change.

Or take a deep breath and...  In registration form:  [a] cut off prefix;
[b] make user pick that prefix from drop-down list;  [c] make user input
rest of the number in input field *above* the list;  [d] by _make_ mean
real bisyness, by shortening input field to ten characters (luckily
numbers are just numbers and no utf8 is involved) so users can't input
all twelve right away.

-- 
Torvalds' goal for Linux is very simple: World Domination
Stallman's goal for GNU is even simpler: Freedom

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

#15145

On 2/12/2017 11:23 AM, Sylvia Else wrote:
> 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.
>>
>>
>>
> Just extending this old thread with a new user annoyance item:
> 
> When showing a user their credit card details, so that the user can 
> update an expiry date, replace some of the card digits with asterisks as 
> a security measure, and then complain about them when the user tries to 
> submit the change.
> 
> Sylvia.

I pursued this with the government entity involved. The response I got was:

"The RMS is required to comply with Privacy Laws and other road 
transport legislation when dealing with any personal information 
including credit card details.

You need to re-enter your credit card details through a secure platform 
for verification purposes."

This is, of course, total garbage. I've asked for specifics. I'll see 
what happens.

Sylvia.

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

#15146

Sylvia Else <sylvia@not.at.this.address> wrote:
> On 2/12/2017 11:23 AM, Sylvia Else wrote:
>> Just extending this old thread with a new user annoyance item:
>> 
>> When showing a user their credit card details, so that the user can
>> update an expiry date, replace some of the card digits with
>> asterisks as a security measure, and then complain about them when
>> the user tries to submit the change.
> 
> I pursued this with the government entity involved. The response I
> got was:
> 
> "The RMS is required to comply with Privacy Laws and other road 
> transport legislation when dealing with any personal information 
> including credit card details.
> 
> You need to re-enter your credit card details through a secure
> platform for verification purposes."

Ok, fine, then don't pre-fill the field with asterisks, leave it
totally empty, which would be a huge clue to "reenter this detail
here".

> This is, of course, total garbage. I've asked for specifics. I'll see 
> what happens.

It's a BS answer, probably created by someone with little technical
knowledge who's reading from a checklist.

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

#15177

On 14/12/2017 1:06 PM, Rich wrote:
> Sylvia Else <sylvia@not.at.this.address> wrote:
>> On 2/12/2017 11:23 AM, Sylvia Else wrote:
>>> Just extending this old thread with a new user annoyance item:
>>>
>>> When showing a user their credit card details, so that the user can
>>> update an expiry date, replace some of the card digits with
>>> asterisks as a security measure, and then complain about them when
>>> the user tries to submit the change.
>>
>> I pursued this with the government entity involved. The response I
>> got was:
>>
>> "The RMS is required to comply with Privacy Laws and other road
>> transport legislation when dealing with any personal information
>> including credit card details.
>>
>> You need to re-enter your credit card details through a secure
>> platform for verification purposes."
> 
> Ok, fine, then don't pre-fill the field with asterisks, leave it
> totally empty, which would be a huge clue to "reenter this detail
> here".
> 
>> This is, of course, total garbage. I've asked for specifics. I'll see
>> what happens.
> 
> It's a BS answer, probably created by someone with little technical
> knowledge who's reading from a checklist.
> 

I pursued this further, and next got a reply

"Roads and Maritime Services has implemented rigorous security 
mechanisms to ensure that your information and accounts are protected. 
The latest strong encryption technologies have been used to protect your 
data when being sent over the internet."

So I sent a somewhat testy response to that, starting "This is even less 
of an answer to my question that the previous response was" and finally 
reached someone with a clue. The problem may thus ultimately get addressed.

But it's like getting blood out of a stone.

Sylvia.

[toc] | [prev] | [standalone]

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

Back to top | Article view | comp.misc

csiph-web