Jump to content

Mathwiz

Member
  • Posts

    1,862
  • Joined

  • Last visited

  • Days Won

    51
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Mathwiz

  1. I suppose I could try yet again from another PC, but registering for that site is just a ridiculous amount of trouble for a hack that does little but save me from going to the M$ Update Catalog once a month. They even seemed to not like my passwords because they were too random! Besides, I'm sure this forum will soon have its own @Bersaglio who posts links to the new updates every Patch Tuesday.
  2. That's interesting, but.... GHacks didn't publish the hack; you have to get it from the My Digital Life forum. OK.... You have to register at mydigitallife.net to get to the hack. That's still not so bad, but Mydigitallife.net bans all popular "masked" email domains. Sounds to me like they want to spam you (or sell your email address to someone who will), and they don't want to make it too easy for you to block their emails. They also require your birth date (including year) to sign up. I suppose I could lie about that one.... Just to make things that much more annoying, they use a Google reCAPTCHA too.... Geez. I suppose I could create a new gmail account, use it to sign up, retrieve the hack, then delete the account, but what a hassle. Instead, I'm gonna use my wife's gmail account; she gets plenty of spam already. Aaand, after all that, apparently they didn't like the handle I was gonna use. ("Mathwiz" was taken.) Even after successfully completing the reCAPTCHA, twice, their #$%^@ system still thought I was a spambot and blocked my IP address! Ironic they're so paranoid about spam they don't even trust a reCAPTCHA to weed out the bots, but they won't let you use a masked email. Kind of a double standard, I'd say! So, it's up to the rest of you.
  3. There was a never-released Windows 9 with IE 11?
  4. (Yes, @LoneCrusader suggested names, and even @Matt A. Tobin liked them!) A few more suggestions were made starting here:
  5. Not sure. But, it's likely that pretending to be FF 68 causes YouTube to use CSS, JavaScript, or something else that was written for post-Quantum versions of Firefox, but that Serpent doesn't understand. Instagram has a similar problem. Maybe, but it could also be due to a change in Serpent, which used to report version 60.9; now it reports version 68.9. Github often sends code that Serpent can't handle, unless you use one of a few specific user agent strings. FF 60.9 works (or at least, it used to); so does the "native" Basilisk/Serpent user agent. But FF 68.9 apparently does not. BTW, a better approach than turning off FF compatibility mode completely is to create a SSUAO just for GitHub. That will fix GitHub without breaking other sites.
  6. Arctic Fox is very similar to New Moon 27. But at present @roytam1 only has an SSE2 build available. New Moon 27 has an SSE-only build. MyPal is very similar to New Moon 28. Both require SSE2. So if you're looking for a browser for an SSE-only PC, I'd look at either New Moon 27, @roytam1's Firefox 45 build, or perhaps his SSErpent 52 build (that last one is still experimental though).
  7. @msfntor I would expect Arctic Fox to require the same LAV video .dll's as NM 27 for video playback to work. (IIRC there's a FAQ in post 1 of this thread with the links to these .dll's.) But I haven't confirmed if they work with Arctic Fox myself. It wasn't clear whether that was addressed to the OP or to me. So just to clarify, I don't have uBO or uBO Updater installed in FF 45 at all. I only use FF 45 for testing, so I've kept the installation as "clean" as I can. I do have both extensions installed in Serpent 55, probably from GitHub (I know I got uBO itself from there), and both auto-updated fine. But it's certainly possible the OP installed uBO Updater from APO (I of course don't know). If the version on APO differs from the one on GitHub (I'm too lazy to download them and check), that could indeed explain its failure to auto-update on his system. That aside, what I think you're saying is that uBO Updater redirects update requests to GitHub not only for uBO, but also for itself. Which makes sense now that you mention it. Interestingly, uBO Updater not only auto-updated my uBO installation on Dec. 16, but also auto-updated itself on Dec. 18, presumably after GitHub made the changes that required the fix to uBO Updater in the first place. So now that I know the backstory, I'm rather surprised it auto-updated for me or anyone. (But I'm not complaining!)
  8. I suppose I should ask how you feel about RoyFox (perhaps with variations as @Mcinwwl suggested). I know you'd rather we not rebrand at all, but if it happens, we still want your opinion on what the new branding should be. I'll give mine: I like "Moebius" for Serpent 55. I've been labeling my Serpent 55 icons "Moebius" long before @Matt A. Tobin suggested using the name. The others, I don't have particularly strong feelings about. We could use all, some, or none of his suggested names. (Although if we go with Whistler, his suggested replacement for New Moon, we do already have a rather nice logo for it.) AIUI the name New Moon is a placeholder name built into the Pale Moon source repo and is automatically given to any unofficial builds of Pale Moon; it's not something @roytam1 came up with on his own (if it were we wouldn't be having this discussion in the first place). I think there's some confusion here. All of the browsers under discussion target Windows XP and up. There aren't different browsers for different Windows versions. AFAIK none of these run on unmodified Win 2000. (With KernelEx, some may work; I don't know.) That said, I do like your idea of using a "base" name like RoyFox with a "modifier," which could be @Matt A. Tobin's suggested names. So RoyFox Whistler would be @roytam1's Pale Moon fork, RoyFox Neptune would be his Borealis fork, etc.
  9. If you delve back into the original 200-page thread, you'll find plenty of suggestions for new names. None caught on, probably because we soon had far too many to choose from! I tried to avoid that this time, figuring @Matt A. Tobin's suggested names were good enough and I didn't want to start another avalanche of name suggestions So far the leading alternative suggestion seems to be RoyFox and variations thereon. Which would also be fine by me. ================ Well yes, but I think the immediate concern is rebranding New Moon, Serpent, Navigator, and Interlink (mail/news). The others (FF 45 SSE, Arctic Fox, K-Meleon) can remain as they are for now. So maybe four polls (five if you consider Serpent 52 and 55 separate).
  10. FF 45 probably looks at addons.mozilla.org, and uBO Updater is probably not hosted there any more. At least, a search doesn't bring it up, which would make sense because it's probably a pre-WebEx app (otherwise it wouldn't run on NM, PM, or official Basilisk, which are its primary targets) and therefore banned from AMO. I got lucky: my Serpent 55 (which also uses AMO) updated to the new uBO version on Dec. 16, when uBO Updater 1.6.7 was still working.
  11. You're right, of course; those languages are closely related and I just got them mixed up in my head. Actually I just remembered: it's rey in Spanish; roy is French! Apologies to speakers of both languages. It sounds like JustOff (author of uBO Updater) is essentially taking over further development of the legacy branch of uBO while Gorhill concentrates on the WE branch. Probably just as well.
  12. Anyone who finds the suggested "Whistler" branding for NM 28 objectionable, should let us know now, while there's still time to change it. Seems pretty innocuous to me, but you never know what might turn folks off unless you ask! For the @roytam1 NM browsers that are usually updated each week, the best way to do what you want would be to wait until the version number changes, then download the last build of the previous version. That would be closest to the eventual release version. OTOH, if you always want the latest, greatest version, @i430VX has an installer that takes the drudgery out of updating your browser! I'm sure it doesn't mean the same thing in Chinese, but in Latin, "Roy" means "king;" so for me, "RoyFox" conjures up an image of a fox with a crown on its head! Then again, that might trigger a "raccoon"-like reaction with some folks.... Edited to add that @caliber suggested a nice "RoyFox" logo a few pages back. No crown but it looks nice to me.
  13. I don't think that @roytam1's Arctic Fox for XP, FF 45 for SSE PCs, or K-Meleon builds are affected at all. Arctic Fox already has its own branding.
  14. Admittedly, there's zero benefit to me from new branding. At best, we'll get some spiffy new icons, and new artwork in Help / About, but the core functionality of our UXP-derived browsers isn't changing. The difference I see is that this time, @Matt A. Tobin is offering to do a good portion of the necessary work. And I don't see that we're sacrificing anything; if we are, please enlighten me. I'd be much more dubious about this if I though we were losing anything concrete .
  15. It doesn't matter, because Windows Media Foundation doesn't exist in XP. Microsoft added that feature in Vista. On Win 7, I often set media.wmf.enabled to false for testing (so the browser won't look for it, forcing it to use alternate media decoders such as Primetime). You might also set it false if your Windows version has a WMF bug you find intolerable; otherwise I'd leave it at true for normal browsing.
  16. OK that's progress; we now know the changes that broke APZ/tiled compositing came before that alpha release of FF 52. We know that SM 2.48 works, so it's pretty likely that FF 51 works too; but I haven't actually tested FF 51. Perhaps I should do that next, just to be sure.
  17. Learned a new word today! Although in these parts, we still call it, uh, a still... It's a bit belated, but I wanted to say thanks for that tip! It's finally given me a way to maintain multiple Firefox versions on the same PC, each with its own profile, without a kludge like setting up separate Windows users (and having to log out and back in) to access each version. Just make sure to include the intended FF version in the name of each profile you set up. Very useful when you want to test FF versions ranging from 45 through Quantum to "Firefox Browser" (or whatever the name of the week is). Even on XP, I now have FF 45 SSE, FF 52 ESR, and FF 53 (patched to run with XomPie) all coexisting in relative peace.
  18. I tend to agree. Perhaps @dencorso can move the last few dozen posts about branding to their own thread? Be careful, though; there are a few unrelated posts strewn among them!
  19. Branding is hard work. You don't need just a name; you also need artwork, and you need to make sure your artwork doesn't tread on someone else's IP. I for one am glad @Matt A. Tobin is willing to do that work (and seems pretty good at it, too); it's not a field most of us have much skill at. At one time I created an icon for Moebius (I spell it with the e so I don't need an umlaut on the o); I'll attach it here. For Neptune, I'd go with the planet; plenty of public-domain Voyager images to choose from, and Neptune's trident might be too suggestive of the Devil for some folks moebius-triangle.ico
  20. Oh, wow ... so did you have to move to a newer Windows version? OK, unpacked FF 52.0.a1 into a new folder. Installed the UOC Patch for FF 45. Created a new, clean profile for it and installed the UOC Enforcer for 45. Started it. (This version defaults to e10s on.) On Darksky.net I saw some of the same symptoms as you when scrolling up: black rectangles and/or incompletely-redrawn parts of the page. (Scrolling down seemed OK.) Turned e10s off in about:config. (There seems to be a bug with the checkbox in about:preferences: it sets the wrong pref, and e10s stays on.) Much better; apparently e10s is incompatible with APZ and/or tiled compositing. But, one problem remained: I couldn't get that dark grey overlay to completely disappear. Often it would cover the whole graphic, but if I scrolled up from below slowly, it would just cover the bottom part, as in this example. As a control, everything looked fine on Serpent 55 (Moebius). Do you remember if those were the same kinds of problems you had with SSErpent 52?
  21. Aw, man ... that's too bad. It didn't take the HDD with it did it? Can you just replace the MoBo and reactivate XP instead of reinstalling everything?
  22. OK, so my test plan for tomorrow is: Download and unpack @roytam1's FF 52.0.a1 build linked above Install the UOC Patch & Enforcer for FF 45 Scroll up & down in some web pages and look for the issues seen above. Try both with e10s off and on. Any suggested Web pages to try? Is MSFN enough?
  23. The name "New Moon" was built into the Pale Moon source repo as a placeholder for anyone making an unofficial build of Pale Moon. It was always recognized as a temporary name. In the original thread, I and many others made many clever suggestions for a permanent name, but none caught on, so @roytam1 just kept using the New Moon name. I'm reluctant to restart the cacophony of suggested names again. "Whistler" may not be that inspiring, but it's not bad and fits a theme. Let's get this done at last.
  24. Adobe's online installer isn't a Trojan AFAIK; it's only problem is that it doesn't work on XP. As for Avast, I'm aware of their snooping: As I hinted in the last line, sometimes that's the price of a "free" product. So they bumped the revision up to 68.9.... No idea why @caliber wants to be version 2 though; that's pretty a old FF version.... I'm still using version 60.9 on my user agent; most sites don't seem to complain about an "outdated dinosaur browser" as long as they think you're running a post-Quantum version. Must have been changed by July 19; that version reports Basilisk/20190719 In the 20190719 build, toggling it false has no effect: you still get Basilisk/20190719. But by build 20191115, toggling it false works: you get Basilisk/52.9.0. So they must have fixed it somewhere between those two points. I doubt many sites check for a "Basilisk" UA segment, but there may be a few.
  25. It is true. The online installer downloads and launches, and on Win 7 it runs fine. But on XP this happens: The offline installers at the links @Bersaglio posts work fine on XP.
×
×
  • Create New...