#firefoxnightly — Public Fediverse posts

@MsDropbear42

So, I was going to my bank's website and for some reason it kept hanging ssh which I use as a dynamic socks proxy. After a few tries, I launch ssh with -vvv to see what's going on (I've seen hangs before due to dns lookups, so wanted to see what domain), and so I load it again and going to my bank website again I want the queries and on of them was for ads . Mozzila.

I then go to my config and find a few ad related options turned on. I'll provide screen shots and exact verbage when I get back to my computer. But this was definitely after I had turned off some of the tracking stuff from a year or two ago.

This is also NOT on nightly.

#FirefoxNightly #FUD

Firefox Nightly mit neuem Profilmanager - LinuxNews.de
https://linuxnews.de/firefox-nightly-mit-neuem-profilmanager/

#Mozilla #Browser #Firefox #FirefoxNightly #Profilemanager

Just did a small batch of #ArchLinux updates, a couple of days after the bigger last lot that included lovely #KDEPlasma 5.27.0, logged out & toggled to tty2, used #needrestart to restart the various services sans-reboot, toggled back to #SDDM & logged back in, then before relaunching my #FirefoxNightly, #Goodvibes & #Thunderbird [all in #Firejail ofc] i took a moment to gaze contemplatively at my #Wayland desktop, & reflected for the umpteenth time; how GREAT is #FOSS!! 🎉

#PlasmaParadise

TIL that with #FirefoxBeta now having jumped to v111, it has inherited #FirefoxNightly's Wayland-autodetection, such that in a Wayland session, to launch Beta as a full-W app, not merely an Xwayland one, you no longer need to use the prefacing `MOZ_ENABLE_WAYLAND=1` environmental variable in your command launcher. Nightly has had this for *several* versions, & my only surprise is that it's taken this long for it to flow down to Beta.

TIL that with #FirefoxBeta now having jumped to v111, it has inherited #FirefoxNightly's Wayland-autodetection, such that in a Wayland session, to launch Beta as a full-W app, not merely an Xwayland one, you no longer need to use the prefacing `MOZ_ENABLE_WAYLAND=1` environmental variable in your command launcher. Nightly has had this for *several* versions, & my only surprise is that it's taken this long for it to flow down to Beta.

TIL that with #FirefoxBeta now having jumped to v111, it has inherited #FirefoxNightly's Wayland-autodetection, such that in a Wayland session, to launch Beta as a full-W app, not merely an Xwayland one, you no longer need to use the prefacing `MOZ_ENABLE_WAYLAND=1` environmental variable in your command launcher. Nightly has had this for *several* versions, & my only surprise is that it's taken this long for it to flow down to Beta.

TIL that with #FirefoxBeta now having jumped to v111, it has inherited #FirefoxNightly's Wayland-autodetection, such that in a Wayland session, to launch Beta as a full-W app, not merely an Xwayland one, you no longer need to use the prefacing `MOZ_ENABLE_WAYLAND=1` environmental variable in your command launcher. Nightly has had this for *several* versions, & my only surprise is that it's taken this long for it to flow down to Beta.

#KDEPlasma #WindowRules #Wayland

Both these work fine in Wayland; #Firefox & #FirefoxNightly [ie, reliably, on launch in Plasma Wayland sessions, without any manual user intervention then needed, both these browsers correctly are stripped of their window decorations & titlebars].

Otoh, this fails 100% of the time; #FirefoxBeta [ie, this browser always still retains window decoration & titlebar in Plasma Wayland].

Any gurus here know why, pls? 🤷‍♀️

#KDEPlasma #WindowRules #Wayland

Both these work fine in Wayland; #Firefox & #FirefoxNightly [ie, reliably, on launch in Plasma Wayland sessions, without any manual user intervention then needed, both these browsers correctly are stripped of their window decorations & titlebars].

Otoh, this fails 100% of the time; #FirefoxBeta [ie, this browser always still retains window decoration & titlebar in Plasma Wayland].

Any gurus here know why, pls? 🤷‍♀️

#KDEPlasma #WindowRules #Wayland

Both these work fine in Wayland; #Firefox & #FirefoxNightly [ie, reliably, on launch in Plasma Wayland sessions, without any manual user intervention then needed, both these browsers correctly are stripped of their window decorations & titlebars].

Otoh, this fails 100% of the time; #FirefoxBeta [ie, this browser always still retains window decoration & titlebar in Plasma Wayland].

Any gurus here know why, pls? 🤷‍♀️

#KDEPlasma #WindowRules #Wayland

Both these work fine in Wayland; #Firefox & #FirefoxNightly [ie, reliably, on launch in Plasma Wayland sessions, without any manual user intervention then needed, both these browsers correctly are stripped of their window decorations & titlebars].

Otoh, this fails 100% of the time; #FirefoxBeta [ie, this browser always still retains window decoration & titlebar in Plasma Wayland].

Any gurus here know why, pls? 🤷‍♀️

@schoentoon
I agree. #FirefoxFocus might actually be the one who handles it the best (though I would like to see more details and an option to exempt the page (temporarily)), as #FirefoxNightly and #FirefoxPreview just showing a broken padlock when I explicitly try to visit an httpS page, without any clear popup notification, or details why it is insecure, is just as bad imho as #GoogleChrome showing a green padlock...

okay, that's weird...
Using #GoogleChrome on #Android the #tcrf site loads without issues, and shows there's an #SSLCertificate present, issued by #LetsEncrypt:
https://mastodon.social/media/ZP6e6gYlMJ7hqj2eBX4

However, it completely refuses to load via @mozilla #FirefoxFocus:
https://mastodon.social/media/NhIGy4-jHenpc7xBAZw

And #FirefoxNightly loads the page, but says it's 'insecure' and doesn't seem to present an #SSL cert at all? Or at least 'Certainly Something' doesn't seem to detect it:
https://mastodon.social/media/W-QMXjbCtzzm6oCQLr4

https://tcrf.net/The_Cutting_Room_Floor