@honoriscreed: type 'stamp' into the search box in Options, turn off the last matching option. Come to the support group fb.com/groups/SocialFixerUserSupport

@coder-256 According to the git history, Tampermonkey went closed-source after version 2.9, in early 2013. So it has been that way for 6 years.

Opera's blacklisting of it was far more recent. I would like to hear their reason for doing so; especially as they did not blacklist the ID of the TM version found in their own 'store'.

I reported the listing to the Tampermonkey folks at https://github.com/Tampermonkey/tampermonkey/issues/635

Opera's blacklist of extensions is at https://extension-updates.opera.com/static/omaha/blacklist.txt and appears to be in chronological order of addition to the list. TM is the 2nd last entry; they must have added the last two at the same moment.

Since this was reawakened: the file I previously pointed to (https://extension-updates.opera.com/static/omaha/blacklist.txt) no longer exists; but TM is still blacklisted by Opera. It appears in my Preferences file -- certainly not by my preference, but injected there by Opera.

Opera! There is no reason to be blacklisting Tampermonkey non-beta.

@derjanb got some sort of response from them a long time ago, some sort of guff about TM being force-installed into people's Opera installations by some sort of malware, then used to run the malware's browser extension. Great. That is a bug, misfeature, attack, however you want to characterize it, ON THE PART OF THE MALWARE, not Tampermonkey!

And whatever that malware was, years ago, it is surely handled by people's antivirus etc. these days.

Please un-blacklist TamperMonkey non-beta, ID 'dhdgffkkebhmkfjojejmpbldmpobfkfo', from the Chrome 'store'. And the one from Opera 'store', but I don't know its non-beta ID as you've hidden it in the web UI.

See also DNAWIZ-49270; github.com/Tampermonkey/tampermonkey/issues/635

There were also comments about it on some of the beta blog posts, but those posts now have zero comments at all (https://blogs.opera.com/desktop/2019/01/opera-59-0-3187-0-developer-update/#comment-4270524260) -- ???

BTW @derjanb you said the Opera 'store' edition would update alongside the Firefox edition, about every 3mo. https://addons.opera.com/en/extensions/details/tampermonkey-beta/ is on 4.13.6138, updated 2021-06-22, while FF is on 4.16.6160, updated 2022-04-05.

BTW @derjanb you said the Opera 'store' edition would update alongside the Firefox edition, about every 3mo. https://addons.opera.com/en/extensions/details/tampermonkey-beta/ is on 4.13.6138, updated 2021-06-22, while FF is on 4.16.6160, updated 2022-04-05.

Since this was reawakened: the file I previously pointed to (https://extension-updates.opera.com/static/omaha/blacklist.txt) no longer exists; but TM is still blacklisted by Opera. It appears in my Preferences file -- certainly not by my preference, but injected there by Opera.

Opera! There is no reason to be blacklisting Tampermonkey non-beta.

@derjanb got some sort of response from them a long time ago, some sort of guff about TM being force-installed into people's Opera installations by some sort of malware, then used to run the malware's browser extension. Great. That is a bug, misfeature, attack, however you want to characterize it, ON THE PART OF THE MALWARE, not Tampermonkey!

And whatever that malware was, years ago, it is surely handled by people's antivirus etc. these days.

Please un-blacklist TamperMonkey non-beta, ID 'dhdgffkkebhmkfjojejmpbldmpobfkfo', from the Chrome 'store'. And the one from Opera 'store', but I don't know its non-beta ID as you've hidden it in the web UI.

See also DNAWIZ-49270; github.com/Tampermonkey/tampermonkey/issues/635

There were also comments about it on some of the beta blog posts, but those posts now have zero comments at all (https://blogs.opera.com/desktop/2019/01/opera-59-0-3187-0-developer-update/#comment-4270524260) -- ???

Hi,

TLDR:

(1) change .deb metadata to depend on libgbm1 >= 8.1~0 [like .rpm]
(2) Linux .deb downloader sends 68.0.3618.5, despite ...18 being shown here

===

I am unable to install opera-beta 68.0.3618.5 (nor opera-developer 69.0.3623.0) on my Linuxmint 17.3 system. (Not beta 68.0.3618.18, because the server sends 68.0.3618.5; not developer 69.0.3630.0, because this version wasn't built for Linux).

Installation fails due to a new package dependency on 'libgbm1 (>= 17.1.0~rc2)'. Previous Opera versions I installed (opera-beta 67.0.3575.28, opera-developer 68.0.3590.0, and all 357 versions I have .debs of, as far back as opera-beta 43.0.2442.21) did not call for libgbm1 at all.

My system has libgbm1 10.1.3-0ubuntu0.6. I converted the RPM build of 68.0.3618.5 to DEB with alien, and the converted package only calls for 'libgbm1 (>= 8.1~0)', well within the range of my system.

Also worth noting: Google chrome-beta 81.0.4044.69 and chrome-unstable 82.0.4085.12 install happily. These are respectively newer than the base versions used in the current Opera beta & developer packages.

===

Yes, the system's grossly out of date. But earlier releases installed fine; this is caused by an unnecessary change in your build environment. Your RPM build environment says only 8.1~0 is required; please change the DEB packaging manifest to the same.

I did not install the RPM as I do not wish to step outside the system's package manager and establish a permanent exception I would have to maintain.

@honoriscreed: type 'stamp' into the search box in Options, turn off the last matching option. Come to the support group fb.com/groups/SocialFixerUserSupport

@coder-256 According to the git history, Tampermonkey went closed-source after version 2.9, in early 2013. So it has been that way for 6 years.

Opera's blacklisting of it was far more recent. I would like to hear their reason for doing so; especially as they did not blacklist the ID of the TM version found in their own 'store'.

I reported the listing to the Tampermonkey folks at https://github.com/Tampermonkey/tampermonkey/issues/635

Opera's blacklist of extensions is at https://extension-updates.opera.com/static/omaha/blacklist.txt and appears to be in chronological order of addition to the list. TM is the 2nd last entry; they must have added the last two at the same moment.