Wordpress handles 404s really slowly? I'm kind of surprised it works at all then, as at least in my logs there's a very steady stream of bots probing it for vulnerabilities by trying random URLs.
It's an open source project, with a good discussion of the technical issues on GitHub[1]. Probably linked to certain user behaviors, like having hundreds of tabs open, but surely also contingent on the complexity of wedging a browser in iOS. Like maneuvering an excavator into a sandbox.
I also wonder how these requests "beat the shit out of the web server." It's requesting the feed and the favicon, both of which could be cached by a CDN. Even if they aren't, how much traffic are you gonna see from this compared to some other page trending on HN? Wasteful, sure, but hardly that big a deal
I can easily have hundreds of Chrome tabs open, and none of this happens. I can have hundreds of tabs inadvertently open in iOS Safari, and none of this happens.
Would you kindly refrain from blaming users for what clearly is a bug in the application?
Given the seriously negative sibling comments, I thought I'd weigh in with my own experience. I'm unaware of anything behind the scenes, but I've always enjoyed the user experience in Firefox on Android, at least for the last couple years before the rewrite. I don't like browsing the web on my phone, but it's made it bearable.
I can't speak to the problems behind the scenes though, and they certainly merit attention.
Firefox on Android is a godsend to me, and the secret is that I can install uBlock origin and noscript on my mobile. I get a whiplash when I see someone else browsing the web without these, it is absurd how much attention people will allow to be just stolen away.
Firefox on Android is NOT amazing. For MANY YEARS the user agent included the exact model of your phone. They seem to be incompetent. (Edit: this is a bit harsh, and to clarify, directed at the company and not any specific people in their employ.) Exactly what Google wants -- plausible deniability when it comes to monopoly, but an awful alternative.
iOS requires a browser to use the OS-provided WebKit, but you can still use your own networking layer, and doing your own scripts injection (e.g. for extensions, like what Orion is doing). Firefox for iOS used to use Alamofire as its networking engine, but switched over to NSURLSession/URLSession at some point. Chrome for iOS uses Cronet which was extracted from Chromium's networking stack (or maybe used, I have not followed the development recently).
> I thought firefox on ios was just safari with a reskin
It is. It does avoid some of the tracking/ad content, so I guess it does do some things somewhat differently. But if it's such a scourge, add a favicon.
BTW, I've never seen this, and I regularly use Firefox on iOS to test.
I'm another who loves firefox on android. It annoys me that to some degree Android forces chrome on you, even if firefox is set as your default. The full plugin support that got added in the last year really took it up a notch too.
The author of this site usually takes pains to obfuscate whatever big commercial entity she's talking about who did dumb stuff. But when it's Firefox, she names names. Huh.
I remember something similar with Internet Explorer back in the day, where it would ask for the favicon (which we didn’t have setup at the time) so our 404 page would be returned, which then seemed to trigger another request for a favicon. (╯°□°)╯︵ ┻━┻
I get it, everything adds up and over millions of page-loads there will be a bit of wasted bandwidth. But it seems the original author blew this issue out of proportion with this post. Why even be annoyed by such a minor issue?
> And yet, this thing decides to beat the shit out of the web server while trying to get it.
This is an exhorbitant exaggeration. They are duplicated requests for a favicon. Not only is that a tiny resource, most of these requests are 404ing which is cheap. And even if it isn't 404, your favicon is a tiny static asset, it should either be served by CDN or in the server's filesystem cache anyways.
Title implies that this article thirdly explains how to waste annoying sysadmins, which is an entertaining prospect.
Are we talking about not putting annoying sysadmins to good use? Or are we talking about, you know, makin sure they don’t cause nobody no trouble again, boss?
> First up, why in the hell do you need to request the same link 12 times? No, scratch that, 15 times, since it does 3 more after getting the css and feed icon.
It makes a debouncing. It compares the result with the previous to be sure it is OK. /s
[+] [-] markerz|1 year ago|reply
Basically Firefox loaded favicons 4x the number of tabs opened to that website. It would do this every time I opened or closed any tab.
https://aggressivelyparaphrasing.me/2022/12/12/why-does-my-l...
It was resolved a while back so maybe it’s similar symptoms but different root cause, or maybe it’s people using older versions?
[+] [-] gwd|1 year ago|reply
[+] [-] aaron695|1 year ago|reply
[deleted]
[+] [-] seism|1 year ago|reply
[1] https://github.com/mozilla-mobile/firefox-ios/issues/12113
[+] [-] yosefk|1 year ago|reply
[+] [-] WesolyKubeczek|1 year ago|reply
Would you kindly refrain from blaming users for what clearly is a bug in the application?
[+] [-] seism|1 year ago|reply
[+] [-] AtlasBarfed|1 year ago|reply
That is, they are just skins
[+] [-] Aardwolf|1 year ago|reply
Firefox on android is amazing with its plugin support, though I still prefer their pre-2021 UI
[+] [-] loufe|1 year ago|reply
I can't speak to the problems behind the scenes though, and they certainly merit attention.
[+] [-] butterNaN|1 year ago|reply
[+] [-] smolder|1 year ago|reply
[+] [-] sirn|1 year ago|reply
[+] [-] tgv|1 year ago|reply
It is. It does avoid some of the tracking/ad content, so I guess it does do some things somewhat differently. But if it's such a scourge, add a favicon.
BTW, I've never seen this, and I regularly use Firefox on iOS to test.
[+] [-] Twirrim|1 year ago|reply
[+] [-] chithanh|1 year ago|reply
* Tabs get stuck frequently, and can only be revived by closing, then undoing close.
* Can no longer access about:config in release builds
* Bookmarks got demoted in favor of Pocket, can no longer set bookmarks as default home page
* URL autocompletion got dumbed down, first on mobile and then also on desktop
* etc.
[+] [-] unknown|1 year ago|reply
[deleted]
[+] [-] jepler|1 year ago|reply
[+] [-] yuliyp|1 year ago|reply
[+] [-] batch12|1 year ago|reply
[+] [-] Aloha|1 year ago|reply
[+] [-] bennettlp|1 year ago|reply
[+] [-] jb1991|1 year ago|reply
[+] [-] rrr_oh_man|1 year ago|reply
[+] [-] userbinator|1 year ago|reply
Having a path-specific favicon actually sounds like a feature.
[+] [-] missblit|1 year ago|reply
https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes...
[+] [-] Kwpolska|1 year ago|reply
[+] [-] justsomehnguy|1 year ago|reply
Can you provide at least a couple of use-cases for a path specific favicons?
[+] [-] chime|1 year ago|reply
[+] [-] vasco|1 year ago|reply
[+] [-] alexchamberlain|1 year ago|reply
[+] [-] perfect_wave|1 year ago|reply
[+] [-] johnp_|1 year ago|reply
[+] [-] shantara|1 year ago|reply
[+] [-] yokoprime|1 year ago|reply
[+] [-] ggm|1 year ago|reply
[+] [-] lopkeny12ko|1 year ago|reply
This is an exhorbitant exaggeration. They are duplicated requests for a favicon. Not only is that a tiny resource, most of these requests are 404ing which is cheap. And even if it isn't 404, your favicon is a tiny static asset, it should either be served by CDN or in the server's filesystem cache anyways.
[+] [-] fnord123|1 year ago|reply
[+] [-] justsomehnguy|1 year ago|reply
[+] [-] mock-possum|1 year ago|reply
Are we talking about not putting annoying sysadmins to good use? Or are we talking about, you know, makin sure they don’t cause nobody no trouble again, boss?
[+] [-] hulitu|1 year ago|reply
It makes a debouncing. It compares the result with the previous to be sure it is OK. /s
[+] [-] unknown|1 year ago|reply
[deleted]
[+] [-] r3db34rd|1 year ago|reply
[deleted]