NotHereToPlayGames

I don't use the "latest and greatest" NoScript, I intentionally use an older version - v11.2.3. No need to add it if you can already block scripts via uBO. As a rule of thumb, I don't allow scripts and when I visit a site that has twelve of them, I narrow it down to the one or two or three that are "required" then continue to block the remainder. I seldom let a web site run willy-nilly and pretty much never let a web site load as many scripts as its authors thought were necessary. I wouldn't necessarily call it an "incompatibility" issue. I tend to think of those as more along the lines of "clever cloaking" then "incompatibility". The web site is trying to "force" you to use a newer web browser by employing tricks that I bet they are well aware of that prevent the site from functioning on 'older' web browsers. I say that because I have witnessed it. One of my vendor's accounts-payable site has a .css overlay that prevents me from seeing what's "under" the overlay and the .js that loads the .css has "incompatible_browser" right in the title of the .js file! It's a pop-up overlay telling me to use a newer web browser and then a link to log out. Little do they know that I've accessed that accounts-payable site from XP for the last two years where they think they were clever enough to prevent their customers from doing so. I just block the .js that loads the .css and whoala, In Like Flynn.

Noted, thanks. Not yet updated in either of today's updates.

Download link for v13.5.1030 Alpha_10 added to first post. Only file change since Alpha_9 is chrome.dll. Only specific and precise location modifications, no throwing of a wide net and "replace all" generic types of replacements. Telemetry removals of following items - upext.se.360.cn ext.se.360.cn se.360.cn a.tbcdn.cn dmp.360.cn i.360.cn dd.browser.360.cn (unicode) cloud.browser.360.cn (unicode) ext.chrome.360.cn (unicode) down.360safe.com (unicode) se.360.cn (unicode) i.360.cn (unicode)

Yeah, more of an illustration on how you can use the .ini to delete extension logs for extensions that don't need those logs from one session to the next. Those folder entries would be one or two of the extension I was using at the time.

Download link for v13.5.1030 Alpha_9 added to first post. Only file change since Alpha_8 is chrome.dll and minor addition to loader .ini. Only specific and precise location modifications, no throwing of a wide net and "replace all" generic types of replacements. Telemetry removals of following items - upext.chrome.360.cn ext.chrome.360.cn skin.chrome.360.cn api.chrome.360.cn yun.chrome.360.cn chrome.360.cn upext.chrome.360 dd.browser.360.cn sug.so.360.cn so.360.cn cloud.browser.360.cn site.browser.360.cn cdata.browser.360.cn extsign.browser.360.cn google-translate.browser.360.cn

I use the extended .ini from v13.2206-4 in my own copy (should not require modifications but I have not verified that as of yet). The Extension State depends on which extensions you use so I left that for the end user to decide/experiment for themselves, some extensions require the log file and some do not (when the log file contains browser history, I boycott that extension!). The only reason I reverted the .ini for the public release was because some users didn't like that cookies and passwords were not remembered from one session to the next (I personally do not let my browser remember my passwords).

Oops, forgot

Page loads fine for me in v12. BUT only with my default NoScript blocking .js on github.com domain! As soon as I set the github.com domain as "trusted" then I only get the blank-out. Everything on that site seems to function just fine with .js blocked, but since I don't normally visit it I guess I'm not 100% sure on that.

Download link for v13.5.1030 Alpha_8 added to first post. Only file change since Alpha_7 is chrome.dll. Only specific and precise location modifications, no throwing of a wide net and "replace all" generic types of replacements. Telemetry removals of following items - 224.0.0.251 210.52.216.4 123.125.54.234 106.39.219.43 101.226.4.6 101.199.103.206 s.f.360.cn dl.360tpcdn.com puv.tt.browser.360.cn hiya.browser.360.cn 95001111 crash.browser.360.cn (unicode) pvstat.qihoo.com (unicode)

Download link for v13.5.1030 Alpha_7 added to first post. Only file change since Alpha_6 is chrome.dll. Only minor and precise location modifications at this point, no throwing of a wide net and "replace all" generic types of replacements.

Note to self -- dark theme issues in special need of attention - Search Engines Manage Passwords Manage Autofill Import/Export Bookmarks Kernel Switcher Clear Browsing Data -> English Content Settings - plus all sub-containers Pop-up Exceptions Proxy Settings

I suggest using a PORTABLE LOADER even with all of Roytam releases (similar to how my 360Chrome releases use a portable loader). For all of Roytam releases, use the official portable version from here -- http://archive.palemoon.org/palemoon/28.x/28.2.2/ I personally use only the 32bit version even on my 64bit systems. Do not "exectute" the file after you download it (the file name is Palemoon-Portable-28.2.2.win32.exe). Do not download the "latest and greatest" (it will not work on XP, if I recall, unsure). Extract the file into its own folder using 7zip or similar. Delete all of the files in the Bin folder and replace with your Roytam files for whichever browser you wish to run as portable. If it's a Basilisk or BNav browser, just rename the executable to palemoon.exe or dig through the .ini and edit accordingly. You'll have to learn a new portable loader .ini format but well worth it - I always run all of my browsers using a loader and .ini. You can copy your existing profile into the portable loader file structure, the default profile for a NM/PM is in User -> PaleMoon -> Profiles -> Default. I also do this for added security, my OS doesn't have a "default browser" and the OS can't open what it thinks is the "default browser" because the executable file no longer exists.

Noted, thanks.

I would buy that... If you didn't post half a dozen posts on the very same thread and then backtrack to post a "rib-jab" implying we are "ignorant" and don't know the difference between SE and EE.

I'd say something like "no sh ... t" but I don't think we are allowed to use words like that @rereser's post did link to the SE, but so what, it was a conversation starter that did kick off the EE alpha, so why nitpick SEVEN DAYS LATER that an SE was referenced in his post? https://msfn.org/board/topic/182993-360-extreme-explorer-arcticfoxie-versions/?do=findComment&comment=1205830

I think I had the same thing when I tested an older version, don't recall offhand. Works fine in XP x86 SP3 but does not work in XP x64 SP2 (ps - @Humming Owl, the "wow_helper.exe" that you remove in recent 360Chrome builds is required in order to run in XP x64).

Good to know, thanks. I was about to think that my work in alpha 13.5 was in vane because something better came along already, lol. I hadn't gotten as far as testing Kafan Min-Browser (tested an OLDER version and was not satisfied at that time, but have not tested the latest version).

I do hope that you will reconsider. Personality clash aside

January 14 -- "And don't forget to like my posts" -- https://msfn.org/board/topic/182304-extreme-explorer-360-chromium-78-86-general-discussion/?do=findComment&comment=1194269 January 20 -- "you should have mentioned me with a tag , like this @Dixel" -- https://msfn.org/board/topic/182304-extreme-explorer-360-chromium-78-86-general-discussion/?do=findComment&comment=1194558 July 23 -- "Oh , and I'm just really curious , you see , I do upvote your posts , will you upvote mine" -- https://msfn.org/board/topic/182304-extreme-explorer-360-chromium-78-86-general-discussion/?do=findComment&comment=1202717 August 8 -- "even though I put a like on your post again" (implying I didn't put a "like" on your post ???) -- https://msfn.org/board/topic/182876-360-extreme-explorer-modified-version/?do=findComment&comment=1203199 Just last Thursday you whined about not getting a "thanks" in this thread, probably unconsciously forgotten by me simply because our personalities CLASH so much! My fault? Your fault? Who cares? -- here You misread me often. I misread you often. Why? Who knows, who cares? I feel like you seek attention with your number of "likes" all because of that January 14th post where you specifically requested me to "like" your posts and several mentions thereafter, in this thread and in others. Then on July 23rd you saught more attention by reminding me to "upvote" your posts. I don't do Facebook, I don't do Instagram, my self-worth has ZIP to do with a number of "likes" on any given web site. I mean, come on, just look at the personality CLASH that you and I have - why in Hades would I subject myself to something "like" (pun intended) Facebook or Instagram or TikTok or Twitter or YouTube or Vimeo or Reddit - all platforms that live and die by the "like" button. But I digress...

Sweet! A new toy!

This is the Tampermonkey script that I use to have a much better font-rendering experience with Chrome-based -- https://greasyfork.org/en/scripts/2372-clean-font-families/code

Agreed! Especially in non-XP OS's. XP, at least in my experience, is MUCH better at taming all of the "cleartype" and "antialias" crap.

Normal behavior for an in-process alpha build. Not all of the extensions page modifications have been implemented yet. Maybe it was too confusing to roll out "alpha" releases and I should have held off until an official "rebuild_1"? It's because Flash plugin files are not supplied by default. Outside of a "test" site, Flash no longer seems to have any real-world presence. If you have sites that "require" Flash then I could supply notes on how to install and where to obtain (no clue offhand, to be honest, I thought all web browsers removed Flash support a year ago, seems a step backwards to bring it back).