New Redistribution and Branding Terms

[Basilisk-Dev]

Effective immediately, there are updated branding and redistribution terms here: https://basilisk-browser.org/branding.shtml

Here are some of the changes made. This may not be all of the changes, please review the page for anything I missed. As always, these changes only apply to officially branded builds and officially branded binaries from the Basilisk site.

* Explicitly ban uploads of Basilisk binaries and branding assets to archive (piracy) sites such as archive.org
* Explicitly ban redistribution of portable versions of Basilisk
* Explicitly ban redistribution of Basilisk official branding files
* Clarify that Linux distributions can repackage official Basilisk binaries, and the ONLY preference they may change is to disable automatic updates (since the package manager will handle them)
* Ban redistribution of Basilisk with changed default preferences (other than the Linux distros disabling auto updates mentioned above)
* Explicitly ban unofficial releases of the official Basilisk binaries that include NPAPI plugins or XUL extensions.
* Update the page to call the unofficial Branding "Snake" instead of "Serpent"

I will also be more aggressively enforcing the branding and redistribution terms going forward. I found a few old forks of Basilisk on GitHub that have the official branding files in place, including some forks by some forum members here. If you have one of these forks, please remove the official branding files by Friday, 30 August or I will send a DMCA request to GitHub.

I am also in the process of purging all "portable" versions of Basilisk from archive.org.

[Pentium4User]

Code: Select all

 * Explicitly ban uploads of Basilisk binaries and branding assets to archive (piracy) sites such as archive.org

Why do you want this?

What about other repos?
Some distribution keep every build/package in an archive forever. Will they be affected too?

[moonbat]

Why do you want this?

Should be obvious - these are unauthorized builds/bundles that may not work, be out of date or contain additional malware - for which users will hold Basilisk-Dev responsible. The same terms apply to PM and most other software distribution terms also.

[Basilisk-Dev]

Why do you want this?

What about other repos?
Some distribution keep every build/package in an archive forever. Will they be affected too?

I really only care about unofficial modifications to the official Basilisk binaries on archive.org. I found a bunch of bundles that include Adobe Flash and change default prefs for example.

Git repos don’t matter to me as long as the official branding files aren’t present in those repos.

Linux distribution packages don’t matter to me as long as the only change they make is disabling auto updates.