Jump to content

basilisk-dev

Member
  • Posts

    34
  • Joined

  • Last visited

  • Days Won

    2
  • Donations

    0.00 USD 
  • Country

    United States

basilisk-dev last won the day on May 18 2023

basilisk-dev had the most liked content!

About basilisk-dev

Profile Information

  • OS
    none specified

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

basilisk-dev's Achievements

123

Reputation

  1. This is incorrect. Pale Moon was always intended to be a browser that was utilized newer CPU optimizations to increase performance. Your claim that it was done with the explicit intention of running on older CPUs is false, although that is an unfortunate side effect of enabling the AVX instruction set. There is absolutely a noticeable performance improvement when comparing the AVX builds to the pre-AVX builds. I disagree with the requirement to have AVX instruction support to run Pale Moon and I think it was a bad move on Moonchild's part, but basically every claim here that you've made is either false or misguided.
  2. The site works fine for me on both ARM MacOS and aarch64 Linux.
  3. I am working on a fix right now. You are welcome to contact me here or on the Basilisk GitHub mirror if you are unable to contact me on the Pale Moon Forum or Pale Moon repo. There is also an official subreddit at https://old.reddit.com/r/basiliskbrowser
  4. I am not doing this, I considered doing it to prevent buggy code being pushed to roytam1's users, but I never decided to actually go forward with it. What's sad is that roytam1 continues to release code to his users that has not been verified as production ready. Code in the master branch of upstream UXP or upstream Basilisk is not always production ready. I have seen issues reported on MSFN for roytam1's builds because he was pulling code from master branches before they were ready. He is doing a disservice to his users by giving them potentially buggy code.
  5. Basilisk releases use the date for the version, for example "2023.11.05" is the most recent release of Basilisk. Basilisk release builds are compiled with "export BASILISK_VERSION=1" in the .mozconfig. Internally Basilisk releases present themselves to addons as "52.9.date" rather than just "date". This ensures that Basilisk works with extensions that were developed for Firefox 52. The 52.9.date internal version as well as the date version number comes from the confvars.sh shell script: https://repo.palemoon.org/Basilisk-Dev/Basilisk/src/branch/master/basilisk/confvars.sh You can also set BASILISK_VERSION to a date if you want to specify a date. For example, if you do "export BASILISK_VERSION=2023.12.01" then the Basilisk version number will be 2023.12.01. This functionality is in the above shell script as well. If "export BASILISK_VERSION=1" is not present in the .mozconfig then the version defaults to 52.9.0. This is the reason that Serpent uses 52.9.0 as the release number. 52.9.0 comes from the txt files in the basilisk/config directory:https://repo.palemoon.org/Basilisk-Dev/Basilisk/src/branch/master/basilisk/config
  6. This happens for me even in Basilisk. I was never able to figure out why, sometimes archive.org works for me and sometimes it doesn't.
  7. Here you are: https://repo.palemoon.org/Basilisk-Dev/Basilisk/commit/894aab8cb56b34f1396c2471e5d792ba6fee893a https://repo.palemoon.org/MoonchildProductions/Pale-Moon/pulls/1928 After seeing all of these domains that are having issues with the Goanna slice I'm now wondering if I should just configure Basilisk to never send the Goanna slice at all.
  8. Support for the marquee element was removed in UXP issue #1525. https://repo.palemoon.org/MoonchildProductions/UXP/issues/1525
  9. I've submitted a PR to Pale Moon to add a User Agent Override for this site: https://repo.palemoon.org/MoonchildProductions/Pale-Moon/pulls/1927 I've also added a User Agent Override to Basilisk: https://repo.palemoon.org/Basilisk-Dev/Basilisk/commit/54ebc66d9d00449d0ad89572f912cef9a8e87d84 On my personal machine I use Basilisk, Pale Moon, LibreWolf. I do have Ungoogled Chromium installed but I only use it if I run into a site that does not work in any of the aforementioned browsers. On my work machine I use Librewolf and Ungoogled Chromium. On my phone I use Mull and the version of Chromium included with Calyx OS. On my Windows 2000 machine I use Serpent and MyPal 68.
  10. Thank you, although I don't think there's anything to congratulate me for. Being nice to others, even if you disagree with them or the things that they do, is not a difficult task (unless your name is Matt A Tobin).
  11. I am the developer of Basilisk as of about a year ago. Moonchild is no longer involved with Basilisk directly. I think you should focus on MyPal 68 for now until you think it is stable enough to divide time between two browsers. Until then people can always use Serpent if they need a Firefox 52 type browser for Windows XP. I use Serpent on my Windows 2000 gaming PC with the BWC extended kernel. I'm obviously biased since I am the developer of Basilisk, but it would be cool to see Centaury continue or restart development at some point in the future if you ever have the time.
  12. I understand your desire to focus on MyPal rather than having your time split between two browsers, but if you ever have the desire to continue Centaury development you have my full permission to do so.
  13. I'm not in the southeastern part of the US, but where I live it is hotter than usual for this time of year. My family who lives in those areas has told me that it's so hot that they basically have to stay inside 24/7, going outside for even 5 minutes is unbearable.
  14. I'm planning on backporting this to Basilisk. When I do @roytam1 will be able to pull my change into Serpent.
  15. I see, according to the UXP issue MS Visual Studio 2017 works with C++14. If they decide to upgrade to C++14 then Visual Studio 2017 can continue to be used. If they go with C++17 then I only see two routes forward: * Switch to mingw/fix mingw builds * backport changes from upstream to work on C++14 For some background on their decision for switching to a newer C++ standard, a major reason that they switched to Visual Studio 2022 in the first place was so that they could switch to newer C++ versions.
×
×
  • Create New...