Wget Jami-Swarm-x86_64.AppImage downloading does not work

Developers
1

wget https://dl.jami.net/alpha/Jami-Swarm-x86_64.AppImage
https://jami.net/swarm-introducing-a-new-generation-of-group-conversations/

The file appears to be an appimage. Running the above command
does not work. It results in an error message. How do
I download the file?
Why is there no common link for downloading the
file? A link like other files have.

On
jami’s website
can you get a hash sum
for the appimage
file? Thanks.

2

there is no appimage anymore, it’s now in beta and in release on a lot of platforms (https://jami.net/first-jami-beta-with-swarm-support/)

So now, just follow https://jami.net/download-jami-linux/

3

Indeed. I wouldn’t rule out the possibility of adding them again at some point in the future though.

1 Like
4

Are you saying all downloads on
“jami.net/download-jami-linux/”
are the jami beta version? And they all support
swarm?

I already had jami installed. Running
jami I cannot find an about jami
option in the menu. The package manager says
version 20210930.1.835f5ae~dfsg1-1 is
installed. Is that a swarm supporting version?

5

that’s what the article is saying.

Right click on the contact, profile, if you see “Is Swarm:” your version is compatible

6

I found the about jami in jami. The version
is 202110011957

7

Yes, that version should have Swarm support. For individual conversations, you can do what @sblin suggested to check if that conversation is Swarm or not.

8

Ugh. The Arch package is persistently broken; every release introduces some segfault or library issue. The package manager is very responsive, but lately Jami is usually more broken than working on Arch (Issues · Arch Linux / Packaging / Packages / jami-qt · GitLab).

The disk space required to install the flatpak image is 1.3GB. For a chat app. The native packages (jami-daemon, jami-qt) total 33.64MB.

I don’t know if an AppImage would end up being as enormous as Flatpak, but I’d like to know if there’s anything the community can do to contribute to more stability in the project. The Arch packager suggest that the frequent segfault issues is because Jami is highly sensitive to even minor depedency incompatabilities. I wish we could just get some sort of stability.