31–40 of 158 posts
It's not part of individual directories. That would be stupid. Having a path-specific favicon actually sounds like a feature.
> Having a path-specific favicon actually sounds like a feature. Can you provide at least a couple of use-cases for a path specific favicons?
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. [1] https://github.com/mozilla-mobile/firefox-ios/issues/12113
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
Earlier quoted context omitted.
I thought all browsers on iOS were using the apple browser engine and ditto for Android. That is, they are just skins
They are using the WebKit rendering engine, but there’s a lot more to a web browser than just its rendering engine. They aren’t just skins.
Earlier quoted context omitted.
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
404s don't get cached. At least I don't configure anything to cache them.
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. [1] https://github.com/mozilla-mobile/firefox-ios/issues/12113
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 get that not every client is well behaved, but you'd hope that Firefox would be, given Mozilla's presence in web standards.
(Which, tbh makes me think this issue is the "on iOS" bit, given it's Firefox. I presume Apple still has their "only Safari's rendering engine" rule in place for... ...reasons)
[flagged]
This isn't a very constructive post. Are we supposed to believe this is the only inefficient and buggy software out there? Seems weird to call out a particular project like that.