Jump to content

Mathwiz

Member
 View Profile  See their activity

  • Posts

    1,867

  • Joined

  • Last visited

  • Days Won

    51

  • Donations

    0.00 USD 

  • Country

    United States

 Content Type 

Everything posted by Mathwiz

  1. Mathwiz
    Basilisk/52.9.2022.08.06? I'm surprised ABBO accepts that. Wasn't MCP's final Basilisk version released over a year ago? But, as long as it works.
  2. Mathwiz
    And here I thought Plex was just PVR software to run on your own PC! I guess they're branching out and trying to get into the streaming game with plex.tv.
  3. Mathwiz
    Let me push back a little bit against that. AFAIK, FF 52 does support TLS 1.2 and many modern, secure cipher suites. I probably wouldn't store my email or banking passwords in a FF 52 profile, but it's probably just fine for most casual browsing. Like WinXP itself, just because it doesn't have all the latest security features, doesn't make it "totally" insecure! You just have to be a little more careful.
  4. Mathwiz
    I can answer on @Dave-H's behalf. He also uses Firefox on Android and so relies on Firefox Sync, which hasn't been supported on, say, Serpent, in many years (specifically, since MCP created their own sync platform for Pale Moon and, at the time, Serpent Basilisk, and @roytam1 followed suit in New Moon and Serpent). True, he could probably "upgrade" to the last Serpent version prior to the changeover, but that really wouldn't improve his situation all that much.
  5. Mathwiz
    Possibly related: I'm using @roytam1's Serpent 55 and am able to post. However, when I click Submit Reply, MSFN doesn't appear to do anything. It actually does post my reply, but since it doesn't seem to, it's easy to accidentally double-post. That just happened to me. Edit: It appears this behavior only occurs if your post appears on a different page than the one you're viewing! So it usually works correctly, and only fails one time out of 15 (or if I'm replying to an old post). Edit 2: Seems to be fixed. At least, St 55 is working fine for me now.
  6. Mathwiz
    (deleted)
  7. Mathwiz
    Question about this: it wasn't long ago that addons.palemoon.org checked your browser's user-agent and wouldn't let New Moon users (version 28.10.*) or users on unsupported OSes (< NT 6.1) download any add-ons. Easily fixed with a SSUAO; e.g., general.useragent.override.addons.palemoon.org;Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:4.8) Goanna/20211001 PaleMoon/29.4.0.2 (that's a rather old Pale Moon version, but you get the idea) ... but is that not required any longer?
  8. Mathwiz
    Well, your (and @VistaLover's) English is far, far better than my German (and I don't understand Greek at all)! But since this is an international forum, whenever I'm misunderstood, I always wonder if something I said didn't translate well into the reader's native language. Hence my preemptive apology for any language barrier. At any rate, it was all just a big misunderstanding! I knew at least one browser (my favorite St 55) requires palefill's install.rdf to be modified, and as far as I knew, there, well, "may" be others, so I thought it best to warn those reading my post about that possibility. But somehow that possibility got misread as an inevitability, so everyone thought I must have "assumed" that NM, or all browsers compatible with XP (or something - I'm still unsure what exactly I was thought to be "assuming") required a modification to palefill's install.rdf. The fact that the gh-wc-pf version I happened to be using (1.2.19.1) doesn't work with GitLab (which is why I recommended switching to palefill in the first place), but both the version before (1.2.19) and the one after (1.2.19.2) do work, likely added to the confusion. If your only goal is to download the latest CleanFlash installer, you don't need palefill at all; the last "official" version of gh-wc-pf on its GitHub page, 1.2.19, displays GitLab pages fine. But ironically, you are more likely to need to modify gh-wc-pf 1.2.19's install.rdf. Besides, palefill fixes some Web sites besides GitHub and GitLab. So even though you don't have to, it's probably worth switching to palefill anyway.
  9. Mathwiz
    (emphasis added) Wow; what a prickly pair of posts! Let me respond in kind. The GitLab link failed to load for me, not only in St55, but also in (UXP-based) IceApe. I was using 1.2.19.1 in both browsers, so I'm surprised to learn that GitLab works with "plain" 1.2.19; I guess the fix @roytam1 added in .1 (to fix a GitHub issue) broke GitLab somehow. Unfortunately Roytam's fixes are linked in comments and so aren't shown on gh-wc-pf's release page, so I was unaware 1.2.19.2 even existed until I read @VistaLover's post. Thus I turned to Palefill (v1.19.3), and the GitLab page loaded fine in both browsers. So I linked to Palefill as a known-working GitLab solution, though of course now that I know about gh-wc-pf 1.2.19.2, I suspect Palefill 1.19.3 doesn't incorporate the latest GitHub fixes (or equivalent ones) from it; so for the specific case of GitHub, I suppose gh-wc-pf 1.2.19.2 is the preferred solution. (Also unknown is what happens if both are installed at once!) At any rate, both add-ons are chasing many fast-moving targets. And speaking of Palefill, apologies if there is a language barrier, but I made no assumption about browsers. I said, "you may also need to modify install.rdf," not "you will also need to modify install.rdf." "May" makes the sentence conditional, so I didn't think I'd nonetheless be expected to test Palefill installation in every possible browser to see which ones needed a modification!
  10. Mathwiz
    Clean Flash Installer version 34.0.0.267 is now available at https://gitlab.com/cleanflash/installer/-/releases/. Unfortunately, JustOff's GitHub-wc-polyfill add-on is no longer v1.2.19.1 isn't enough to access GitLab from a UXP browser; if you have that version, you must now either downgrade to v1.2.19 or upgrade to v1.2.19.2 (links below) or use Martok's Palefill add-on. You may also need to modify install.rdf to allow either add-on to be installed. Palefill is compatible with more browsers without modification, and it fixes some websites other than GitHub and GitLab, so I now recommend Palefill over GitHub-wc-polyfill. Also, Serpent 52/55 must be in single-process mode. 360EE-based browsers should work without issue.
  11. Mathwiz
    I get the "unsupported after Dec. 2020" banner as far back as Version 77.0.235.9 (Aug. 2019). M$ had already built a time bomb into Edge by then.
  12. Mathwiz
    At least this time it's not Google causing trouble! I'm guessing, from the "-moz" prefix on the media queries, it's Mozilla this time - probably unintentionally too; the idea was probably to let Web designers give their sites a look "compatible" with the standard theme of a user's OS (so on Vista/7, a Web site could have an Aero look, etc.) But it also allows Web designers to make their sites unusable on any OS they dislike, as long as a Mozilla-derived browser is used. Just make everything hidden unless Win 10 is detected! And UA spoofing is useless, since the browser itself is determining the OS version and applying the CSS accordingly. I'm surprised MCP didn't use this CSS trick to make their sites useless to XP/Vista users running Serpent/New Moon/MyPal back when MAT was there! Might be a good idea to find a launcher that can fool the browser into thinking it's running on a Windows version other than the one it's really running on, just in case this becomes a bigger problem over time. Naturally, St55 does require install.rdf to be modified. But I've gotten quite used to that by now; once modified it installs and looks fine in St55. Naturally on Win 7, I get the Win 7 "look," which doesn't really match my "Classic" (Win98-like) theme! Still, my only complaint was that everything got way too big for my taste. It's perfectly usable.
  13. Mathwiz
    His argument seems to be that you, the user, shouldn't trust any add-on that allows logging into a banking site, because the add-on author could have slipped some code in to steal your password. (And although I doubt Martok would do such a thing, perhaps he worries about being falsely accused if someone's bank account were coincidentally hacked shortly after installing his add-on.) He has a point, but it seems his point proves too much, as it could apply to any add-on, not just one that specifically permits logging into a banking site. You have to grant a bit of trust to every add-on you install! Perhaps this is why Mozilla started requiring all the add-ons at AMO to be digitally signed: makes it easier to track down the author if malware is discovered in an add-on....
  14. Mathwiz
    All that stuff is saved in the browser's "profile," which is stored in a separate directory from the browser code itself. (To see the directory it's stored in, click Help / Troubleshooting, find the "Profile Folder" row, and click "Open folder.") So yes; all you have to do is unpack the new version and run it, and all your data will still be there. You can almost always unpack a new version over the previous version, although I prefer to keep at least one prior version, in case the new version has bugs the old version didn't have. Also, you don't have to update every week, although you're free to do so if you wish, of course.
  15. Mathwiz
    It seems odd.... custom elements (part of Web components) have been around for quite some time now and are recognized as a standard part of the DOM by now, while optional chaining and "nullish" coalescing are relative newcomers - yet we got support for the latter first! Evidently implementing custom elements is a great deal more work. Well, the concern is, no support may be better than incomplete or buggy support. That certainly seems the case with Web components. I leave it disabled, and let add-ons like palefill try to substitute for its absence. Leads to a better browsing experience overall. I'm less sure about PerformanceObserver. @VistaLover has evidently been inadvertently browsing the Web with it enabled for some time now, without apparent ill effects - so enabling it doesn't seem to hurt anything, at least. We need a relatively thorough Javascript features test page, even though I'm sure it'd be a lot slower than the pages I'm familiar with, like the GitHub test page and html5test.com. Those just test for the presence of a feature, but don't really exercise it enough to show whether it works properly.
  16. Mathwiz
    Ah, the old "behind a pref, disabled by default" trick. That's the third time I've fallen for it this month! BTW, setting pref dom.webcomponents.enabled to true turns CustomElements on GitHub's test page green. But I'm skeptical that it works correctly; my banking site (chase.com) does not quite function correctly if this pref is set. Perhaps there is incomplete support for custom elements in Serpent? If so, I have a hypothesis about the performance observer pref. It too was incomplete at the fork point from Firefox (since Mozilla didn't finish it until FF 57, the first Quantum version), so the pref was created and set to false. Later, MCP completed the implementation (and @roytam1 ported it to St55) but the pref was never changed (at least in St55). Not surprisingly, it's meant to, well, observe "performance" events. OK, I can see that for web pages that check your browser's performance; but why on earth would GitHub require it in order to function? (Rhetorical question. I do wonder, though, if there are other Web sites that require this rather old function to, well, function!)
  17. Mathwiz
    Useful link! For comparison I tried St55 with the same results, except for one more unsupported feature: PerformanceObserver constructor (whatever that is). This surprised me because it's supported by NM 27 as of April 1. So it seems like it should be feasible to support in St55, but of course I don't really know.
  18. Mathwiz
    And to make our strange language even more complicated, there's another use of the word "either:" to emphasize that a subsequent "or" is exclusive. For example: ... meaning, I'll have one of those choices, but not both.
  19. Mathwiz
    OK, I'll bite. I know what browser.startup.homepage is, but what the heck is browser.startup.homepage_override.mstone? (Mine is set to 4.0.3 but I have no issues saving files....)
  20. Mathwiz
    Maybe; maybe not. It was discussed a few pages back: There is a patch for Waterfox Classic, based on FF 56, but between FF 53 (the St 55 fork point) and FF 56, I think Mozilla's Javascript engine was rewritten in the Rust programming language. Before Russia invaded Ukraine, Feodor2 noted that Rust can be made to output XP-compatible C code, so it's doable, I think, but a lot of work, and of course @feodor2 has been unavailable to help with our trivial matters since the invasion....
  21. Mathwiz
    Good news on that front: I got 360EE v13 working again. Turns out I need to "Run as Administrator" on Win 7 - no idea why. I've never needed to run a browser as "Administrator" before.... Edit: Now that I think about it, I think I know why. I foolishly put the 360EE folder under the "Program Files (x86)" directory, and 360EE modifies some files there. That works fine in XP but requires administrator privileges on Win 7. Oops! Anyhow, the troublesome site https://cw33.com/morning-in-america/ doesn't load correctly there either! I'm starting to think the Web page itself is broken, not a problem with older browsers. Sorry for the false alarm, everyone....
  22. Mathwiz
    Here's a challenge: on Serpent 55, a local TV station's pages only display the heading; no content. Despite optional chaining, nullish coalescing, froglick combining, and what-have-you, there's just a big blank space where the content should be. Same in Edge 77, so I'm guessing 360EE v11/12 as well. (And my 360EE v13 is suddenly refusing to load, so I can't test it.) The modern Web's Googlized Javascript (Googlescript?) continues to evade our attempts to avoid modern browsers and their resource-hogging OSes. Is there any hope at all?
  23. Mathwiz
    There is also a pref "javascript.options.wasm_baselinejit". I assume it becomes irrelevant if javascript.options.wasm is set to false, but I don't really know....
  24. Mathwiz
    Really, @UCyborg, that's a double negative. Do you mean it "does work also?" Seriously though, I get the point. The Amwater.com site really wants you to use "modern" Windows or MacOS. I doubt even Win 7 will work for long, assuming it even works now! (Ironically, they don't recommend Edge as a "supported" browser....) It's like a reverse IQ test. If you use anything "too smart" you're blocked!
  25. Mathwiz
    Ah; well, that explains it then. The site truly is an anti-XP (and Vista) bigot; you just chose to "pass" as Win 10. Probably not even realizing you needed to. Pray tell, how do you fake your display resolution, given that it's not part of the UA? Asking for a friend Seriously; faking a display resolution would help with browser fingerprinting, for those of us using Microsoft's VM. In full-screen mode, the display resolution is usually your monitor's resolution minus two rows. That "minus two rows" stands out like a sore thumb. I don't personally, but a lot of folks do. BTW, this is a great example of "hyper-resolution-itis;" a disease which inflicts many designers of smart phone and laptop screens these days: The compulsion to cram as many pixels as possible into as small a rectangle as possible. Come on, let's get real: no one can see the difference between 1280x720 and anything greater, on a screen the size of a typical smart phone, unless they're viewing the screen with a microscope! Even my old BlackBerry Priv (well, ca. 2015 is "old" when you're talking about smart phones) has a 2560x1440 screen! (I like the phone anyway.) But "4K" resolution lets the marketing guys brag: "You need our phone because we have more pixels than the other guys!!" And enough folks are stupid enough to fall for it, that the disease has become endemic.
×
×
  • Create New...