Comunicating from your Linux machine?

[Linux for blind general discussion]

I expect not.  When I ran telegram-cli earlier an import function for
the author of telegram was one of the failures and that oughtn't have
happened since that import was for the original author of telegram who's
address can be found in the README.md file in the source of
telegram-cli.  The import address had strange coding with lots of
backslash characters too.  What I need is a test set of commands that
work on the standard version of telegram I can try on this version of
the package.  That way, I can speed up what I do on this end and you
will have any successes and failures to examine on your end.

On Thu, 12 Sep 2019, Linux for blind general discussion wrote:

> Date: Thu, 12 Sep 2019 13:56:51
> From: Linux for blind general discussion <blinux-list at redhat.com>
> To: blinux-list at redhat.com
> Subject: Re: Comunicating from your Linux machine?
>
> Hello Jude and list,
>
> Telling "I'm not certain sending functions work yet", "may not have been
> buikt the last time" or "Other distributions may have better compiled
> versions of telegram-cli available" don't help to find issues in the
> package, if any."
>
> What I need is actual testing by users, stating what works and what
> doesn't after having actually tried.
>
> So please try the sending functions and report your findings, whatever
> they be. A good report could look like "I did this, excpected  result A,
> got result B."
>
> I never used myself telegram, so I have to rely on end users to file
> bugs in a way then allow to find what's wrong, case occurring.
>
> I am also eager of feedback on any other package shipped in Slint.
>
> Best regards
>
> Didier
> --
> Didier Spaier
> Slint maintainer
>
> On 12/09/2019 17:25, Linux for blind general discussion wrote:
> > On slint we have telegram-cli and although receiving functions work I'm
> > not certain sending functions work yet.  It is a new slint package
> > having first lived in slackbuilds repository so may not have been built
> > properly this last time.  Other distributions may have better compiled
> > versions of telegram-cli available.  It's worth checking.  You will need
> > a cell phone and to provide your cell phone number to telegram-cli to
> > set up an account since for future logins you'll use your username and
> > the provided login code.  The login code is sent to your cell phone and
> > you enter it on the computer to finish setting up your account.
> >
> > On Wed, 11 Sep 2019, Linux for blind general discussion wrote:
> >
> >> Date: Wed, 11 Sep 2019 22:42:15
> >> From: Linux for blind general discussion <blinux-list at redhat.com>
> >> To: Linux for blind general discussion <blinux-list at redhat.com>
> >> Subject: Re: Comunicating from your Linux machine?
> >>
> >>> Telegram works fine here using emacs +emacspeak.
> >>>
> >>> Is there a specialized client you run to make that work, or can it run in
> >>> a
> >>> regular terminal? The Telegram app I saw was a graphical app, but I think
> >>> I
> >>> don't have something set properly, although I assume it's a qt5 app, and I
> >>> had Mumble qt5 working. I would prefer something that interfaces with
> >>> Pidgin, so I stick to the phone for Telegram, as I just didn't look hard
> >>> enough to find a Pidgin plugin, and Pidgin here seems to have trouble with
> >>> voice. That said, looking for telegram didn't yield a Pidgin plugin,
> >>> although I do recall seeing a text client, though it seems it was separate
> >>> from the "official" (air quotes there) client.
> >> ~Kyle
> >>
> >> _______________________________________________
> >> Blinux-list mailing list
> >> Blinux-list at redhat.com
> >> https://www.redhat.com/mailman/listinfo/blinux-list
> >>
> >>
> >
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list at redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

--