My personal suggestion would actually be that customers stop using those customisations. As noted, the repo is now intentionally inaccessible and it is not clear whether that will ever change in the future and/or whether the customisations are now maintained v. abandonware. etc. etc.
I could re-upload the clone that I have of the original repo if that would help find if itās malicious or not⦠Donāt have a Codeberg yet, so why not?
Sure, but someone will need to maintain the repository.
Fat chance at me being able to do it, I have a surface-level knowledge
Yes, exactly. Two considerations:
- someone needs an accurate clone of the original
- someone needs to step up and maintain it.
If these customisations provide substantial benefit still and noone is going to maintain the repo then it might as well be rolled into the official PureOS distro.
But if they are starting to suffer from bitrot, as Firefox makes incompatible changes and for other reasons, and noone is maintaining it then best just abandon.
Start with uploading the clone to Codeberg or another forge of your choice, then we can wait to see if anyone is interested in updating and maintaining the codebase thereafter.
From @linmobās mastodon:
I just tagged a new #mobileConfigFirefox release Making sure you're not a bot!
If you long for major improvements, donāt get your hopes up - this release ships what weāve in master had since mid April, making the urlbar experience a tad less bad on ESR 140 and release (142). Weāve kept changes intentionally small to not put much rebasing-pain on other changes that have been in the works. Yes, I am talking of the changes demo-ed Danny Colin: "I've been working on a rewrite of mobile-config-fā¦" - FLOSS.social here ![]()
⦠not sure if this is just Postmarket specific, though.
So Firefox ESR 140 had just landed for me and Firefox is once again broken. Iāve installed mobile-config-firefox from PostmarketOS and immediately very dearly missed Emmaās work ![]()
Could you be more specific about what is broken? I have Firefox ESR 140.3.0 and firefox-esr-mobile-config 4.6.0 and itās working for me.
Maybe ābrokenā is too big a word. But I dislike the additional tab bar:
And uBlock Origin is not usable anymore (too big and unscrollable):
I wonder if somebody knows how to contact Emma? Maybe we can get her to do some contract work that updates her user chrome to Firefox ESR 140?
Otherwise Iāll have to vibecode something together ![]()
Trust your vibes.
Go with the vibe.
Yeah, mobile-config-firefox is not where I would like it to be currently.
The main issue is that we still have to support (the IMHO horribly old and terrible with touch screens) Firefox ESR 128 for Alpine 3.22/postmarketOS 25.06, and you canāt really fix much for ESR 140 / release 143 in CSS without introducing breaking ESR 128 at the same time.
Now, there are ways to solve this (like shipping different CSS modifications for 128 and 140++), but sadly, those donāt exactly grow on trees, either.
Following latest posts, I lost 2h of my precious life trying to adapt firefox to Librem 5 screen on PostmarketOS with Plasma without success! Iām tired! Thatās why mobile market is dominated by Apple and Google!! I canāt use firefox on PostmarketOS + plasma (and I tried both flatpak and apk installations) + suggestions from AIs! Why, why community still missing fix it if firefox is so important?
So Iāve to use angelfish with all limitations. Just to mention three:
-
no addons
-
no about:config
-
no lmarena website (compulsory for me)!
@carlosgonz thatās why people still selling their Librem 5ā¦
Ok so:
-
let me bully the bullies



-
why community chosen angelfish instead of Firefox?
Angelfish it is pure QT chromium mobile browser for Plasma mobile. Firefox it is not QT but GTK like Phosh.
To be honest the Librem 5 native mobile browser it is Epiphany, which it is extremly nice.
Our hero dos shipped tons of improvements recently to Gnu crimson epiphany(not yet release), i like Epiphany
Ok AI is helping me to understand:
Why postmarketOS + Plasma Mobile optimized Angelfish instead of Firefox
Technicalāorganizational reason Plasma Mobile is a KDE project. KDE also develops QtWebEngine (the technical base of Angelfish). Thus Angelfish is the āināhouseā browser, written in the same language (Qt/QML) and using dependencies already present in the system. Firefox is written in GTK and uses Gnome libs ā a different technology. Including it on Plasma means adding half a world of GTK libraries that KDE developers would have to maintain just for one app. For a lightweight mobile project (postmarketOS + Plasma), that would be a considerable burden.
āMobileā reason Angelfish was designed from the very beginning for small screens and a touch interface. Firefox: no ā it exists as a desktop browser and as an Android version, but the Android one uses Java and Graal libraries not ported to Linux ARM. So the KDE community was able to adapt Angelfish right away, while Firefox would have needed deep patches like those from Purism (lots of work, little time).
āProject philosophyā reason postmarketOS aims to create a system completely independent of closed or monolithic components. Firefox, in its Flatpak packaging, includes preācompiled Rust subcomponents and sandboxed portions. Angelfish, on the other hand, is built directly from KDE sources, so itās more transparent. In short: for technical consistency and practicality, plasmaāpostmarketOS chose its own KDE browser ā not out of hostility toward Firefox, but because itās simpler to integrate and more efficient on mobile hardware.
Then it continue showing a matrix with differences! Very interesting! So with Dawn we can say goodbye to Firefox!
Without GLES3 peoples Do Not need to install FF on L5. Firefox can be accidentally installed on a mobile-machine that supports GLES3, otherwise it will create a CPU bottleneck.
So as Librem 5 it is a modular device, imagine using also a modular Framework for system like QT, even better super-optimized for embeded mobile device?
Sadly GTK and Gnome are very obsessed with Apple Electronics, and iOS desing.
The dream for Gnome fundation is to get Phosh on iphone 17 than L5. IMHO
I so sorry to be too toxic, but i super tired on Gnome work.
AI is teaching me that I could use flags with angelfish as substitution for about:config and addons on Firefox (eg: angelfish --incognito --disable-remote-fonts --no-sandbox) so, that makes me feel happy! Carlos donāt care to Gnome evolution, donāt be sad! Itās not worth getting upset about different choices ![]()
Everybody will follow what prefer! Fortunately weāve options, differently from Apple and Google users ![]()
Hope @dos will release Dawn as soon as possible so we can begin to try and test it!
Dear @dos , please, some news about first release?
Thank you

