Forced updates mean I must re-downgrade after every launch about jitsi-meet-electron HOT 11 CLOSED

First of all thank you for highlighting this, this slipped through on my end. I have now added it as a note to the release

from jitsi-meet-electron.

To head off one possible suggestion of possible workaround...

Previous suggestions of Flathub and HomeBrew don't work because Flathub is for Linux, and both of these have already bumped to 2023.11.0, anyway.

I have long used MacPorts, so I tried to install the jitsi-meet-electron port which still shows as being 2023.10.0, but it fails to build, without useful error. (I've also logged a bug on the port.)

from jitsi-meet-electron.

Please stop posting the same issue over and over again.

You are using an operating system that has been without any support from Apple for over 2 years now, that includes security updates.

We cannot support your use case.

from jitsi-meet-electron.

@saghul — I am currently trapped on macOS 10.14 due to mission critical abandonware, which breaks with the update to macOS 10.15. I would LOVE to upgrade, I assure you, but I cannot.

I have found and hereby offer a workaround for the worst Jitsi pain, for others who may run into this issue: install Little Snitch, and when it alerts that Jitsi Meet.app wants to connect to githubusercontent.com, DENY it. This will silently prevent the new version from being discovered and downloaded on this and subsequent Jitsi sessions. So far (one meeting), it doesn't seem to have caused any problem with active use.

from jitsi-meet-electron.

That can work. Now that we reached the point of no return you could just make a custom frozen in time build for yourself too.

from jitsi-meet-electron.

you could just make a custom frozen in time build for yourself

I'd love to know how to do that. At first blush, it seems I would need to disable the phone-home code somehow, in addition to running whatever compiler, etc., (all of which I have installed, just minimally used)...

At this point, I'm little more than a script kiddie. My primary coding language is English, though I have ever debugged a little Pascal and a little C and even written some AppleScript and shell.

from jitsi-meet-electron.

You can follow these steps: https://github.com/jitsi/jitsi-meet-electron#building-the-production-distribution

from jitsi-meet-electron.

Note that that anchor is hidden by default. Readers must expand the Show building instructions section.

Then, the "first step" is not documented beyond "Install Node.js 16 first", which I think would benefit by at least a link to relevant instructions from that crew. I did Google that f'ing thing, and that got me to nodejs.org where I found that Node.js 16 is on its last last last legs. Still, I downloaded and installed the relevant node-v16.20.2.pkg. Guidance beyond that was found on a third-party site, but of course, it's focused on getting the latest-and-greatest version, not this multi-year-old v16, so I'm not sure I should sudo npm install npm --global // Update the npm CLI client. I'm also pretty certain that export PATH=/usr/local/git/bin:/usr/local/bin:$PATH doesn't have the desired effect on macOS, and that some extra hoops need to be jumped through to adjust $PATH and other environment variables.

All that said, if I had reached the point of building the production distribution — so far as I can see, I would have exactly the same issue of auto-updates as I have with the prebuilt download.

I think I am best off living with blocking Jisti Meet.app's access to githubusercontent.com, until and unless there are real step-by-step guides for near-absolute beginners.

from jitsi-meet-electron.

Oh right I forgot the most important part 🤦

Edit package.json and drop the project URL. That is what is used for checking for updates.

from jitsi-meet-electron.

I wonder whether config.json might be put to use for Jitsi Meet, as it can be to prevent updates of Element.app?

from jitsi-meet-electron.

We don't use that file ourselves AFAIK. The update URL gets bundled with the app and it's taken from package.json.

Since you will essentially be keeping a fork, edit the file, remove the URL and the build won't self-update.

from jitsi-meet-electron.