Jump to content

NotHereToPlayGames

Member
 View Profile  See their activity

  • Posts

    6,960

  • Joined

  • Last visited

  • Days Won

    89

  • Donations

    0.00 USD 

  • Country

    United States

 Content Type 

Everything posted by NotHereToPlayGames

  1. NotHereToPlayGames
    You really have to answer this one yourself. You ask 50 people, you'll get 50 different answers. You ask 5000 people, you'll get 4999 different answers and two people that give the same answer. I personally use v27 because I have ran benchmark tests and v27 is faster - "mileage may vary" and you should really run your own benchmark tests.
  2. NotHereToPlayGames
    I will not. I do not follow "their" build, I follow your build.
  3. NotHereToPlayGames
    ALL settings in about:permissions is broken. "Most" of them were fixed in NM27 but they still remain broken in ArcticFox.
  4. NotHereToPlayGames
    Agreed! I, for one, do NOT want BLOAT added. I want to go the OTHER WAY and REMOVE (what I feel) is BLOAT already added. I want FAST and EFFICIENT at its CORE. "You guys" can slow your browser down all you want with addon after addon and extension after extension. "To each their own", as the saying goes.
  5. NotHereToPlayGames
    300+ MB RAM with only the "Tableau" open ??? HECK NO, that's not for me! (you asked my opinion, lol) Plus I don't want my browser to use my OS's proxy settings - I know there's probably an extension for that but the 300+ MB RAM with nothing open is a showstopper for me.
  6. NotHereToPlayGames
    I can direct SOME (not "most") to web devs. I whitelist JS and only allow a portion of them to work on a very small number of web sites. I have high hopes for BNavigator but it can't dethrone Mypal / New Moon / Pale Moon just yet. Pale Moon (at the upstream level) has become BLOATED and there is no such thing as a current fork that attempt to remove any of the BLOAT. "Most" can be directed to "web standards" and that browser developers FALSELY think they need to attempt to adhere to them. The "web standards" are GIGANTIC and we CAN browse the web WITHOUT a very VERY large portion of them. Read some of our "patch" descriptions on a weekly basis then try to track down WHY that patch was implemented. You are kidding yourself if you think MOST of them have anything to do with "security" as opposed to 'striving to achieve 100% web-standards-compliance'. (Granted, I can only find a WHY for a very small number of these "patches"). But it's also not my "line of work". But I digress. There WILL be a day where I will have to switch to Win 7 or 10 or run a Server version (I ran Server 2003 for several years and trial-ran 2008 and 2012). But that day is FAR away so long as I don't fool myself into thinking I need to achieve a 555 score for HTML5 -- I don't!
  7. NotHereToPlayGames
    I've personally become INCREASINGLY displeased with "new" web browsers. I want FAST and EFFICIENT. What good does it do to boast "works on XP" if it takes 10 seconds to load or 5 seconds to render (exaggerating, 'slightly') ??? FAST and EFFICIENT is WHY I run XP - boot time from full power down is UNDER 20 seconds compared to OVER A FULL MINUTE for Win 10 -- "mileage may vary". My default-for-everything is currently Mypal 27.9.4 dated July 19, 2018. PassMark AppTimer == https://www.passmark.com/products/apptimer/ Kraken 1.1 == https://krakenbenchmark.mozilla.org/ Basemark Web 3.0 == https://web.basemark.com/ Speedometer 1.0 == https://browserbench.org/Speedometer/ Speedometer 2.0 == https://browserbench.org/Speedometer2.0/
  8. NotHereToPlayGames
    "mileage may vary"
  9. NotHereToPlayGames
    "mileage may vary"
  10. NotHereToPlayGames
    "mileage may vary" I haven't yet concluded if it is 'important' or not that various Roytam browsers "freeze" during the Basemark Web 3.0 test. My next addition is to browse through the patch lists and find Roytam's version "closest" to Mypal 27.9.4. Because it seems to me that "newer is NOT better" - we score lower and lower with each new release so I'd rather run an 'old' browser inside my 'old' OS. The RAM column is with my default profile (eight add-ons) with no page loaded and sitting idle for a few minutes.
  11. NotHereToPlayGames
    What other pages ???
  12. NotHereToPlayGames
    Roy, A reminder that NM27's about:permissions page is still broken. The Receive Push Notifications and the Hide the Mouse Pointer options both have not worked for a very long time.
  13. NotHereToPlayGames
    That NM27 v27.5.1 is from Feodor2's GitHub archive -- https://github.com/Feodor2/Mypal27old/releases Feodor2's releases were called "New Moon" and didn't take the "Mypal" name until v27.7.2. His very first release was Mypal but switched back to New Moon "because the most users did not like the name change" (according to GitHub). From my slipstreamed installation disk, my only browser in March 2017 was GreenBrowser + Proxomitron. My next archived installation disk isn't until September 2018 and it shows I went to Roytam's v28.1.0a1 32-bit 2018-09-14. That is from my Acer machine and it's actually only used out in the garage. My eMachine computer will tell a bigger picture but would also require more digging. I know that I was using Moonchild's Pale Moon for several months, then Mypal for several months when Moonchild dropped XP, then Chromium only as a backup to Mypal. Then I eventually landed on Roytam's v28.1.0a1 and only trial-tested Roytam's "weekly" releases but kept v28.1.0a1 as default-for-all. I personally feel that Roytam's upgrade process is too "rushed" and I have witnessed far too many patches that are later "backed out". To each their own, we all have different needs and different perspectives. I am aware that some of those back-outs are upstream also, but some are literally just "typos". It displeases me that several of these aren't even "discovered" in this forum because the forum-users seem to only notice if YouTube gets broken and nothing more. All of that has me digging through archives and performing my own tests and seeking out, at least from my perspective, a "mature" version that renders all of my needs. I'm using various "benchmarks" and attempting to keep "personal preference" out of the picture. I would like to edit the Help -> About popup boxes in several of these archive versions during my testing process basically with the end-in-mind that one of these is going to become my new default-for-all. I am still in-process of determining which version that is going to be. But I do know this, it's NOT going to be Roytam's "latest and greatest" because about:permissions remains broken and I'm getting better benchmark numbers with older versions. I'm probably not supposed to say that in a forum where we all cheer-lead Roytam because he is doing great work and I'm not trying to undermine that. I think the Help -> About has to be done to xul.dll but until then I have found that I can do various hides and highlights via Stylem.
  14. NotHereToPlayGames
    Perfect example of why I highly prefer the good-ol'-days when software went through "alpha" and "beta" testing. Instead of the "nightly" and "weekly" roll out routine where software is no longer actually TESTED before being released to the public. And we end up with a public with a 'warm and fuzzy' "false sense of security" because they're running that nightly/weekly - and that can't wait five days for an announced bug-fix. I believe that the public has become blind to the fact that often an "update" INTRODUCES more issues than it 'fixed'. Us Roytam users need to start calling ourselves what we are - "beta testers". But I digress
  15. NotHereToPlayGames
    Anyone know how to edit the Help -> About popup box? I'd like to grammatically correct and update a MyPal version's About popup I keep around for benchmark comparisons and add the release date. It's petty, I know, but I know I've been able to do this with other software but I can't seem to with this.
  16. NotHereToPlayGames
    BNavigator -- *any* version (on XP x86 or XP x64) Does the Download Manager (Ctrl+J) work for anybody with any of the Roytam versions?
  17. NotHereToPlayGames
    Okay, that makes sense. I only allow scripts on a white-list basis so in the 2+ years I've switched over to NM as my default-for-all, mom and dad's Ally Bank has been the ONLY site where I've seen that pop-up. And here I've been crossing my fingers that "one of these days", our weekly updates was going to 'fix' that Edit: The i7-4770 is my computer with five widescreen monitors. I technically do most of these types of tests/upgrades inside a "VirtualBox" environment before ever testing/upgrading on "real" Operating System on other computers. Good catch for noticing ... But why would I run such a relatively new CPU with only 1GB RAM, lol
  18. NotHereToPlayGames
    I could never get PAE to work on my two Core Duo older machines so I ended up giving up on it and dropped down to 3GB RAM. Regarding the "Warning: Unresponsive Script" error -- here is why I feel it is the culprit. That error would pop up with NM27 from TWO weeks ago. That error would pop up with NM27 from THREE weeks ago. That error would pop up with NM27 from FOUR weeks ago. That error has been popping up with NM27 (at Ally Bank at least) for TWO YEARS!. BUT the NEWEST (one weekend ago, just a few days old now) does NOT pop up that "Warning: Unresponsive Script" error -- it CRASHES instead.
  19. NotHereToPlayGames
    Yeah! I was finally able to crash the newest NM27! The key is that "Warning: Unresponsive Script" error. I used to get that all the time at my parents' (I carry my browser with me on USB) at Ally Bank. It was for the longest time the only website I used as an indicator to "upgrade" or not. If the latest NM27 didn't "fix" that error, then I stayed on my OLD version and opted to NOT "upgrade" (at least not the NM27 on USB). At least on this end, if I tell that error dialog to "Don't ask again" then the next browser session doesn't crash - the page stops loading but at least the browser didn't crash and there was no error dialog popup.
  20. NotHereToPlayGames
    Interesting. Should I feel glad or sad that it doesn't crash for me? I kinda feel left out But with Roytam mentioning that area of code hasn't been touched in a while, that kind of bugs me. Because it tells us that a "new patch" at one address DOES effect code in a totally different address.
  21. NotHereToPlayGames
    Including this one, I've done THREE screencaps - only the first was XP x64, the second two are XP x86. I can NOT reproduce a crash for your YouTube link either. Nobody else has chimed in one way or another, I at least TRIED to help
  22. NotHereToPlayGames
    I already screencap'd that I'm using the same exact NM27 that you cite the crash. I have jumped through every hoop I can think of in trying to reproduce this crash, including XP x86. I simply can NOT reproduce this crash - and nobody else has chimed in to offer anything additional so I don't see anything additional that I can do, sorry.
  23. NotHereToPlayGames
    Okay, German site crashes in Germany and in France. I await to hear from anybody in the US where it crashes for them "here". I stand by my diagnosis that I am being served a DIFFERENT script then folks on that side of the pond. And the script that I am being served is NOT crashing the NEWEST NM27 (as I screencap'd earlier).
  24. NotHereToPlayGames
    Since you live in Germany, my hunch is that you are being served different scripts than I am here in the States.
  25. NotHereToPlayGames
    Again, it's just you. I can NOT reproduce this here. This is from my XP x64. Did not test in my XP x86 (and most likely will not). Can we have a screencap of your Add-On list?
×
×
  • Create New...