
NotHereToPlayGames
MemberContent Type
Profiles
Forums
Events
Everything posted by NotHereToPlayGames
-
My Browser Builds (Part 5)
NotHereToPlayGames replied to roytam1's topic in Browsers working on Older NT-Family OSes
That's not how I use the Restore Session feature. I monitor RAM. When Serpent RAM exceeds 1 GB for only two tabs, I task-kill Serpent with the two tabs still open. Then I relaunch Serpent. What is supposed to happen is that a the Restore Session page is opened with a table containing descriptions of those two tabs and a RESTORE restores the two tabs, still logged in and everything. THIS DOES NOT *ALWAYS* WORK IN "NEWER" VERSIONS OF SERPENT! Sometimes no Restore Session page at all, sometimes the Restore Session page but no table containing tab descriptions, et cetera. -
Sending "empty strings" is the WORST IDEA EVER !!! DO NOT send "empty strings" !!! If the "intent" is to reduce your fingerprint, then why in Hades would you STAND OUT LIKE A SORE THUMB via an "empty string" ??? We've been over this a "thousand" times, you must use something like PROXOMITRON to fake Client Hints with the string of your choosing, sending an empty string is "dumb". You must "blend in with the crowd" (ie, fake Client Hint strings), *not* "stand out like a sore thumb" (ie, an "empty string").
- 105 replies
-
2
-
- crx
- Anti-feature
-
(and 3 more)
Tagged with:
-
My Browser Builds (Part 5)
NotHereToPlayGames replied to roytam1's topic in Browsers working on Older NT-Family OSes
I use the Restore Session at least twice a week (Serpent RAM leaks)! It really is "hit or miss" in newer versions of Serpent 52. Whereas it *ALWAYS* works in 2023-07-31. There's also really *nothing* in newer versions that I technically need (it is used as an email/text-message reader 24/7/365 but it is not used to browser the internet for news, videos, streaming, etc). I try the latest-and-greatest every three weeks, pretty much like clockwork, *hoping* it is going to be fixed, but alas, IT NEVER IS. It really is "hit or miss" on my hardware, no clue "why" exactly. -
My Browser Builds (Part 5)
NotHereToPlayGames replied to roytam1's topic in Browsers working on Older NT-Family OSes
I have not combed through the changelogs of Serpent, Basilisk, Pale Moon, New Moon, etc to see when/if layout.css.nesting.enabled flag is added/present. As far as my daily-use Serpent v52.9.0 (2023-07-31), I can report that the flag is not present. For my useage, there are other things "broken" if I upgrade to newer (ie, Restore Session feature is very-much-so "hit or miss" in newer) so I intentionally use 2023-07-31. -
My Browser Builds (Part 5)
NotHereToPlayGames replied to roytam1's topic in Browsers working on Older NT-Family OSes
Agreed. My intended point was more along the lines that these "experimental" flags effect both css and js. -
My Browser Builds (Part 5)
NotHereToPlayGames replied to roytam1's topic in Browsers working on Older NT-Family OSes
CSS That's because the web site in question is using CSS NESTING (not all "failures" are javascript). All of the browsers you listed can not use CSS Nesting. Supermium/Chromium 122 CAN USE CSS Nesting. The CSS being IGNORED/DROPPED by St55-Ch87 is this (note the indented &'s, this is "nesting", a css selector "inside" another css selector): [in this case, it's selector #5 (img) inside selector #4 (a) inside selector #3 (li) inside selector #2 (...sharing-options...) inside selector #1 (...social-share...)] CSS Nesting can not be rendered in anything below Chrome 120 and can not be rendered in anything below Firefox 117. -
D.Draker - GREAT JOB at creating one of the BIGGEST "unproveable" (both "sides" will always see it "their way" no matter what the "other side" has 'proven' or 'disproven') CONSPIRACIES to ever hit MSFN! Learn how to read GitHub "commits".
-
Go for it. You don't think they already know how "BS" this thread has become?
-
Please learn how to read GitHub "commits".
-
I certainly hope so! So that we can nail this d#mn coffin, faking a user agent or client hint is WAY different than "claiming" to be several versions newer on an older engine. THE SUPERMIUM ENGINE IS WHAT IT IS CLAIMING TO BE !!! Plain and simple. TO H#LL WITH TWITCH! Twitch by itself proves NOTHING. It only proves bad coding at TWITCH! IT WOULD BE AN ENTIRELY DIFFERENT STORY IF WE HAD A HUNDRED OR A THOUSAND WEB SITES THAT DO NOT WORK IN SUPERMIUM! Let's face it, PERSONAL BIAS is leading this discussion. Not logic and reasoning.
-
Bingo!
-
This is not true! Something in Supermium is indeed breaking Twitch. But "do" the same exact thing (once we find out the "exacts") in OFFICIAL CHROME v132 and Twitch *WILL* break also! If Supermium was "not even v126", a hundred or even a thousand web sites would be broken, NOT ONLY TWITCH.
-
Disproving CONSPIRACIES is a DEATH TRAP. I'm done with the "conspiracy" of Supermium not being the engine it claims to be. H#LL, we're still trying to prove who killed JFK or whether we really landed on the moon or not. Some CONSPIRACIES will NEVER be proven - this one is NOT WORTH ANY MORE OF MY TIME. You guys are, of course, obligated/entitled to define how your time is allocated.
-
re: --test-type chrome flag https://github.com/GoogleChrome/chrome-launcher/issues/24 https://github.com/GoogleChrome/chrome-launcher/blob/main/docs/chrome-flags-for-tools.md I do not get the Chromecast UDP in *any* of my browsers! But I can confirm that I just *disabled* the --test-type flag but I still do *NOT* get the Chromecast UDP! Would require additional testing which time alludes me at the moment. Only tested in Official Ungoogled as of this morning. No time to test further.
-
Highly HIGHLY improbable. We either need to NAIL THIS COFFIN SHUT or we need to PROVE this CONSPIRACY once and for all. Let's all of us take a step back and come up with some sort of D#MN PROOF. Twitch PROVES NOTHING. Let's start thinking outside the box that we have all buried ourself in. I've already "seen enough" to see THIS IS MISINFORMATION !!! But the "west side story gang" is always always always going to stick together and "go down with the ship".
-
Agree *AND* Disagree. We still don't really know the EXACT reason that Twitch is broken. NO ONE is denying that Twitch is broken. NO ONE is trying to find another example web site! It's just "dogpile on the rabbit". If it is CSS or FONT related, then Supermium's HIGHLY APPLAUDED endeavor at attempting DirectWrite broke a CSS coding at Twitch. I don't have Twitch, I will not be signing up for Twitch. BUT IT WOULD BE NICE TO HAVE MORE EXAMPLE WEB SITES instead of just more "dogpile on the rabbit". Has anyone tried Twitch in the only other GDI/DirectWrite browser that at least I am aware of - ie, this one = https://github.com/GTANAdam/GDIChromium ? But it's also showing its age big time, it's still at v103 and appears to be an abandoned project.
-
You're not listening. Twitch this, Twitch that. Is Twitch seriously the *ONLY* web site out of roughly 1.1 BILLION of them that isn't working in Supermium? If so, that's about 438,692,547 times better than Pale Moon, Basilisk, and Serpent. I myself have never heard of Twitch until this "hit the fan". But YES, apparently it is "important enough" of a web site that the developer SHOULD BE finding out what he did to the Chromium Code that broke Twitch.
-
Yes and no. I give it the benefit of the doubt. Only the next release would indicate if the author accepted the critique or not. I don't think that the author "owes" a reply to every issue/bug being reported. I mean, there's over 500 open and 600 closed. Yes, "gigantic" bugs would be nice to have a reply. But I myself do not see them as "owed" to us.
-
Was it answered in a previous issue tracker?
-
That seems perfectly fair and legit. Afterall, all of Roytam's and Feodor's releases spoof useragent overrides for the same exact "better webcompat" reasons.
-
IDENTICAL results in XP. Personally, all of this "chitter-chatter" hinting/suggesting/accusing Supermium of being an older engine is FALSE, "misinformation", and "slanderous". None of us do MSFN any "justice" when all we do is go around "following" our 'favorite Lemming' over the cliff. My two cents...
-
Enabling experimental javascript and experimental web platform features results in chromiumchecker to PASS v135 pre-release checks and PASS one of the v133 checks, but still FAILS the v134 check.
-
I just did that test ( https://chromiumchecker.com/ ) using Supermium 132 and it passes all v132 and older checks, it fails v133 thru v135 pre-release checks. Supermium 132 is "faking" user agent and client hints as pretending to be v133. But *SMART WEB SITES* know better, LIKE THIS TEST SITE, all it takes is ONE javascript test to prove that a claimed user agent and client hints (despite them both "matching" each other) is actually FAKED. I tested in Win10 with all default flags. Will test in XP shortly.
-
I kind of still think that this is an Unproven Hypothesis and akin to "misinformation". Our one (and ONLY ONE?) variable is TWITCH. All other sites are behaving as they should (even the British Gas site) once the end-user swaps the flag defaults that Supermium swapped behind the scene. Seems we should be finding ways to PROVE this before we keep spreading it as "gospel".
-
My Browser Builds (Part 5)
NotHereToPlayGames replied to roytam1's topic in Browsers working on Older NT-Family OSes
You could try one of the below (their .js files would need modified accordingly, easy to do if we know "what" you need in the Open With list) - https://chromewebstore.google.com/detail/open-with-switchbar/klgpknafjlhnpkppfbihchgfebbdcomd https://chromewebstore.google.com/detail/open-in-openoffice/ioppgifkecchbmpobbkdkobildodihed https://chromewebstore.google.com/detail/open-with-notepad++/hgfbigeomjlaahldcoilagphholnmhlc Or any of their "related" extensions. Note, just because they are "extensions", you don't have to use them as extensions, most are easily converted to userscripts.