ArcticFoxie/NotHereToPlayGames -- 360Chrome v13.5.2044 rebuild 2

[NotHereToPlayGames]

3 hours ago, UCyborg said:

but works with BYPASS FILTERS button on.

I have my Proxo config call up a .txt file for domains to bypass and Google Drive is one of the bypassed domains.

[rereser]

google is rolling out the new chrome extensions webstore site.
"chrome.google.com/webstore" redirects to "chromewebstore.google.com"
with an extension like "cookie keeper 0.2.4" you could delete the new "chromewebstore" cookie to get the old site back.
download : https://www.crx4chrome.com/crx/47259/  ("Download Crx File from Crx4Chrome" is the only link working)
but lately that does not work anymore for most extensions installed.
the old site is still up and can be reached through this page : https://webextension.org/listing/access-control.html (no need to install)

this script will let you download extensions if you click the "add buttom" but you will have to install the crx files manually.
--------------------------------------------------------------

// ==UserScript==
// @name         Chrome New Webstore make available for all web browsers which support it
// @namespace   https://greasyfork.org/en/users/85671-jcunews
// @version      1.0.1
// @license      AGPL v3
// @author       jcunews
// @description  Make extensions in the new version of Google Chrome Webstore be available for all web browsers which support it
// @match       https://chromewebstore.google.com/*
// @grant        none
// ==/UserScript==

(t => {
  function chk(a, b, c) {
    if ((a = location.pathname.match(/^\/detail\/([^\/]+)\/(.*)/)) && (b = document.querySelector('section>div>div[data-is-touch-wrapper]>button:not([data-forall])'))) {
      b.dataset.forall = 1;
      b.disabled = false;
      b.addEventListener("click", () => c.click());
      b.appendChild(c = document.createElement("A"));
      c.style.display = "none";
      c.href = `https://clients2.google.com/service/update2/crx?response=redirect&prodversion=100.0&acceptformat=crx2,crx3&x=id%3D${a[2]}%26uc`
    }
  }
  (new MutationObserver(() => {
    clearTimeout(t);
    t = setTimeout(chk, 200)
  })).observe(document.body, {childList: true, subtree: true});
  chk()
})()

-------------------------------------------------------------------------
script source : https://greasyfork.org/en/scripts/479807-chrome-new-webstore-make-available-for-all-web-browsers-which-support-it

Edited November 16, 2023 by rereser

[Hunterw]

On 10/10/2023 at 1:58 AM, NotHereToPlayGames said:

edit:  kind of does make me curious, what year/version did Mozilla switch from "favorite" to "bookmark"?  what year/version did Chrome switch from "favorite" to"bookmark"?  what year/version did Opera switch from "favorite" to "bookmark"?

i kind of suspect that "all" browsers used "favorite" back in the day, hmmm...

I got to give up on reading these dozens of pages but, while we're flogging this horse, before I used IE I used Netscape, and they always used "bookmarks." So AFAIK IE/Edge is the only browser to use favorites. Which was a hugely influential browser, to the extent that I regard the terms equally even if everyone has actually been saying "bookmarks" all this time since then.

[Milkinis]

On 11/16/2023 at 10:13 AM, rereser said:

google is rolling out the new chrome extensions webstore site.

''Users impacted by the rollout will see Manifest V2 extensions automatically disabled in their browser''

https://developer.chrome.com/docs/extensions/migrating/mv2-sunset/

disabled ? what the heck !!

so all of my extensions will become unusable or can they be used under developer mode ?

this or any other web browser without extensions is dead in the water

[Dixel]

16 hours ago, Milkinis said:

''Users impacted by the rollout will see Manifest V2 extensions automatically disabled in their browser''

https://developer.chrome.com/docs/extensions/migrating/mv2-sunset/

disabled ? what the heck !!

so all of my extensions will become unusable or can they be used under developer mode ?

this or any other web browser without extensions is dead in the water

Simply add this command line flag.

--enable-features=ExtensionManifestV2Availability 

It will work for now, when they remove it, no one knows.

[NotHereToPlayGames]

14 hours ago, Milkinis said:

disabled ? what the heck !!

so all of my extensions will become unusable or can they be used under developer mode ?

this or any other web browser without extensions is dead in the water

Users of UNGOOGLED versions are not affected.

 

57 minutes ago, Dixel said:

Simply add this command line flag.

--enable-features=ExtensionManifestV2Availability 

It will work for now, when they remove it, no one knows.

Thanks.

[UCyborg]

This browser doesn't even know about MV3 extensions so they (MV2 ones) should continue to work I think. Presumably the older ones may continue to be available on https://www.crx4chrome.com/, at least those that are there now.

But I have a feeling y'all forget about old MV2 extensions the same way you've forgotten about 360Chrome 11.

Edited November 19, 2023 by UCyborg

[NotHereToPlayGames]

But this browser does "phone home" to the Chrome Web Store.

Granted, I would have to experiment because I've never actually used any Chrome Fork that isn't "ungoogled" in some form or another.

For members that do use the "regular" version versus the "ungoogled" version, does your extensions "update" or notify you that an update is available?

If so, then that is at least the first sign that your setup is talking to the Chrome Web Store.

If a line of communication is open, I wouldn't doubt in the least that the Chrome Web Store has (or will soon have) a means to disable MV2 extensions.

But as mentioned, I would need to experiment.

 

ps - I still use 360Chrome v11.  Not as much as v13.5, of course, but still three or four times more frequently than New Moon 27.  

[Dixel]

3 hours ago, NotHereToPlayGames said:

For members that do use the "regular" version versus the "ungoogled" version, does your extensions "update" or notify you that an update is available?

I'm 100% certain, 1030 did update my uBlock 1.36 to 1.43 or 1.42 (quite some time ago). I can't say anything about 2044, sorry.

[Dixel]

4 hours ago, UCyborg said:

This browser doesn't even know about MV3 extensions so they (MV2 ones) should continue to work I think.

"Looking ahead: Manifest v3"

"In 2019 we will introduce the next extensions manifest version. Manifest v3 will entail additional platform changes..."

https://blog.chromium.org/2018/10/trustworthy-chrome-extensions-by-default.html

[Milkinis]

1 hour ago, NotHereToPlayGames said:

If a line of communication is open, I wouldn't doubt in the least that the Chrome Web Store has (or will soon have) a means to disable MV2 extensions.

This is what they do with Android powered phones in order to remove harmful apps that have been deleted from the Play Store

https://developers.google.com/android/play-protect

so long as Play Protect is disabled in the phone side they can't remotely wipe anything out

 

 

 

 

 

 

[Milkinis]

1 hour ago, UCyborg said:

This browser doesn't even know about MV3 extensions so they (MV2 ones) should continue to work I think.

thinking about this (some if not all) extensions that get removed from the chromestore stop working on the browser

https://chrome.google.com/webstore/detail/hompjdfbfmmmgflfjdlnkohcplmboaeo

 

[UCyborg]

10 hours ago, Dixel said:

"Looking ahead: Manifest v3"

"In 2019 we will introduce the next extensions manifest version. Manifest v3 will entail additional platform changes..."

I think it was already discussed at some point, isn't this browser just one or two versions behind (Chromium version) the one that started supporting Manifest V3 extensions?

[XPerceniol]

Hi @NotHereToPlayGames ... its been a while but I'm now getting back into the swing after being away for a very long time and I forgot a lot. Ugh, you can read in the Cafe as I addressed it.

Your newest browser works quite well out of the box.

All the best...

~Sal

Edited November 20, 2023 by XPerceniol

[XPerceniol]

On 11/3/2023 at 12:44 PM, NotHereToPlayGames said:

I would say that you are much better off with build 1030 over 2044.

With each and every new "upstream" build, all that was really added was just more and more telemetry to track down and remove.

1030 uses the v86 engine.  2044 uses the v86 engine.  You don't really gain anything but "risk" by using 2044 over 1030.

2036 was tested by a larger audience so higher probability of finding unwanted connections so it should be trusted above 2044.

I'm sorry, are you going to update those builds? Perhaps I misunderstood, mind is mush.