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


Groups > comp.misc > #15177

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

From Sylvia Else <sylvia@not.at.this.address>
Newsgroups comp.misc
Subject Re: Let's compile a list of ways to annoy the user.
Date 2017-12-21 13:52 +1100
Message-ID <fa0lv2FnlgqU1@mid.individual.net> (permalink)
References <dfo97jFc2lfU1@mid.individual.net> <f8ea3sF4limU1@mid.individual.net> <f9e3nsFf9k2U1@mid.individual.net> <p0smad$dja$1@dont-email.me>

Show all headers | View raw


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.

Back to comp.misc | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

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

csiph-web