NotHereToPlayGames

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).

I still plan on creating a dark theme - but it's so back-burner that it's sitting on the stove at the appliance store instead of the stove in my own kitchen.

For those truly curious as to whether "dark themes" are 'better' for your eyesight -- https://www.androidauthority.com/dark-mode-1046425/ https://www.maketecheasier.com/are-dark-themes-better-for-eyes-battery/ "In terms of readability, the verdict is clear: black text on a white background is the best." Um, no duh in my view, you cannot buy a book or a newspaper that uses white text on black paper -- Q.E.D. But for any of you entrepreneurial type dark-theme fans that feel so strongly that dark themes are the best invention ever, maybe you can found your own company speciallizing in books and magazines using "dark theme" print schemes - "good luck". I also had Lasik several years back and also corrected an astigmatism so this too could explain why DARK THEMES look TERRIBLE per MY eyesight. Couldn't resist...

I do not use this option and have no issues with pop-ups without it - I only allow whitelisted javascript and do not use any pop-up blockers be they built-in or be they extensions. I personally find that pop-up blockers are a headache 70% of the time while blocking ALL javascript then reloading a webpage that simply "forces" javascript is only a headache 30% of the time. I will take that 30% over that 70% any day of the week To each their own... Aware, have not gotten this far yet, this should be resolved once alpha finally makes it to an official "rebuild_1". Blah, blah, blah... I'm starting to feel like "dark themes" have somehow become the ultimate mind-melt control mechanism of "tech giants" indoctrinating the mind and turning us all into "Lemmings" -- sorry, I will not follow those Lemmings over the cliff, I am not a "gamer" and do not see the need for my web browser to look like a scene of some video game so "easy" to the eyes that a "gamer" will spend the entire day in front of it and then wakes up one morning and finally decides to let some sunshine in and finds himself wondering how life passed him by... But I digress...

Thanks. Yeah, profile maintenance can be a bit of a pain when updating frequently. I created an AutoIt script that recreates my profile for me - fully automated, always kinda fun to watch the mouse move around and text fields filled in with no interaction with the mouse or keyboard. I prefer to create a brand new profile from scratch with each and every release, I don't try to preserve it or migrate it, I install extensions from the ground up each and every release.

Download link for v13.5.1030 Alpha_6 added to first post. en-us.pak -> capitalization correction missed in previous alpha's options.zip -> switcher_manage.js search_engine_manager_engine_list.js options.js appstore.js appstore.css cookies_view.css import_or_export_bookmark_overlay.css shortcut.css options_page.css advanced_options.css browser_options_page.css options.html