New release?

[Neustradamus]

Dear @Bitmessage team, @Atheros1, @PeterSurda,

It is possible to have a new release build?

The current latest is very old and not secure (2018-02-13), 7 years old soon.

• https://github.com/Bitmessage/PyBitmessage/releases

Thanks in advance.

[tuxayo]

See #1712

[jon1enforce]

A new release, compatible with openbsd freebsd linux MacOs win64 python2.7 and python3.xx all versions of libressl is necessary, because of security deprecations, and buggy socket. functions.

There is an approach from kashikoibumi@github, and a DEBUG version on my own https://github.com/jon1enforce/DEBUG_pybitmessage

we need a new consens whitepaper, to migrate to the modern state of the art and dependencies.

YOUR Tasks:

consensus whitepaper
migrate this repository to the whitepaper pledges, while keeping a original old version behind.
create an AppImage
create an android image
create an pkg and apt image.

This will make it accessable for all users in the world.

We also need to talk about the protocol, because of post quantum.

[jon1enforce]

exploit...

#2304

[Neustradamus]

Dear @Bitmessage team, @Atheros1, @PeterSurda,

Have you a date for a new release build?

Thanks in advance.

[PeterSurda]

The artifacts for snap, appimage and windows binaries are produced automatically for every change, just getting to them is a bit convoluted.

[Neustradamus]

@PeterSurda: The goal is to have here in GitHub, a tag and a release:

• https://github.com/Bitmessage/PyBitmessage/tags
• https://github.com/Bitmessage/PyBitmessage/releases