Alpine 2.22 released

[Adam H. Kerman]

Among additions from previous versions are the XOAUTH2 support for Gmail.
Users will have to get their own client-id and client-secret from Google,
which can be shared with up to 100 users.

I've barely followed this. Is this some sort of file one uploads to
gmail to identify the user? I hope it won't turn out that google is
using it to track users when using other applications.

There is also automatic display of calendar events, to make it easy for
you to read invitations that you are sent.

alpine built-in calendar, or a calendar from other programs?

All feedback that can be used to improve future releases of Alpine is
highly appreciated. Enjoy!

Thanks for your selfless devotion to email communication.

[Eduardo Chappa]

This post might be inappropriate. Click to display it.

[Adam H. Kerman]

Post by Eduardo Chappa

Post by Adam H. Kerman
I've barely followed this. Is this some sort of file one uploads to
gmail to identify the user? I hope it won't turn out that google is
using it to track users when using other applications.

There could be many reasons for this. The main one is that a hacker cannot
steal all your data. XOAUTH2 allows you to access your email and that's
it, not yoour google drive, etc. Google is always getting as much
information as they can about you, but in this case, it also helps with
your security.

If it remains a proprietary means of authentication to gmail, I guess
that's a point. If it spreads to other Google services, maybe not.

Post by Eduardo Chappa

Post by Adam H. Kerman

There is also automatic display of calendar events, to make it easy
for you to read invitations that you are sent.

alpine built-in calendar, or a calendar from other programs?

This is built-in. However, you cannot (yet) do more than just view the
event.

Ok. I'm using the calendar in my cell phone. I should probably revert to
a pocket calendar I carry with me.

Years ago, an old Verizon smartphone I used at times had a nicely
designed calendar able to look up addressbook entries, which meant if
the appointment was at someone's office, then it filled in the meeting
location.

The alpine addressbook doesn't have very many fields or organizing
options. It's less convenient to repeat the same data from one dataset
to another, but maybe that's a good thing, given years of history of the
built-in Microsoft addressbook being used to spread viruses through
email.

[Eduardo Chappa]

Post by Adam H. Kerman
If it remains a proprietary means of authentication to gmail, I guess
that's a point. If it spreads to other Google services, maybe not.

XOAUTH2 is a standard, but it is only offered by Google. This is not
propietary of google in any way. This is really not different than a
username and password combinarion that you use with any server. If you
call XOAUTH2 propietary for google, then every authentication with
username and password would be propietary. It is not different than that.

[Adam H. Kerman]

Post by Eduardo Chappa

Post by Adam H. Kerman
If it remains a proprietary means of authentication to gmail, I guess
that's a point. If it spreads to other Google services, maybe not.

XOAUTH2 is a standard, but it is only offered by Google. This is not
propietary of google in any way. This is really not different than a
username and password combinarion that you use with any server. If you
call XOAUTH2 propietary for google, then every authentication with
username and password would be propietary. It is not different than that.

Well, yes, that's the way I'm using the term "proprietary".

Basic security should mean I use proprietary username-password
combination for every remote host I log onto.

[Johann Beretta]

Post by Adam H. Kerman
Well, yes, that's the way I'm using the term "proprietary".
Basic security should mean I use proprietary username-password
combination for every remote host I log onto.

It's not like that anywhere in the corporate world. Generally you have 1
username and password that you can use to log into your "account" from
any host on the network that you are permitted to use.

Roamning Desktop was what it was called at one time.

[William Unruh]

This is a multi-part message in MIME format.
--------------98BF61A637F512EBCE3F284D
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Post by Adam H. Kerman
=20
Well, yes, that's the way I'm using the term "proprietary".
=20
Basic security should mean I use proprietary username-password
combination for every remote host I log onto.

Propietary means owned by someone, with copyright/trademark/patent law
to back up that ownership.
I think what you mean is "different".

Post by Adam H. Kerman
=20

It's not like that anywhere in the corporate world. Generally you have 1
username and password that you can use to log into your "account" from
any host on the network that you are permitted to use.
Roamning Desktop was what it was called at one time.

[Bud Spencer]

Dear Alpiners,
it is with great please that I announce the release of version 2.22 of
Alpine. This version brings new features and fixes bugs found in earlier
releases of Alpine. As with any version, test it by yourself before putting
into a production environment.
The source code and PC-Alpine binary versions can be downloaded from
http://alpine.x10host.com/alpine/release/

This is wonderful news!

There is also automatic display of calendar events, to make it easy for you
to read invitations that you are sent.

So calendar .. interesting!


/
Bud
/

a1=S0
b1=[1..2,'L0L']
a2=2*a1
a3=S1.4#b1
a4=(a2,a3)
a5=64*a4

[Bud Spencer]

Out of the curiosity, do you have any idea how long it takes for new
releases to get into FreeBSD ports?


/
Bud
/

a1=S0
b1=[1..2,'L0L']
a2=2*a1
a3=S1.4#b1
a4=(a2,a3)
a5=64*a4

[Lucas Levrel]

Hi,

it is with great please that I announce the release of version 2.22 of
Alpine.

Many thanks Eduardo for your continuous work on Alpine. Is there an "all"
patch for 2.22 ? Or should I apply the latest of the 2.21.x series ?

[Eduardo Chappa]

Post by Lucas Levrel
Many thanks Eduardo for your continuous work on Alpine. Is there an
"all" patch for 2.22 ? Or should I apply the latest of the 2.21.x series
?

Yes, everything was updated. The latest all.patch can be found at

http://alpine.x10host.com/alpine/info/all.html

Thank you.

[Brandon Jewett-Hall]

Impressive!

[Allodoxaphobia]

This post might be inappropriate. Click to display it.

[Dermot Loughnane]

Dear Alpiners,
it is with great please that I announce the release of version 2.22 of
Alpine. This version brings new features and fixes bugs found in earlier
releases of Alpine. As with any version, test it by yourself before
putting into a production environment.
The source code and PC-Alpine binary versions can be downloaded from
http://alpine.x10host.com/alpine/release/
Among additions from previous versions are the XOAUTH2 support for Gmail.
Users will have to get their own client-id and client-secret from Google,
which can be shared with up to 100 users.
There is also automatic display of calendar events, to make it easy for
you to read invitations that you are sent.
Other additions and bug fixes can be found in the Release Notes, which
can be accessed from the Main Screen by pressing "R", or by following the
link above. There are two binaries of PC-Alpine in the web site. The
explanation of the difference between these versions is in the web site.
All feedback that can be used to improve future releases of Alpine is
highly appreciated. Enjoy!
--
Eduardo

First thing, thanks so much Eduardo for keeping this going! Alpine has been my daily driver for many years now, not sure what I'd do if it went away. Mutt? yikes!

That having been said, long time listener, first time caller. If I want to replace my 2.21 with 2.22 do I have to start again from scratch and build the new version or is there some way to "upgrade" 2.21 to 2.22? Assume you're talking to a dolt and it will be more efficient!

[Eduardo Chappa]

Post by Dermot Loughnane
That having been said, long time listener, first time caller. If I want
to replace my 2.21 with 2.22 do I have to start again from scratch and
build the new version or is there some way to "upgrade" 2.21 to 2.22?
Assume you're talking to a dolt and it will be more efficient!

Building from source is the best way to do this. You can download the
source from

http://alpine.x10host.com/alpine/release/

and unpack the source code with the command

$ tar Jxf alpine-2.22.tar.xz

then use the

$ ./configure

command. If it fails, let me know how it fails. Many times you need to
install extra libraries, I can tell you what you need.

If you prefer to avoid that, you will have to wait until yout distribution
upgrades their version of Alpine. That will depend on the distribution of
linux that you use. Unfortuantely, there is no "upgrade" where the binary
upgrades somehow, and all is good. Someone has to do this process of
compilation or downloading a fresh copy from their distribution for
Alpine.