41–50 of 158 posts
Interesting. From a user experience, Firefox for iPhone has been a really excellent app, it’s been my preferred browser for years.
Even if it’s basically a skin for Safari?
Earlier quoted context omitted.
> 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?
Sites where users each get a directory for their profile.
Do this require a browser probing every path with /favicon.ico?
[flagged]
Are you commenting on the right post mate?
Of course he could’ve just gotten the link from Google Images and not noticed.
But I would rather like to imagine that he himself is one of the “Redditors” he apparently so vehemently despises.
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
Would you kindly refrain from blaming users for what clearly is a bug in the application?
Earlier quoted context omitted.
Also, when I saw the headline, I had to think of all the LLM scrapers and bots (soon to be running directly on your AIphone!) roaming the Interwebs.
Just yesterday I blocked the bots from my blog using this[1]. Of course whether these bots respect robots.txt nowadays is a different question altogether [1]: https://github.com/fardog/fardog.io/commit/b2e3eac838ea25209...
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?
Though they aren't common enough that it needs to be a built-in, especially as you can already specify a page specific icon via a link tag in your page's head which every up-to-date stable browser has had support for since 2010 or before (ref: https://caniuse.com/?search=link-icon).