Subj : Someone should make that happen..
To   : Arelor
From : Ogg
Date : Sun Jul 18 2021 11:12:00

Hello Arelor!

** On Saturday 17.07.21 - 08:16, Arelor wrote to Ogg:

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

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

Yes... that seems to be a consequence of people once being  
accustomed to using desktops for most of their login  
requirements and switching to tablets or phones that seem to  
manange logins a bit differently?


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

Like I said..  I bet Telegram was designed with smartphones/ 
tablets in mind considering that sales seem to indicated most  
people have migrated to those devices or that they are are 1st  
devices of purchase for those entering the "net" realm for the  
first time?

Meanwhile, Telegram's desktop solution (via an Electron core)  
might be a kludge, but it is a fine and efficient kludge never  
the less. However, Telegram's open API allows anyone to design  
and build their own Telegram app.  It would be cool if there  
was one that handled Fidonet echos with FTN characteristics in  
mind: in-line requoting, random taglines, etc.

But the current solution provided by a sysop located in Crimea  
is very clever. He's built a bot that basically acts like a  
scanner/tosser and accomodates the various FTN requirements.

The bot even accomodates modest netmail-to-Telegram messaging  
and visa versa. It's not a vastly advertised feature, but one  
that I am willing to explain how to operate to anyone who pops  
onto the network and asks me!  ;)


--- OpenXP 5.0.50
 * Origin: Ogg's Dovenet Point (723:320/1.9)
 þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

.