How i can block IPFS Update?

[ZeroCool22]

I want to use the 0.29.0 version and not want it to get updated, what file i need to block in the firewall?

[ZeroCool22]

Someone?

[whizzzkid]

Hey @ZeroCool22, apologies for the slow response, I don't think there is a config to prevent automatic update (that can be added, but that would then increase fragmentation of kubo runtimes, which is not ideal)

That being said, are you comfortable building projects locally? If yes, then I think you can comment out this line and build ipfs-desktop locally, that should disable background checks and hence make it stay at the version you'd like.

Let me know if you need further assistance.

[ZeroCool22]

Hey @ZeroCool22, apologies for the slow response, I don't think there is a config to prevent automatic update (that can be added, but that would then increase fragmentation of kubo runtimes, which is not ideal)

That being said, are you comfortable building projects locally? If yes, then I think you can comment out this line and build ipfs-desktop locally, that should disable background checks and hence make it stay at the version you'd like.

Let me know if you need further assistance.

Mmm, i never compiled anything i just use Visual Studio Code for html and css (not JS yet), how i do it?

[whizzzkid]

@ZeroCool22 you can find the guide to build from source here.

Once you have the project cloned locally, you can run the build command to run local ipfs-desktop.

[SgtPooki]

@ZeroCool22 in #2617 you say there are errors that are too big of a problem for you to update. Can you share more information and logs, or relevant existing issues?

We want to fix all the errors, but without information from users who are experiencing them, we can't address them.

As far as blocking the auto-update, that is counter-intuitive to deploying fixes that are needed for resolving errors anyone experiences. The right solution is to report the error with as much information as needed so we can address the root problem.

If we need to hop on a call, let me know, you can email me at my username at protocol.ai, or https://calendly.com/sgtpooki.

[waltzz92]

Has any progress been made on this? I too would like a version of IPFS Desktop with automatic updates disabled. As shown by the Windows OS, its no secret that updates break things. Even worse are bad features being forced on the user by the developer, as is the case with Google's Manifest V3. It would be best if users have full control over the software on their machines.

Unfortunately, I'm not familiar with programming. If someone could make the current Windows version of IPFS Desktop without the update feature, that would be great.

[whizzzkid]

Thanks for the feedback @waltzz92, even if we added the feature to disable autotmatic update today, you'll still have the latest version which won't be updated going forward. i.e. you'll have all the bugs that ship today with no opportunity to fix them. I feel the sentiment here was to have an old version which won't update. You can always build an old version from source.

I would like to re-iterate what @SgtPooki mentioned:

As far as blocking the auto-update, that is counter-intuitive to deploying fixes that are needed for resolving errors anyone experiences. The right solution is to report the error with as much information as needed so we can address the root problem.

I disagree with your statement:

its no secret that updates break things

That would not be ideal as a lot of things change pretty fast, i.e. having fragmentation in the ecosystem will only cause more problems and compatibility issues. I feel most of these issues were fixed with the latest release, if not, please report those as newer issues and someone can look into those.

[github-actions]

Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.

[SgtPooki]

@waltzz92 @ZeroCool22 we will add an option in the IPFS-Desktop config.json to disable autoUpdates, but won't provide a UI element for toggling it, so you will be able to disable auto-update, but only via modifying the config.json file.

This will:

1. prevent users who don't know exactly why they're doing it from shooting themselves in the foot (with an easy UI toggle)
2. allow users who are adamant about preventing auto-updates to do what they want
3. be easy to implement (simple config read and wrapper around a few lines in src/auto-updater/index.js)

cc @whizzzkid