Jump to content

basilisk-dev

Member
 View Profile  See their activity

  • Posts

    30

  • Joined

  • Last visited

  • Days Won

    2

  • Donations

    0.00 USD 

  • Country

    United States

 Content Type 

Everything posted by basilisk-dev

  1. basilisk-dev
    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.
  2. basilisk-dev
    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
  3. basilisk-dev
    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.
  4. basilisk-dev
    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.
  5. basilisk-dev
    Support for the marquee element was removed in UXP issue #1525. https://repo.palemoon.org/MoonchildProductions/UXP/issues/1525
  6. basilisk-dev
    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.
  7. basilisk-dev
    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).
  8. basilisk-dev
    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.
  9. basilisk-dev
    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.
  10. basilisk-dev
    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.
  11. basilisk-dev
    I'm planning on backporting this to Basilisk. When I do @roytam1 will be able to pull my change into Serpent.
  12. basilisk-dev
    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.
  13. basilisk-dev
    What build environment are you using? What OS/MSVC/etc?
  14. basilisk-dev
    Off topic, but not too long ago 3 year old kid decided to play with our Apple TV remote (my wife uses an Apple TV for media streaming) and was hitting random buttons on the remote. He purchased GhostBusters: Afterlife for $30 before I realized that he had the remote as I was in the next room over washing some dishes. The movie was definitely not worth the $30 he spent on it. It was terrible. Needless to say I enabled the parental controls on the Apple TV after that.
  15. basilisk-dev
    What I meant here is that I can help roytam1 with whatever assistance he may need to continue Serpent and any of his other XP browser projects. Some examples could include paying for a server to host a git repo that is accessible in China/HK, providing mirrors of his builds, or providing him with a mirror of the UXP/Pale Moon/Basilisk/etc codebases that is accessible from China/HK, etc. MyPal 68 is not compatible with XUL extensions. I have no interest in non-XUL based Firefox browsers.
  16. basilisk-dev
    If there is anything I can do to help feel free to let me know.
  17. basilisk-dev
    This is false. I release both 32 and 64 bit builds of Basilisk for Windows. Edit: sorry for reviving an old thread, I wasn't paying attention to the dates. Ignore me
  18. basilisk-dev
    @Egorkaru No need to spam this forum topic. It is possible to convert themes from the Mozilla addons site to Serpent 52/Basilisk format, but it will not be easily possible to make them installable directly without converting them first as they are in WebExtension format. New Firefox themes are essentially just personas. In this Pale Moon Forum topic jobbautista9 provides an example of a theme from the Mozilla addons site that he converted into a persona. If someone is interested in the conversion process, it would be useful to review his converted persona and compare the source code of his persona to the same theme on the Mozilla addons site. You'll see in my comment on that topic I provided a link to an old version of the Mozilla addons site on archive.org that has some older themes archived. Some of those themes will install on Serpent 52 and Basilisk.
  19. basilisk-dev
    It is already removed. There is nothing to decide.
  20. basilisk-dev
    The UXP team has already said they have no intention of dropping Windows 7/8 support right now, but if it came down to it yes that is correct. I wouldn't expect that to happen for at least 5+ years.
  21. basilisk-dev
    Correct. I think it's beneficial for Serpent users here and for developers of Windows XP UXP applications to have a direct line of communication with people involved in upstream development. There have been very negative interactions between MSFN members and Pale Moon forum members in the past. I think it is time to move past that and embrace the fact that we all are using code that comes from a shared history and to work towards a common goal of creating browsers that break away from Google's monopoly of the web, regardless of if that code runs on Windows XP or Windows 10 or Linux. This was a consideration when I took over the Basilisk project. I eventually decided that it would not be feasible to do this. Basilisk is an application built upon the upstream Moonchild Productions UXP platform. The upstream UXP platform has no XP support and the UXP development team have no interest in XP support, therefore Basilisk will not have XP support. That being said, if you need Basilisk on XP you can consider Serpent an officially recommended option from my perspective. I appreciate roytam1's work in maintaining Serpent and try to be active in this thread since Serpent is a fork of Basilisk. It is very likely that Serpent bugs will also affect Basilisk. Two reasons: 1 - It was removed from the UXP platform. 2 - There were multiple security vulnerabilities in the multi process implementation that Mozilla was using around the time Firefox 52 was released and UXP was created. Mozilla's current implementation is in Rust so the fixes cannot be backported. There is no plan to add this back at this time.
  22. basilisk-dev
    Agreed. The behavior in that thread was unacceptable. I locked the topic and made it clear that I won't allow that behavior in the forum section for my project. If you see something like this in the Basilisk section of the Pale Moon Forum again feel free to let me know directly.
  23. basilisk-dev
    Yeah, Moonchild says it's a "privacy footgun" but I am not sure how this is the case. I've gotten him to explain it to me before but I still didn't understand his reasoning. Is this a pref that people think should be enabled in upstream Basilisk? If so I can do that. I've been having to enable it to get Basilisk to work for my work sites even before I took over the project.
  24. basilisk-dev
    Nice, glad to hear that it worked. Does it work with Tab Mix Plus?
  25. basilisk-dev
    Yes, I prefer the tab label fading feature rather than elipsis as well. The WebComponents improvements are not ready, which is why they are not merged into Basilisk yet. There are bugs that are still being fixed. I generally do new releases around the same time as Pale Moon releases. My original implementation was a direct backport from Firefox 53 so it is possible that the addon behaves differently between Firefox 52 and 53. I did not check the extension since I don't use it. I plan to reimplement this feature using the same method that the Pale Moon team used (this should preserve backwards compatibility with addons). It will be togglable with a pref just like the Pale Moon feature.
×
×
  • Create New...