OMG, #Firefox have added this change in #Nightly where it only shows the domain in the address bar now and I hate it! I genuinely need the rest of the information. I selfhost, so I often need to see the protocol and/or port to see why things aren't working. #FirefoxForAndroid#FirefoxMobile
For anyone unaware, Google Chrome is currently rolling out an update that track your interests based on browsing history, then share them with 3rd party websites. The notification page makes it sound like they added a new privacy feature, but in actuality they automatically enrolled you into their tracking system and you have to go and manually opt out.
@malwaretech@torproject
I have Tor, but it isn't suitable for all things. Neither is FF Klar/Focus and IceCat. I found that Chrome was required for boarding passes for Westjet. It is in Insular (FOSS version of Island- isolated from all apps). So we make do with imperfect combinations. I also recommend Blokada from F-droid. No ads on android and blocked ~200k trackers in a year.
@pallenberg ublock Origin. Seit vielen, vielen, vielen Jahren das erste und wichtigste Add-On auf jedem neuen System. Und der Grund, warum ich auf Android den #FirefoxMobile nutze. #Firefox#ublockorigin
Has anyone else noticed on GitHub that we can't even browse source code now without running their JavaScript? Well, I can't in a FireFox-based browser with privacy plugins anyway. This is just another step down the path to the further enshittification of GH by its small, soft overlords.
If you are still developing Free Code on GH, it's long past time to consider an exodus. There are plenty of community-hosted replacements:
@strypey@tripleo
I just opened one of my public #GitHub repos in #FirefoxMobile on #Android, used the #NoScript extension to block all scripts from both github.com and githubassets.com, and I can still read source code files, browse commit history, etc.
On the mobile site, the page element containing the repo's root directory is hidden by default (presumably to conserve screen real estate). Naturally, un-hiding that hidden page element requires #JavaScript, so that's why the "view code" link doesn't work. However, that's the only part of the mobile site that I could find which requires JS.
A simple fix: Enable the "Desktop site" toggle in your mobile browser settings. 😉