New Firedragon version!

Announcements
103

That is Firefox related, I think. Does this help?

104

I would think it should be the hack since Firedragon is based on Firefox. That said I meant at the bottom of the browser, not under the address bar.

105

That was possible with the old Firedragon?

106

I would assume so since it worked in Firefox before they made some changes. People over the last few years have been able to get it to work again after it was broken with Firefox updates. Iā€™m hoping someone will fix it again in 119.

107

Version 20 is out!
See Post #1 for server link (it hasnā€™t changed).

Changelog:

  • Mozilla Sync back to using Garudaā€™s token. Users should change the URL in their other browsers, according to @BluishHumility precise procedure above
  • 2nd attempt at setting a default User Agent when fingerprinting is disabled. It is now working, set to Windows/FF 121 (must select the CUSTOM User Agent from the UI). However since we use 2 types of FP settings, one of the 2 is not available to be turned ON or OFF through the GUI (FPP). Therefore it is better to set them to false in firegragon.overrides.cfg
pref("privacy.resistFingerprinting", false);
defaultPref("privacy.fingerprintingProtection", false);

I have to decide whether it is better to enable Fingerprinting Protection (the new one from Firefox) or just stick with the normal Fingerprinting. The latter choice would allow users to manage User Agent and Fingerprinting from the UI. If they donā€™t know about the FPP, their User Agent will not change and might cause issues on some websites.

Also the FPP is available on newer versions of FF. I think it was not there by default with 115. Maybe when Floorp will upgrade their FF ESR version it will have that new feature in the UI.

All those scenarios to take into accountā€¦

2 Likes
108

a bit offtopic but maybe the right time.

like I was saying in my post linked at the end of this post, for a new user the garuda custimizations can have sideeffects that are hard to find if there is no information that there are specific overrides.

the fingerprinting for example also bugged me for weeks after my first install, as some icons were just broken and I thought I have a graphics driver problem.

having one place that is updated with the customization choices would have helped me.

best place would probably to start with wiki ā†’ garuda overrides ā†’ firedragon / firefox

especially if you would do a new install of garuda I think you would not get the idea to read firedragon.cfg.pacnew to know about that stuff

109

The difficulty is not the .pacnew file, as this one is super easy to do a compare with firedragon.cfg in the same folder and see what changed.
The difficulty is all the dependencies within Firefoxā€™s possible settings. When you need to disable a pbmode settings that has nothing to do with applying custom color in autofill form fields in a NORMAL window, you then understand things can get very complicated.

I have documented many of those weird things but the best place is in firedragon.cfg, cuz all the settings are there.

The wiki would be used to say ā€œcheck in firedragon.cfgā€. That could still help, though!
And then people need to know there is a wikiā€¦ If the wiki serves as a middleman, not sure. If itā€™s easy for a user to know there is a wiki without asking, then yes. Weā€™ll think about it certainly!

The fingerprinting example is harder to document. That setting can cause various issue types, not all can be documented if you donā€™t know all of them. It gets even worse when it is used in combination with certain other privacy settings. The most important limitations I have documented in firedragon.cfg. But I donā€™t think documenting what each setting can cause as issues is a good approach. This will get very complicated very quickly and the maintenance of it would be huge, especially when a config file has hundreds of settings in it. Adding to that the fact a user can change a setting from the UI or about:config and then it can cause conflicts Garuda couldnā€™t think about, so back to square one.

Trust me, that documentation/communication issue has made me scratch my head non-stop for a few weeks, nowā€¦

2 Likes
110

He doesnā€™t know Firedragon is even better! :rofl:

4 Likes
111

Matter of preference. I went to Waterfix cause the Tabbar at the bottom above the Statusbar is a must for me.

112

well, i can only talk from my perspective.

If there would have been a wiki entry like:

page: Garuda Customizations.

topic: security

"we do optimizations to security in firefox / firedragon. they can in some cases lead to sideeffects. You can see all modifications in file ā€œlink to github or description where to find it in systemā€

the wiki is already default bookmark in default browser and prominent in garuda welcome.
the detailed description should be only in code / git, so you can also see history of why something was implemented, see issues etc.

that would have been enough for me for the FF firedragon stuff.
could of course be extended

then that page could also be linked from the hompage because those are actual good features!
so I would have even known before choosing and installing Garuda.

1 Like
113

Iā€™m thinking of linking a wiki page in the Sidebar. Attempts to modify by default what shows up in there failed, but time will tell. There are a lot of activities to look into with this big browser update.

114

Major Version 11.8.0 is out!
And available in Chaotic repo (the one in Post #1).

Release Notes

Garuda changes included in 11.8.0

  • None. :slight_smile:
115

I appreciate this question is really late, but Iā€™ve got to ask.

Firedragon usesā€¦

I have looked through the list of what it does and it looks really impressive, but Iā€™m wondering if Firedragon is utilising speculative loading.

Iā€™ve got limited bandwidth and I personally wouldnā€™t to use this part of FastFox as it could potentially cause me problems.

116

It does not, I have removed that part when I moved over the FastFox tweaks.

/** [SECTION] PREFETCHING AND SPECULATIVE CONNECTIONS
 * Disables prefecthing for different things such as links, bookmarks and predictors.
 */
pref("network.predictor.enabled", false);
pref("network.prefetch-next", false);
pref("network.http.speculative-parallel-limit", 0);
defaultPref("browser.places.speculativeConnect.enabled", false);
// Disables speculative connections and domain guessing from the urlbar
defaultPref("browser.urlbar.speculativeConnect.enabled", false);
117

Thatā€™s great.

:100:

1 Like
118

And 11.8.1 is already out!

Thatā€™s not me, it came from Floorp. They added a few more fixes.

119

Step 5 is the only necessary one for upgrading after initial install, right?

120

Step 5 is a must yes.
Step 1 that says Close FD is advisable too, but not the backup part.
Step 8 must be checked too, so you can compare files and see changes yourself. In the end if you want to benefit from the changes you must integrate them in firedragon.cfg (or firedragon.overrides.cfg depending on how you manage that, but itā€™s always better to have the default files in the right place first and build from that on your own side, so copying the .pacnew over firedragon.cfg is best. After you revise changes, of course.)

121

A few more fixes? Thatā€™s a bit of an understatementā€¦

122

They pretty much just added this

Fixed some workspace bugs (related to side effects of some bugs that were suddenly discovered)
Various bug fixes regarding vertical tab design
Refactored vertical tabs and removed some functionality.

This is 11.8.0