By January 1, 2005, rebranding was being referred to as the "Iceweasel route". It was intended as a parody of "Firefox." Iceweasel was subsequently used as the example name for a rebranded Firefox in the Mozilla Trademark Policy, and became the most commonly used name for a hypothetical rebranded version of Firefox. The first known use of the name in this context is by Nathanael Nerode, in reply to Eric Dorland's suggestion of "Icerabbit". During this debate, the name "Iceweasel" was coined to refer to rebranded versions of Firefox. This policy led to a long debate within the Debian Project in 20. Unless distributions use the binary files supplied by Mozilla, fall within the stated guidelines, or else have special permission, they must compile the Firefox source with a compile-time option enabled that creates binaries without the official branding of Firefox and related artwork, using either the built-in free artwork, or artwork provided at compile time. The Mozilla Corporation owns the trademark to the Firefox name and denies the use of the name "Firefox" to unofficial builds that fall outside certain guidelines. In addition, it includes several security features not found in the mainline Firefox browser. It also maintains a large list of free software plugins. The GNU Project attempts to keep IceCat in synchronization with upstream development of Firefox (long-term support versions) while removing all trademarked artwork and non-free add-ons. Mozilla produces free and open-source software, but the binaries include trademarked artwork. As an internet suite, GNUzilla also includes a mail & newsgroup program and an HTML composer. IceCat is released as a part of GNUzilla, GNU's rebranding of a code base that used to be the Mozilla Application Suite. It is compatible with Linux, Windows, Android and macOS. GNU IceCat, formerly known as GNU IceWeasel, is a completely Free and Open Source version of the Mozilla Firefox web browser distributed by the GNU Project. I used Brave for a few years but switched back to Firefox completely a few months ago.GNU GPLv3 (scripts that make IceCat from Mozilla Firefox) Meanwhile, the latest Firefox versions are quite privacy focused. Of course there are dozens of niche Chrome and Firefox forks like Waterfox, Pale Moon.Įven though these forks may have slightly better privacy options in some ways, maintaining a completely browser is a major engineering undertaking and it's extremely difficult for these forks to try and stay up to date on security issues. If you're determined not to use Chrome or Firefox, and want to focus on privacy while still having everything work, I think Brave may be your best bet for right now. #!!! Error: (msgtype=0x160080,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv WARNING: pipe error (62): Connection reset by peer: file /home/ruben/git/gnuzilla/output/icecat-60.7.0/ipc/chromium/src/chrome/common/ipc_channel_, line 342 WARNING: pipe error (56): Connection reset by peer: file /home/ruben/git/gnuzilla/output/icecat-60.7.0/ipc/chromium/src/chrome/common/ipc_channel_, line 342 out of memory: 0xFFFFFFFFFFFFE610 bytes requested I consistently and repeatably get this error each time the webrtc test is accessing my camera on icecast. If you disable all of icecat's privacy settings and disable librejs, and load the page, it will access the camera and attempt to start webrtc, but it will soon crash. Sorry to be the bearer of bad news on this one, but I don't think getting icecat to work with webrtc is possible without a lot of engineering.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |