NotHereToPlayGames

I use VirtualBox version 4.3.28. I can't recall if there was a specific reason for using that version, but I tend to operate that way, I don't doubt that I selected it for a reason, just don't recall it offhand. All legally owned, during college days the bookstore sold all Microsoft products for $5 with student ID, here are the "size" of all of my VMs, kinda tells you how "bloated" Operating Systems have become - Win 3.1 == 20 MB Win 3.11 == 78 MB Win 98SE == 218 MB Win NT4 == 236 MB Win 2000 == 578 MB Win XP x86 SP3 == 635 MB Win 2003 == 1.07 GB Win XP x64 SP2 == 1.12 GB Win 7 x86 Enterprise == 1.28 GB Win 10 x86 LTSB 2016 == 1.84 GB Win 7 x86 (default install, no customization to install media) == 3.08 GB Win 10 x64 (default install, no customization to install media) == 4.55 GB Win 7 x64 (default install, no customization to install media) == 5.04 GB

I personally avoid ALL updates on my Win10. I use 2016 LTSB on a Dell Latitude E5470 with an i5-6300U @ 2.4 GHz with 8.0 GB RAM and this laptop has NEVER been updated and NEVER will. I personally feel more "secure" NOT letting the laptop ever "see" a Microsoft/Windows Update. That's one of two "dedicated" Win10s (the other being a garage computer used for nothing other than a media jukebox). The other laptop is a triple-boot XP/7/10 but I can't recall the last time I've ever booted into anything other than XP. All three of my desktop PCs run XP and XP alone (one x64 SP2, two x86 SP3).

My fully unattended install basically takes three steps -- 1) Windows XP with slipstreamed updates and signed drivers, 2) nLite's GuiRunOnce list of .exe's, then 3) a dozen and a half or so AutoIt .exe's. If I recall, Step 1 takes ~20 minutes, Step 2 takes ~10 minutes, and Step 3 takes ~10 minutes. So XP by itself is really only ~20 minutes.

I'll be keeping my 360Chrome around even once Mypal 2.0 shows up. They (and Humming Owl's, from what I see) have basically matured to the point of nothing else to really do for them, use them as-is from here on out. I would like to see progress made on the "compile" front, but I cannot take the lead on that. Too steep of a learning curve.

I don't think MAT was kicked out. He's been "put in his place" but that's all I've seen thus far. I don't follow it unless folks here post on it. What I've been very eager to see is Mypal 2.0, or whatever it's going to be called, THAT will be a day of celebration in my book. Because, um, Roytam browsers simply can NOT handle the modern web, period. Unfortunate, but TRUE. I've given up on all of Roytam releases.

How many of you have bumped into portions of text disappearing? The "fix" suggesed in 2019 in the thread I pulled this image from cited disabling Hardware Acceleration (which I never enable to begin with, has always caused more harm than good and DISABLING is always the "go-to" suggestion to "fix" things). I'm currently DISABLING Accelerated 2D canvas, will keep you posted if I see portions of text disappear while this flag is disabled.

Thanks. Thanks. Looks like that's the end of the line for my Arcticfox, I gotta have an always-on status bar. Everyone has their must-have's, that's one of mine.

I have zero clue on what that gitbub page is saying. What is the last version of Arcticfox that still has the always-on status bar?

Speaking of Arcticfox, when did it lose the always-on status bar?

THERE it is! See msfntor, it has NOTHING to do with YOUR posts on MSFN. The nitter site admin is not an MSFN member. The world does not revolve around MSFN (especially not the "Older NT-Family OSes" threads). The nitter bug reports on the proper channels (which is not MSFN) was reported on November 21 by GitGondola. Your first post regarding nitter ( https://msfn.org/board/topic/182993-360-extreme-explorer-arcticfoxie-versions/?do=findComment&comment=1209723 ) was Friday, December 17. TWENTY SIX DAYS LATER, if I counted correctly. My point being, the world does not revolve around MSFN. The nitter cite Admin is not an MSFN member and nitter was not fixed by complaining about nitter on MSFN. There are proper channels to report nitter bugs and it was GitGondola that got that ball rolling. But anywhoo...

Your point being? Of course an MSFN site Admin will read your hundreds of posts. A Google site Admin will not. A Twitter site Admin will not. A Facebook site Admin will not. A Nitter site Admin will not.

I guarantee that the nitter admin did NOT see our posts here at MSFN. Think what you want to. But you place WAY TOO HIGH of an opinion on MSFN if you think web site admins are reading forum posts dedicated to Older NT-Family OSes.

lol, wasn't trying to stand out. The log file is not new, I've seen it in the past, it is why I use a different loader .ini file after I install all extensions, I delete that log file, and have for the last 14 months or so since I've switched over to 360Chrome. BUT, you are correct, I didn't PUBLICLY announce that log until we (you and I) were looking at write-prevents for files/folders. And because I cannot delete that .log file in v13.5 whereas I can in v11 and v12 -- making me distrust any 360Chome version higher than v13 build 2206 [which are also the versions which default Incognito Mode Developer Tools to Chinese]. It honestly didn't strike me as out of the ordinary - BUT only because I do not keep any data between browser sessions.

Right, what D.Draker said. It's not the browser but the JAVASCRIPT that we HAVE TO allow in order to use MSFN.

Very lengthy discussion spanning several pages -- starts here - https://msfn.org/board/topic/182993-360-extreme-explorer-arcticfoxie-versions/?do=findComment&comment=1208958 Log location discussed here - https://msfn.org/board/topic/182993-360-extreme-explorer-arcticfoxie-versions/?do=findComment&comment=1209035

What is "polyfill"? I've seen tons of references to it and I really am clueless (I abandoned Mozilla-based and awaiting patiently for Mypal 2.0), what is it?

I've had SATURDAY'S where I'll install Windows TWO DOZEN TIMES. I do a completely unattended install with a very large number of AutoIt executables and the best way to fully test is to "fully test". The full install on an XP x86 SP3 only takes about 40 minutes whereas an XP x64 SP2 takes closer to 70 minutes. It's actually kinda fun to watch. Mouse moving around unattended, program file locations typing themselves unattended, programs opening and moving to a different monitor then closing so that their last position is memorized so that they open on the correct monitor when I go to use the program (all six of my computers have anywhere from 2 to 5 monitors, none of them only have one), mouse wheel and buttons configures unattended, desktop icon locations set unattended, EVERYTHING that has a setting is pre-set for me, fully automated!

You do not owe anybody an explanation! "We're not here to play games."

Agreed! Reply-box logging is done on pretty much every site with a reply box. It's only when you see this type of logging being performed on username and password fields that you should tie your knickers into a knot. But a reply box? Who cares, in my view. You wouldn't be IN the reply box if you didn't "support" the web site. And the reply box isn't even there until AFTER you LOG IN. If it truly concerns you, then I guess you're more than welcome to READ the content at MSFN, but you can't ADD content to MSFN.

My view is that nefarious keyloggers will send data BEFORE we hit that "submit reply" button. I've watched network packet traffic and I see no evidence of data being transferred WHILE our reply-box typing is being "logged". And you can open that log WHILE typing in this reply box and see just what it logs. I see nothing nefarious going on, just a "feature" that SOME will see as "value-add". I would rather this reply-box NOT be logged AT ALL. It was ME that reported this logging and I've seen ZERO people leave MSFN on account of it. And I have no plans to leave on account of it either. What you chose to do is totally up to you. But I am convinced that we will NOT get MSFN to change their code just for OUR preference. Nor should they, in my opinion. I'm all for privacy and security, but I think way too many people use it as an excuse for paranoia. And everybody's definition of "privacy", "security", and "paranoia" are DIFFERENT. All we can do is do the talking with our FEET, to be perfectly honest. I do that with Twitter and Facebook and 60% or so of Google (I do use some Google services). Twitter and Facebook is blocked. Oh, a lot of Yahoo is blocked also. If I feel like MSFN becomes "nefarious", then my feet will walk. In the meantime, it's all just "talk".

There is a keylogger for the sake of restoring typed content. Some users may see that as a "pro" and not a "con". I'm with D.Draker and see it as a "con". BUT even so, I can only prove that the keylogger is LOCAL, I cannot prove that MSFN is storing this log forever. Even if so, I kinda don't care. Why? Because if I have the reply box OPEN and I'm TYPING in that reply box, those are the ONLY keys being logged, and I'm about to POST it anyway. So what if the "log" show a TYPO that I had to backspace over and there may be a DELAY before the typo is corrected. Point is, this "keylogger" only logs the reply box. And anything beyond that "could" be considered conspiracy theory. I agree with D.Draker that we don't need this keylogger. But it's only logging this reply. It's not like I open the reply box, type profanities for the keylogger to log, then close the log without submitting those profanities. I only use the reply box for content that I'm in-process of submtting to the forum. Like I'm about to do as soon as I scroll the submit button into view...

YES. We let nitter drop! Or face the music and go out and buy a computer with Win10. And that's assuming nitter works on Win10, as none of the Win7 or Win10 crowd has chimed in. Why? Because none of us really care about nitter. Just my opinion, of course.

And I would not necessarily assume that faking a "new" User Agent (Latest User-Agent I see: for Mac Os X 10_7 with Firefox 92.0) would be the correct attempt either. But rather try a User Agent from 2017 or 2018. Keep trying older User Agents. At the very least, try a mobile phone User Agent. And if you never get anything that says something like "your browser is not supported", then that web site has been specifically coded to not care what your User Agent is. Faking User Agents is actually OLD SCHOOL. This isn't 2020 anymore. The "modern web" 'evolves' a crapload faster than it did way back in 2008 or so when "faking" User Agents became so common that some of our parents even know how to do it.

Theoretically, yes. There is a Compiling Chromium thread that was started in 2017 and only hit 3 pages by 2019 and has been recently bumped -- https://msfn.org/board/topic/177191-compiling-chromium-browser-for-xp/?do=findComment&comment=1208782 But the thread has found little to no traction and I wouldn't be able to be the first person to perform such a task until my retirement years 20 years away as it would be a full-time job to learn it all.

MOVE ON! Please. When you stumble upon a web site like nitter and you can't get it to work in TEN different web browsers, then hello, nitter is the problem, not your web browser. You've directly cited issues on nitter with v13.5 r 5, v13 r 6, v13 M, Cent, Slimjet 50, Iron 49, SuperBird 44, Serpent 55, IceApe, and NM28. This is NOT a "browser bug". Are you "reporting" this in forums of all TEN of those browsers? If so, your OCD is worse then mine You're kinda gonna have to ACCEPT that nitter is simply a JUNK web site that WILL NOT WORK (at least in XP, I'm still waiting for Win7 or Win10 users to chime in).