Subj : Someone should make that happen..
To   : Ogg
From : Arelor
Date : Sat Jul 17 2021 08:16:40

  Re: Someone should make that happen..
  By: Ogg to Arelor on Fri Jul 16 2021 06:41 pm

 >  A> Also it is liked to a phone number which I dislike as an
 >  A> authentication system. ... [...] I understand the reasons -
 >  A> for the service administrators it is so much easier to use
 >  A> phones as authenticators than user/password combos - but as
 >  A> a power end user it is insulting.
 > 
 > Perhaps they use the phone for authentication because the app
 > was originally a phone app?  ...and DT version came later?

Maybe, but something I have noticed is that common users are no longer capable
of using user/password combinations at all. I am sure developers are aware of
this.

What I mean is that is is extremely common for end users to set an
user/password for some service, such as email. Then they load their access
credentials in some program or application that manages them automatically so
they never have to type them ever again. Then a catastrophe happens to device
that stored the credentials, and when they want to access the service from a
new device they discover it is user/password protected _AND THEY DIDN'T
REMEMBER IT WAS USER/PASSWORD PROTECTED AT ALL_.

So in the end of the day you get lots of phone calls from grandmas and Stoneage
Joes demanding to know "Why the service is password protected now" or just
asking for the credentials to be reset. If the service is any big the overhead
is just BRUTAL.

The simple solution is to skip the password system and use SMS verification.
It sucks for power users because power users understand there is no reason why
the provider should have your phone number at all and it is just a maneuver for
their gain and nothing else.But it helps them deal with the sheeple with less
work.


--
gopher://gopher.richardfalken.com/1/richardfalken

---
 þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL

.