Package Details: yandex-messenger 2.155.0-4

Git Clone URL: https://aur.archlinux.org/yandex-messenger.git (read-only, click to copy)
Package Base: yandex-messenger
Description: Yandex Messenger is designed for communication: send text messages, make audio and video calls in private and group chats, subscribe to and create channels. Communicate with colleagues in a private space.
Upstream URL: https://yandex.com/support/messenger/install.html
Keywords: messaging
Licenses: custom
Submitter: bulatovv
Maintainer: bulatovv
Last Packager: bulatovv
Votes: 2
Popularity: 0.001438
First Submitted: 2023-09-19 12:53 (UTC)
Last Updated: 2025-05-03 23:00 (UTC)

Latest Comments

altermetax commented on 2025-04-28 19:10 (UTC)

A suggestion: is there any way to make the PKGBUILD use the Yandex API to generate the source link just-in-time?

Gallifreyan commented on 2024-05-14 06:53 (UTC)

thank you for keeping this up to date. The idea with a webservice sounds great to me; there probably is a teeny percentage of users with user-defined makepkg.conf who disallow redirects, but I guess sacrifices could be made

bulatovv commented on 2024-05-14 00:07 (UTC)

I've updated the upstream link to the English one!

I don't think I'll host the deb package somewhere because it's probably against Yandex's Terms of Service. Yandex probably won't be very happy if their package is distributed from some third-party host. Especially the one that's "not actually supported on Linux" (although it's listed on their official installation page and even added to the English version recently).

It's not hard for me to update the link in the sources. It's performed automatically by a cron job. It's a bit clumsy, with its really long git history, but it works. What I can actually do to avoid every-2-hours commits is to host a basic web service that will redirect any request to the current actual temporary Yandex disk link. If I read the source code correctly, makepkg uses curl with -L options, which allows it to follow redirects. It's not hard to do, but it's the same kind of hackery as the current approach with the cron job, and looks even more like a 3rd-party upload.

Gallifreyan commented on 2024-04-01 14:13 (UTC) (edited on 2024-04-01 14:13 (UTC) by Gallifreyan)

  1. The English help page now also lists the download link.
  2. I messaged their support about possibly providing a more direct download link. They replied that Linux isn't officially supported at the moment (that tracks, last update is 2023.06), so I guess that's a no.
  3. Maybe you could move the file to another place, if AUR's rules permit? Just to save yourself the headache of having to update the PKGBUILD

bulatovv commented on 2023-10-01 14:42 (UTC) (edited on 2023-10-01 14:47 (UTC) by bulatovv)

Noticed that the script was messing up the file name in the source. It totally broke the package. Fixed it.

bulatovv commented on 2023-10-01 14:13 (UTC) (edited on 2023-10-01 14:52 (UTC) by bulatovv)

  1. I wasn't aware of the English installation guide. It's possible that the link to the Linux version is not mentioned because the English page might not be as up-to-date as the Russian one. I'll update the upstream link to the English one once they add the Linux version there.

  2. Currently, you can only download the Linux version through a Yandex.Disk (you can find link in the Russian installation instructions). Unfortunately, you can't directly download the package via HTTP through this link. To obtain a direct link, you need to use the Yandex Public API. This direct link is used in the PKGBUILD file. The link is temporary, so I use a cron job to keep it updated in the PKGBUILD (you can see this in the change history). It's a bit of a hack, but it works.

fabiscafe commented on 2023-10-01 10:25 (UTC)

Hi. Maybe you have some answers I'm unable to find online. Do you know why the Linux version is not mentioned on the english side of the installation instruction, but on the russian one?

Why this links to a, what feels like a, 3rd party upload - file hosting solution?

This feels a bit shady tbh.