NotHereToPlayGames

Have you tried any of the 360Chrome releases? Here is the download link to my v12 -- https://www.dropbox.com/s/2r7r53j4i55iuyw/360Chrome%2012.0.1247.zip Here is the download link to my v13rev3 -- https://www.dropbox.com/s/qyyimm3h58r3963/360Chrome%202206%20rebuild%203%20-%20unran%20-%20MSFN.zip Humming Owl's releases -- https://msfn.org/board/topic/182876-360-extreme-explorer-modified-version/ My v12 has been rock-solid for YouTube. I have TRIED to crash it by loading twenty YouTube videos with all twenty playing 720 and with all twenty having audio on. I have not been able to crash v12 no matter how hard I try. Most tests are performed in XP x64 with 16MB RAM but I have also tested in XP x86 with 4MB RAM with twelve YouTube videos.

I was unaware of this version also. Found the Mypal mingw32 but couldn't find the Centaury mingw32. On the to-do list to give 'er a trial-run.

Regarding search engine financial gain, that is interesting indeed. Not sure how to estimate that "financial gain" - nor is it really any of my business, in my opinion, but there is some public-domain sites ( https://www.sitelike.org/similar/palemoon.org/ ) that do place a "value" which does I suppose at least put things in a little perspective. google.com = $3,335,302,900 duckduckgo.com = $5,100,900 opera.com = $1,261,700 mozilla.com = $894,900 kmeleonbrowser.org = $451,200 firefox.com = $145,200 mozilla-russia.org = $107,200 msfn.org = $40,700 maxthon.com = $25,900 palemoon.org = $19,000 basilisk-browser.org = $600 browser.360.cn = $100 rtfreesoft.blogspot.com = $0 binaryoutcast.com = $0 mozilla.org = $0 mypal-browser.org = $0 vivaldi.com = $0

Mypal source code has ALWAYS been EASY to find! I personally wouldn't mind a how-to guide on HOW to compile it myself. You can "claim" that they exist, such as this -- https://developer.palemoon.org/build/windows/ But has anyone here ever FOLLOWED those instructions -- they do not work. I've tried a dozen times in the last two years and I've always failed The Linux instructions might work, but I only dabble in Linux for GUI-something-different-FUN, I can't really "do" anything in it -- http://developer.palemoon.org/build/linux/

This is what is called a RED HERRING here in the US. It's an "attempt" at creating a LOOPHOLE in the "license agreement". Timely manner -- "I asked for it TWO MINUTES AGO and they haven't replied yet, this is a breach of our license." NO IT IS NOT, but "timely manner" can mean anything they want it to mean! Or so they think, try taking that up with a judge. "Timely manner" can mean ONE YEAR to one judge and ONE MONTH to another. But it does NOT mean "two minutes" to any judge on the planet! Reasonable means -- "I had to click three links instead of one, my time is too valuable to have to click three links!". Again, try taking that up with a judge, from any continent, from any planet. But anywhoo... It is extremely sad... I agree! I do, however, find myself ruling against Roytam on this one. We're probably not supposed to admit this out loud but please bear with me and allow a brief explanation. Look at how LONG this "issue" has been ongoing - and 'we' still have a download link with "palemoon" right in the name? The USERS of Basilisk/Serpent don't even know what to call it! The download link says basilisk, the about screen says Serpent. WE know what they are, but the newcomer does not - and that's where this whole thing started, many months ago, with no resolution whatsoever still to this day. I don't know who Binary Outcast is, but did Roytam releasing BNav axe Binary Outcast's project before he/she was even able to release his/her first beta version? But on the other hand, I also don't think (but I am no lawyer!) that Roytam has done anything where Tobin/Moonchild could issue a warrant for his arrest else I think they would have by now, that is the way this has all unfolded, the ongoing saga, no resolution whatsoever, no end in sight, ad nauseam. But feodor2 has followed all of those branding rules - from the beginning! EXCELLENT JOB, feodor2, KEEP UP THE GREAT WORK!

I never visit their site and hadn't realized it was "that" bad. The "why" is because too many people don't know the difference between "Pale Moon" and "palemoon". Look at the LINKS when you download a Roytam build - the link has "palemoon" right in it even if the "about" page might say something different. And Roytam released BNav before the project that it stems from was even released - if I have the history correct. Isn't BNav based on Binary Outcast's Borealis Navigator? Don't know on this. So it all comes down to "branding". But feodor2's Mypal followed all of the rules there, so not sure why Mypal is now lumped in with "palemoon".

For those new to Chromium-based browsers, they include a feature called "OpenSearch" and this feature automatically adds search engines that you use to your list of search engines. You'll see this list when you go to Settings -> Basics -> Search -> Manage Search Engines and they will show up in the "other search engines" section. For those using Tampermonkey / Violentmonkey / et alia, here is a User Script that will prevent "OpenSearch" search engines from automatically being added to your profile -- https://greasyfork.org/en/scripts/37186-disable-opensearch/code There is also this one (much more complex, have not tested this one) -- https://greasyfork.org/en/scripts/375216-block-opensearch-descriptions/code edit - removed image, no longer hosted on my Dropbox as I was running out of storage space...

@Montana Slim - Here is the download link to my v12 -- https://www.dropbox.com/s/2r7r53j4i55iuyw/360Chrome%2012.0.1247.zip Here is the download link to my v13rev3 -- https://www.dropbox.com/s/qyyimm3h58r3963/360Chrome%202206%20rebuild%203%20-%20unran%20-%20MSFN.zip

Forgive the bluntness, but not interested. All of these privacy concerns coming from a guy with an Instagram and Twitter account? If these sort of things concerned me as much as you want us to think they do you, then I WOULD NOT OWN A COMPUTER as opposed to being a tech-savvy geeky dude with SEVEN of them. I wish you the best, @Dixel. But I find these conspiracies, KGB rants, anti-Russian, can't-spell-Google, can't-spell-Cloudfare views to be too extreme for my blood. Maybe it's cultural and being from different countries? Maybe it's the Instagram/Twitter persona that I've never been accustomed to? No clue. But anywhoo...

DO NOT label me a Dem / leftist !!! Now then, "having said that"... Not wanting to share personal data with ad companies is not in-and-of-itself "extremist". I am 100% positive that my setup blocks 98%. Bending over backwards for that extra 2%, yep, I'll label that as "extreme". I do not own a horse and buggy and have no desire to live so "afraid" of GOOGLE and CLOUDFARE that I cannot even bring myself to spell them correctly Signing out for a couple of days to avoid the "toxic mood", life really is too short.

ps - I do not use my ISPs DNS. But nor do I visit anything that I would hide from my own mother.

I do not care to be that "extreme". I'm all for Privacy Rights - but as I've mentioned before - I'm a "centrist", I have no need for such "extremism". To each their own...

Awesome! Thanks for the feedback, I was very curious about XP SP2 x86. I did benchmark tests on all of the v12's and specifically chose this one as my base for my new rebuild based on those benchmark results. While it is one of the earlier versions of v12, none of the newer versions of v12 have a newer Chromium engine. The newer versions of v12 only add "bloat" (same goes for newer versions of v13 as far as that goes), the underlying "engine" is as new as it gets for v12. Another item to note when comparing v12 to v13 is that the Original Chinese, Russian Repack, my v13 releases, and @Humming Owl's v13 and v12 releases, the DNS over HTTPS (DoH) setting DOES NOT WORK (have only tested in XP). Whether that option is checked or unchecked has no difference on your DNS queries (the option exists in early v12's but it is not selectable so I have removed/hidden it from the GUI in my build). I don't use that "feature" by default anyway, but it was something that was observed when I was narrowing down what my next release was going to be based from. The only test sites I could find were these (did not spend a huge amount of time hunting) -- https://www.cloudflare.com/ssl/encrypted-sni/ and https://1.1.1.1/help You do need to set your DNS to 1.1.1.1 and the second link above showed no difference with the 360Chrome setting checked versus unchecked [did not test in Firefox as it too has a setting for DoH] (first link was not found until typing this post).

@Humming Owl - you may be interested to know that there is a v13 build 2256. Unsure of what is "new".

Due to recent YouTube crashes experienced on v13, I have opted to downgrade to v12 as my default-for-all. I have successfully opened twenty YouTube tabs in v12 on XP SP2 x64 and on XP SP3 x86. I have not tested on XP SP2 x86. Download link -- https://www.dropbox.com/s/2r7r53j4i55iuyw/360Chrome%2012.0.1247.zip

Still crashes. Waits until the 3rd tab instead of the 2nd -- https://www.dropbox.com/s/h4wq7elvjby5dk8/youBube.mp4 But I repeated the test two more times but without the video-grab and both of those crashed on the 2nd tab just as I was experiencing the other day. Did not install adblock for this test.

I haven't done that slipstream since Dec 2016. Not sure if links are dead or not, not sure if thread has been updated since. I may be missing a few updates from after Dec 2016 but I really don't feel "insecure" if I missed a few.

Here's the thread I used to create my updated XP x64 -- https://msfn.org/board/topic/105277-howto-create-a-fully-up-to-date-xp-x64-dvd-eol-feb-2016/

I agree! I know! I did not intend to imply that you did! Here, for the sake of an easier-to-follow discussion and a summary of how we got here. Here's how I recall it all unfolding. If I have the chronological order out of place, again, I apologize, but I'm generally pretty good at chronological events. One, there was a discussion between you, me, and perhaps a few others surrounding these embedded extensions and my notes recorded the following (it's in one of the other 360Chrome threads) -- 1 - mhjfbmdgcfjbbpaeojofohoefgiehjai PDF Viewer OFFSET 13022 2 - fjajfjhkeibgmiggdfehjplbhmfkialk CryptoTokenExtension OFFSET 15624 3 - gfdkimpbcpahaombhbimeihdjnejgicl Feedback to Gurgle (!) OFFSET 13882 4 - Chrome Web Store Cloud Print OFFSET 11562 5 - ahjtciijnoiaklcomgnblndopackapon Identity API Scope Approval UI at OFFSET 326728 Two, that discussion turned into me turning to ungoogled-chromium and which of these embedded extensions should remain in 360Chrome because they also remain in ungoogled-chromium. It was at this point where you cited (and I agree, mostly) your stance on ungoogled-chromium. I respect your stance! Three, I did not remove the entire list of discussed embedded extensions, I kept those that ungoogled-chromium has in their code and removed others (our list may be longer, I seem to recall a retired cloudprint one that I removed also). Our discussion, at that time, led me to remove SOME embedded extensions but KEEP other embedded extensions. I seem to recall even seeing that it took longer for 360Chrome to launch without the embedded extensions versus with them. Four, it was around this time that Humming Owl released notes where he removed all references to googleapis in v12. Five, with no adverse side effects from that experiment of removing all references to googleapis in v12, it was either Humming Owl or myself, don't recall in hindsight but it will be in that other thread, that all references of googleapis were removed in v13 - as an experiment. Six, with no adverse side effects reported, that experiment still holds and as of this point both Humming Owl and I have those refences removed in chrome.dll. Seven, discussions regarding registry entries surrounding esent.dll. It was at this point where I suggested to Humming Owl to NOT remove references to esent.dll because ungoogled-chromium has the exact same esent.dll references. To the best of my knowledge, Humming Owl reverted his esent.dll removals, unsure on this. I never removed any esent.dll references in my own build. Eight, several weeks pass and a discussion regarding "connections" when a user compares my build to Humming Owl's build. This is when I discuss the command line startup that would prevent those "connections" on Humming Owl's build. Nine, Humming Owl chimes in and cites he is aware of those "connections" but that he left them intentionally for something called Chromecast. Ten, I cite that Chromecast is likely already broken because of a blanket-removal of all references to googleapis. That's pretty much how I saw it all unfold. I'm on MSFN daily, I doubt that I missed anything.

Consider it this way, a web site called "Greasy Fork" is an excellent source for Greasemonkey / Tampermonkey / Violentmonkey user scripts. It is very common for user scripts to have an @require setting where a googleapis is downloaded ONCE and stored locally for that user script to use over and over and over. The user script only needed to download it ONCE. But if you don't use the @require setting then our web browser now has to download it EVERY time instead of just ONCE. Just thinking out loud - I do have all googleapis references removed in my own build. But I do have to wonder, did I err on the side of safety? Or on the side of breaking things that I just don't know are broken because I haven't tried the right extension or visited the right web site? Or, by removing the googleapis LOCALLY, did I create a web browser that now has to FETCH that googleapis instead? Wouldn't it be better to have it LOCALLY then have to FETCH it every time the web browser / web site needs it? Hhmmm...

Agreed! I kinda pointed this out when we were discussing esent.dll (page 11 of this thread). I really think we can not axe things just for the sake of "warm fuzzies" when we don't know 'everything' that entries like "googleapis" and "esent.dll" really-and-truly DO. I think some peoples' paranoias tend to get ahead of themselves and it becomes very easy to create a "working" browser that has BROKEN FUNCTIONALITIES that only come to the surface months later when testing a new extension. So was that browser really "working" to begin with? I'm exaggerating (slightly). But we really cannot let our paranoias turn 360Chrome into something that is "broken". I like ya @Dixel so I am not casting this net over you (more in a second, we are of the same feather!), though to discuss I do have to bring up something you've said in the past. I once SUGGESTED that some of the googleapis should STAY in 360Chrome BECAUSE they also exist in "ungoogled-chromium". Your reply was something along the lines of disrespect towards the "ungoogled-chromium" project because of their use of the word "ungoogled". But my suggestions remains - we should not be removing something like "googleapis" in the dozens upon dozens of locations where it exists in chrome.dll just for the same of a "warm fuzzy". Although, having said that, and back to my same-feather reference earlier, I do err on the side of caution and I remove all googleapis references in my own rebuild -- but what did I "break" by doing so? Because they were there for a reason and I do not know those reasons. I do know that all of my extensions work, my visited web sites work, et cetera. But rest assured, "something" is BROKEN just by blindly replacing all "googleapis" references without really and truly knowing why they are there. Our collective paranoia might have, just possibly, taken us a wee bit TOO FAR and we might have, just possibly, stripped out more than we "should" have all because we kept looking up in the mirror to see if somebody was following us. If you pay too much attention to that rear view mirror, you will run over a child running into the street. But I digress...

I don't use Chromecast service, so I cannot confirm - but wouldn't this service be broken by the below replacement/modification listed in your v13 build 2250 notes --

I have not verified, but my hunch is that if you launch Humming Owl's with the below command line switch, then his won't connect to Google at launch -- --disable-background-networking

Good catch! I see that now and didn't notice it at first. And something like "gstatic" could easily be a common denominator. My NoScript and uMatrix isn't showing anything being blocked from gstatic here at MSFN "at this instant" (which has a tendency to crash here lately also!). But even though my Stylus blocks the ads here at MSFN, I have a hunch that if I monitor network traffic that I will see gstatic connections here at MSFN (just a hunch, have not dived that deep yet). So I can easily see how some new ad or cookie traffic to and from gstatic can be the cause for crashes all of a sudden. But... Isn't gstatic "required" in order to log into YouTube (I don't have a YouTube login)? So it would seem that a blanket-ban to gstatic isn't really the best solution if indeed that is the root cause. For now, I'm satisfied that v12 isn't effected and I don't mind dropping to v12 for my default-for-all once I complete my modifications/tweaks/rebuild/repack of v12.

Thanks, I will try that "YouTube Redux" eventually. My Chromium v49 on XP uses an extension called "Enhancer for YouTube" which will also stabilize and tame YouTube crashes on v13. However... It's not just YouTube that used to NEVER crash any of the v13 builds but now I am getting crashes with all of the v13 builds. Dixel's v13, Humming Owl's v13, the Russian Repack v13, the Chinese original v13 - they all have major crash issues all of a sudden on XP. When those crashes started happening on "this" computer, I thought maybe a codec or something got corrupted. But I'm getting v13 crashes on XP on five different computers, all with different "levels" of Windows Updates, some with different versions of K-Lite Codec Pack, some without. I really wish I could track it down. I have honestly NEVER had YouTube crashes until just a few days ago. But... It's not just YouTube. YouTube is by far the easiest to "replicate" the crashes. But even this very MSFN forum will now crash on occasion! Axe profile completely, fresh XP install, no extensions installed, you name it, v13 has a tendency to crash all of a sudden. I've been unable to track down any realy "culprit".