hoverzoom VS electron-builder

I will leave this as a gallery of emails with offers to buy extension hoverzoom: https://github.com/extesy/hoverzoom/discussions/670

Sidenote: The "collaboration" offers come from time to time even to non-extensions projects, if they are reasonably widely used. E.g. simple tools (rather widely used suite of android apps recently sold).

> Manifest V3 will stop this by limiting what Google describes "remotely hosted code." All updates, even to benign things like a filtering list, will need to happen through full extension updates through the Chrome Web Store. They will all be subject to Chrome Web Store reviews process, and that comes with a significant time delay.

So the author can't think of any other reason for this change other than to "slow down ad blocker updates"

Well how about stuff like this: https://github.com/extesy/hoverzoom/discussions/670

Where an extension dev details offers to "monetize" his app and basically perform a bait and switch and make it malicious.

These type of offers are actually quite common. See this[0] and the discussion[1]. I try to stick with only the most popular of extensions in the hope that any malicious changes would be widespread news, but it is still a gamble.

[0] https://github.com/extesy/hoverzoom/discussions/670

[1] https://news.ycombinator.com/item?id=37066680

As a maintainer of a semi-popular chrome extension[1], I receive so many buy-out offers that I started publicly collecting them[2] for everyone to see.

[1] https://chrome.google.com/webstore/detail/hover-zoom%20/pccc...

[2] https://github.com/extesy/hoverzoom/discussions/670

Also, here's a open source alternative.

I don't want to download a sieve from a russian forum. Hover Zoom+ is working fine.

Hover Zoom+: https://github.com/extesy/hoverzoom/ (this is the open source one, not the old one with malware)

The last step for each platform's build process is to upload the app to our GitHub releases repository. We automated this step from the beginning, but when we started creating builds for the new M1 chip Macs, we had to add a manual step. This involved merging files needed for the auto-updater to work with the M1 builds.

https://github.com/electron-userland/electron-builder/issues... that issue kinks to the PR that adds the automation.

It's a non-trivial thing to test, since it involves so many secrets and the notarization step can take over an hour, so I don't expect anyone here to actually want to look into it.

My original comment really was just venting my frustration, not a cry for help (but I might be crying soon if I can get to the bottom of this!).

> The ‘autoupdater’ does three things,

>

> - check the app for updates (using Sparkle)

> - report any crashes (using Sentry)

> - start a local HTTP proxy on port 40701 (this can be changed using the configuration json file in the app bundle).

>

> The latter is of course, not to be expected of any app on the machine, especially not one that just claims to be an auto updater.

Well, yes. And no.

For example, electron-builder [^0], a popular framework used for Electron app packaging and auto-updates, uses a local update server on Mac [^1] to add a more sane system backed by a more insane system, Squirrel.

[^0]: https://github.com/electron-userland/electron-builder

[^1]: https://github.com/electron-userland/electron-builder/blob/m...

The Project uses Electorn-Builder to package the app and Electorn-Updater to update.

You can read about this issue here: https://github.com/electron-userland/electron-builder/issues/7114

Ostara is based off of electron-react-boilerplate and uses electron-builder to package the application.

Install electron and electron-builder

I believe Visual Studio Code uses Electron and posts releases on a regular basis. Maybe check their A quick Google search for "electron build github release" turns up "Electron Builder" https://www.electron.build/ I don't really know though; I've never used Electron.

I also would like to have an NSIS installer so if it happens to package the Chromium executable along with my app, how can I accomplish that? I am using electron-builder.

We use electron-builder at work.