NotHereToPlayGames

Thanks. Bottom line - the conspiracy theory that somebody shut down somebody else's project is just that, a conspiracy theory.

I just ran into that also. I guess I should have read all of my unread's before posting, lol.

I'm not finding a DOWNLOAD. Only a "source code" zip which unzips to a useless-to-me "README.md".

Cool !!! So does it reduce RAM footprint for a no-tab bare-minimum browser-only?

That's the wrong list, try this one:

I have. Since January or February. The solution that works for me is to *NOT* use uBO for blocking YouTube ads. *NONE* of the "lists" I could find (nor assistance here at MSFN, but a big thanks to those that did offer assistance) were LONG-TERM. YouTube would break those fixes within weeks, if not days. I found TWO extensions that worked for me, but I have opted for this one as the best solution per my needs - https://helpcenter.getadblock.com/hc/en-us Bear in mind, I've only tested in Chrome-based but this extension is available for Mozilla-based. ONE list and one list ONLY:

No. It's not the same "series" / "branch". 360Chrome has a "Safe Browser", "Secure Browser", and "Extreme Explorer" variations.

I thought they were supposed to work on seven and higher. But I have not tried in Win7.

You should only need to load the search engine then click into the search box. It's the clicking in the search box that "triggers" the "EventListener" for the OpenSearch search engine to be added to the browsers search engine list. If the search engine does not utilize OpenSearch then you will have to add the search engine manually.

??? ??? ??? Um, are we supposed to know what that is? Looks like nitrous oxide to me.

Agreed!

Oh man, you edited out the part I was going to comment on, lol. re: 256 MB spare -- it's because some people eat their cereal with a fork and don't realize that a spoon works better. There would be no MSFN without these types of people, the folks that use the wrong tool for the job then come here to get that FORK (pun intended) to do what the spoon has no issues with.

axel https://www.collinsdictionary.com/dictionary/english/axel

That seems to be true today but it was certainly not true approx three years ago or so. I used to have a Chase account but no longer do because of their you-must-upgrade-your-browser constant and incessant nagging. As a "secondary account", I could boycott their business. But all of my utilities are basically monopolies, I have ONE choice if I want WATER at the house, ONE choice if I want CABLE at the house, ONE choice if I want ELECTRICITY at the house, ONE choice if I want HEAT at the house. I searched for several login pages and they all do lack Facebook today, that did not used to be the case, their own login page used to connect to Facebook! I can actually remember a time when Chase's login page had over 120 scripts being ran! I count via Proxomitron as it will count each and every individual 'script tag'. The top-hit as far as an internet search for the login "front page" (I no longer remember what URL that I used when I had a Chase account) currently only shows 21 scrips and no Facebook connections.

As are SSL "certificates". But I digress.

Sometimes the "not a valid win32 app" error is nothing more than then .exe not properly "signed".

Same here. Just downloaded. Will be a weekend or two before I get around to trying it out.

And Facebook... ?

Your results? I've tested this flag and NONE of the SEVERAL quantifiable measurements (ie, the only real way to truly eliminate Placebo Effect) shows any "considerable" performance difference.

Your profile cites Win7 x64. So you have two 360Chrome options newer than v13.5 (Chrome v86). There is 360Chrome v22.3.3015 which is Chrome v122 (same as Thorium and Supermium). But there is also 360Chrome v22.1.1084 which is Chrome v119. I've only been working with the two in seemingly rarer and rarer free time, but I've come to see the Chrome v119 as probably my "next primary" as far as my system.

The browser is from here -- https://github.com/weolar/xpchrome/releases It was released on November 21st of the year 2023. The "one year" is discussed here -- https://github.com/weolar/xpchrome/issues/11#issuecomment-1817344497 The "one year" is *NOT* technically one year. The "first" time bomb "activation" (ie, the browser will crash at startup) is August 1st of the year 2024. That is 8 months and 11 days, or 254 days, which is not, by any country's definition, "one year" -- https://www.timeanddate.com/date/durationresult.html?m1=11&d1=21&y1=2023&m2=08&d2=01&y2=2024 But the "time bomb activation" is improperly coded - it will crash on August 1 of 2024 it will crash on September 1 of 2024 it will crash on October 1 of 2024 it will crash on November 1 of 2024 it will crash on December 1 of 2024 But it will NOT crash on - January 1 of 2025 February 1 of 2025 March 1 of 2025 April 1 of 2025 May 1 of 2025 June 1 of 2025 July 1 of 2025 But then it WILL crash on - August 1 of 2026 September 1 of 2026 October 1 of 2026 November 1 of 2026 December 1 of 2026 But it will NOT crash on - January 1 of 2027 et cetera

Ah, thank you! That explains it. "Segoe UI" on XP (and 7) gives me migraines. I've not had any issues with "Segoe UI" on Win10.

I prefer the GUI in 122. But it's still "not right" on my systems. Unsure why nobody else is seeing the left edge of GUI fonts being cut off. 122 is also faster, but not by enough that typical browsing would likely even notice.

Yes. It is based on Chrome v122.

I definitely never used that word, lol. But agreed, no title bar in 10 Supermium keeps "flashing" the true XP title bar's upper-right corner icons randomly, that's even more annoying then trying to mock 10's icons on XP. I've actually been porting 360Chrome v122 but it is 64bit and requires Win10. Maybe Win7, unsure. But cannot be ported to XP. This will give me a v122 with a skin of my own creation, with a title bar of my own creation, ungoogled, no telemetry, custom GUI, everything done with v86. But very likely will not become public, just a hobby on bad weather days. While being perfectly content with Official Ungoogled v114 for the time being. The web has become a "race". See if I can get my v122 ready in time before my checking account or billpay sites stop working in v114. Then do it all over again when v122 does the same thing and when "cutting edge" Chrome/Chromium will be v150+. I've never needed, nor wanted, the latest and greatest. I stuck with v86 for as long as I could. I'll stick with v114 for as long as I can. Already preparing for v122 as my next.