Most of Mozilla's money of course comes from Google to make them the default search engine on Firefox. And of course its a way for Google to ensure there's at least one alternative browser engine. Reading about how Texeira was recently fired and how executives have been pushing for AI features for a long time, Mozilla certainly loves chasing trends and then forgetting them, like how Google kills lots of products. It seems like the company can't stand on its own two feet without Google's funding and is poorly run.

What happened to Mozilla over the years? How much effort did they put in to trying to be a successful tech company? because it hasn't been until the past few that I really started following Firefox and Mozilla news.

I wonder if Mozilla could've been Proton, years before Proton AG existed, making their own comprehensive suite of privacy-friendly tools, since Mozilla makes privacy their brand. And they were late to the smartphone game with Firefox OS. If they were smart, they would've ensured their long term survival with an actual business, to continue funding development of their privacy and FOSS software like Firefox, without large funding sources like Google.

Mozilla leadership
(in ref to https://mozilla.social/@mozilla/113153943609185249 )

#comic #firefox #mozilla

That's disappointing. I love #FireFox and #Mozilla but this is the wrong direction. The org doesn't appear to have a strong strategy, constantly moving from VPN, to fedi, to AI. Supporting federated services is such an obviously good long-term play for their mission, so to end their Mastodon instance is unfortunate.

https://www.theverge.com/2024/9/18/24248142/mozilla-will-shut-down-its-mastodon-server-on-december-17th

#Tech

#Mozilla #Firefox 130.0.1 is out now to fix black rendering of AVIF images on #Linux when Firefox is built with GCC and a recent regression causing some UI elements to be rendered as left-to-right instead of right-to-left for users of the Saraiki localization. Download at https://www.mozilla.org/en-US/firefox/130.0.1/releasenotes/

#OpenSource #FreeSoftware

#Mozilla #Firefox 130.0.1 is out now to fix black rendering of AVIF images on #Linux when Firefox is built with GCC and a recent regression causing some UI elements to be rendered as left-to-right instead of right-to-left for users of our Saraiki localization. Download at https://www.mozilla.org/en-US/firefox/new/

#OpenSource #FreeSoftware

Native support for ed25519/x25519 in the browser would be a huge step forward for in-browser/client-side cryptography.

Looks like Google is holding up our ability to use it in production.

(Firefox and Safari both have support enabled by default.)

https://caniuse.com/mdn-api_subtlecrypto_sign_ed25519

#ed25519 #x25519 #cryptography #browsers #web #mozilla #apple #google #firefox #safari #chrome #privacy #security #WebCryptoAPI

If you update a laptop from Ubuntu 22.04.3 to 24.04.1 and the screen is blank with an 'x' cursor after login, do this:

1. control+alt+F1 to go to a tty and login, then:
2. sudo apt install --reinstall ubuntu-session

Further, if #thunderbird doesn't launch, remove the snap installation and install de deb package directly from mozilla (he --purge is so that it doesn't generate adn store a ~4 GB copy of the install). First, do:

$ sudo snap remove --purge thunderbird
$ sudo add-apt-repository ppa:mozillateam/ppa
$ sudo apt update

Then paste this below into a file ( /etc/apt/preferences.d/mozillateamppa-thunderbird ) to tell the apt system that you prefer mozilla's over any other package:

Package: thunderbird*
Pin: release o=LP-PPA-mozillateam
Pin-Priority: 1001

... and install:
$ sudo apt install thunderbird

The same can be done for firefox if you'd rather skip the snap package.

#ubuntu #mozilla #thunderbird #firefox #linux

I'm using Firefox with uBlock Origin on both android and windows. I'm finding more and more sites that are very slow to load, or won't load at all. Yet when I open them in Chrome they work fine. I'm assuming the sites are just failing because of the privacy protection features of ff+ubo, and I'm happy enough to just avoid these shitty sites in general. But - I'm just checking to see - is this expected behaviour, might I have configuration issues?

Say NO to AI in the #Firefox browser - have your say here;

https://connect.mozilla.org/t5/discussions/share-your-feedback-on-the-ai-services-experiment-in-nightly/td-p/60519

https://github.com/Abev08/VolumeControlExtension

That's two longstanding items on my firefox wishlist taken care of by an extension: Actual working volume controls on the built-in media player, and a volume control for other crappy web players that don't have them.

#firefox

I am quite happy they added the borders, but I know some people use high-contrast themes as a base for their own theming and don't want this, in this case, add this to your userChrome.css:

:root {
  --toolbarbutton-outline: none !important;
}

#Linux Weekly Roundup for September 8th, 2024: #Firefox 130, #GNOME 47 Release Candidate, #QEMU 9.1 improves #ARM and #RISCV support, #KDE #Slimbook Plasma VI laptop arrives at #Akademy2024, Firefox 131 enters beta testing with text fragments and temporary site permissions, #Nitrux 3.6.1, #Audacity 3.6.2 brings back legacy effects, and more https://9to5linux.com/9to5linux-weekly-roundup-september-8th-2024

#OpenSource #FOSS

I’m trying to set containers for some websites on a shared windows terminal with multiple users under the same login. We use some cloud software and each user has their own log in. Manually opening websites in container manager allows this, but I’m struggling to do so for opening in container for the home page.

Each log in just launches in the default container (unassigned). I’ve tried using bookmark tree, which seems to support containers, but I can’t get it to work. Assigning a site to always open in a container doesn’t seem to work either as it’s the same site for multiple users (which seems to be the purpose of multi account container), so if it always opens in container A, person B still needs to manually open in their container.

#firefox #chrome #ublockOrigin

Finally, #Mozilla #Firefox for #Linux scales correctly depending on the OS setting instead of it being huge. This had been an issue since they removed the “Density: Compact” option.

version: 131.0b1

#Mozilla #Firefox 131 Enters Public Beta Testing, Improves Translations and Adds Temporary Site Permissions https://9to5linux.com/firefox-131-beta-improves-translations-adds-temporary-site-permissions

#OpenSource #FreeSoftware #Linux

#Mozilla #Firefox 130 Open-Source Web Browser Is Now Available for Download, Here’s What’s New https://9to5linux.com/mozilla-firefox-130-is-now-available-for-download-heres-whats-new

#FreeSoftware #Linux

Dwa pytania do osob korzystajacych z #Linux.a, #Firefox.a i najlepiej z wtyczki #Sidebery (bo o nia tu glownie chodzi)

1. Nad paskiem z zakladkami / tabami wyswietla mi sie taki "tytul" - nie pamietam, zebym w wersji Windowsowej to mial i musial usuwac, w necie znalazlem instrukcje jak usunac to wpisem w pliku css, ale nic to nie dalo jak widac

2. Sidebery z uporem maniaka otwiera mi linki z zakladek ciagle w tej samej karcie przegladarki, jak go zmusic, zeby robil to w nowych kartach? W ustawieniach wtyczki nie widze nic co by za to odpowiadalo

#help #pomoc #FediPomoc #software #przegladarka

Im Mai 2024 habe ich Mozilla über einen Datenschutzverstoß in Firefox (Android) informiert. Ohne Zustimmung des Nutzers wurden Daten an Adjust übermittelt. In der Version 129.0.2 (Android, iOS) wurde Adjust nun entfernt - vermutlich als Reaktion auf meine Analyse. Ich werde aber noch einmal nachhaken. 👇

https://bugzilla.mozilla.org/show_bug.cgi?id=1913363

https://www.kuketz-blog.de/firefox-datenschutzverstoss-bei-der-android-version/

#mozilla #firefox #adjust #tracking #dsgvo #tdddg

#Linux Weekly Roundup for August 25th, 2024: Linux's 33rd birthday, #LibreOffice 24.8, #NVIDIA 560 hits stable, #KDE Gear 24.08 improves your favorite KDE apps, #GNOME 47 enters public beta testing, #SerpentOS alpha is around the corner, #ArchLinux installer gets COSMIC desktop support, #PipeWire default for camera handling in #Firefox on #Fedora Linux 41, #fwupd improves support for #Dell systems, and more https://9to5linux.com/9to5linux-weekly-roundup-august-25th-2024

#OpenSource #FOSS

An update on Mozilla's PPA experiment and how it protects user privacy while testing cutting edge technologies to improve the open web.

I look left and right, and I'm the only one who…

TL;DR: Firefox used to have a great extension mechanism based on the XUL and XPCOM. This mechanism served us well for a long time. However, it came at an ever-growing cost in terms of maintenance for both Firefox developers and add-on developers. On one side, this growing cost progressively killed any effort to make Firefox secure, fast or to try new things. On the other side, this growing cost progressively killed the community of add-on developers. Eventually, after spending years trying to protect this old add-on mechanism, Mozilla made the hard choice of removing this extension mechanism and replacing this with the less powerful but much more maintainable WebExtensions API. Thanks to this choice, Firefox developers can once again make the necessary changes to improve security, stability or speed. During the past few days, I’ve been chatting with Firefox users, trying to separate fact from rumor regarding the consequences of the August 2020 Mozilla layoffs. One of the topics that came back a few times was the removal of XUL-based add-ons during the move to Firefox Quantum. I was very surprised to see that, years after it happened, some community members still felt hurt by this choice. And then, as someone pointed out on reddit, I realized that we still haven’t taken the time to explain in-depth why we had no choice but to remove XUL-based add-ons. So, if you’re ready for a dive into some of the internals of add-ons and Gecko, I’d like to take this opportunity to try and give you a bit more detail.