Live data from Hacker News

Apple's whitelist of the 250k auto-completable domains in iOS

cdn.smoot.apple.com

101–110 of 182 posts

Re: Apple's whitelist of the 250k auto-completable domains in iOS

#101

My competitor is in this list and I'm not, even though my site is more popular. There even are some small Dutch campings, municipalities and regional football clubs on this list. It's a strange list for sure.

Neither I nor my largest competitor are on the list, which is fair enough. However a now-defunct domain which my competitor previously used for their hiring portal is on the list. Weird!

Re: Apple's whitelist of the 250k auto-completable domains in iOS

#102
post #19

Ha! This explains why I always get "cookieandkate.com" suggested when I want to visit another site that starts with "cookie". I was extremely frustrated that it suggested that site with higher priotity than the one I actually visit mostly every day. And I had never myself gone to that site. Now I know why...

That's very strange, you'd expect Apple to provide a good UX by suggesting a website from your bookmarks, history and then their list. I wonder whether that's an oversight or an intentional implementation.

That's exactly the behaviour I have when using iOS.

Re: Apple's whitelist of the 250k auto-completable domains in iOS

#103

Earlier quoted context omitted.

Interesting! Perhaps it could even post a comment to an issue so people can subscribe to it.

Good idea! I’ve created an issue[0] that can be subscribed to, I will implement the feature soon. [0]: https://github.com/b0o/apple-autofill-domains/issues/1

Random q: why fetch depth 20?

Re: Apple's whitelist of the 250k auto-completable domains in iOS

#104
post #102

Earlier quoted context omitted.

That's very strange, you'd expect Apple to provide a good UX by suggesting a website from your bookmarks, history and then their list. I wonder whether that's an oversight or an intentional implementation.

That's exactly the behaviour I have when using iOS.

I see. OP replies saying their history somehow expired, and the page wasn't bookmarked to begin with. So I stand corrected. Thank you

Re: Apple's whitelist of the 250k auto-completable domains in iOS

#105

Ugh, I guess that's why the iOS browsers all suck so hard with autocomplete? I always long for Firefox's url bar, it easily beats everything else since Firefox 2 came out or so. Nowadays you have to un-configure two layers of "let's put a search bar in your URL bar" but then it's still just amazing. Especially compared to google, which obviously doesn't have an incentive to have you skip searching on google.com... an…

> Ugh, I guess that's why the iOS browsers all suck so hard with autocomplete? No. Contrary to popular belief, browsers on iOS aren’t all Safari skins. They all use WebKit, but there’s a vast amount of functionality in a web browser that isn’t handled by the rendering engine. This is one example. Non-Safari browsers on iOS are free to use whatever address bar implementation they like. If Firefox on iOS has a crap add…

right, it's just about the rendering part. so yeah, firefox can do that. I haven't really paid attention to this since I don't personally use apple devices. I'll make sure to pay attention to it though next time I use my girlfiend's ipad. I already installed firefox on there just to have a sane browsing experience, but it wasn't specifically for the autocompletion.

Re: Apple's whitelist of the 250k auto-completable domains in iOS

#106
I was at first guessing this this might have had as a (partial) data source the hsts static preload list[1]. But, a domain I know we never submitted to it was on there while one which was submitted (but has since aged out) is not. Also these lists are so absurdly large

[1] https://cs.chromium.org/chromium/src/net/http/transport_secu...

Re: Apple's whitelist of the 250k auto-completable domains in iOS

#107

Earlier quoted context omitted.

> Ugh, I guess that's why the iOS browsers all suck so hard with autocomplete? No. Contrary to popular belief, browsers on iOS aren’t all Safari skins. They all use WebKit, but there’s a vast amount of functionality in a web browser that isn’t handled by the rendering engine. This is one example. Non-Safari browsers on iOS are free to use whatever address bar implementation they like. If Firefox on iOS has a crap add…

>No. Contrary to popular belief, browsers on iOS aren’t all Safari skins. I know some people hate Apple for both good and bad reasons, but it's pretty wild to me people think Apple does this. I mean right out the gate that would be pretty illegal, no?

...what are you talking about?

Every browser you use is forced by App Store policy to run off of the system WebView, which is Safari...other features being part of the browser doesn't change being forced into using that engine.

Re: Apple's whitelist of the 250k auto-completable domains in iOS

#108
post #64

Earlier quoted context omitted.

You should "make of" it that Apple consider it a popular domain people try and navigate to

You think apple are above censorship at the behest of politicians?

Considering most of us didn't know about this list either, there simply wasn't anyone to ask for the censorship.

Re: Apple's whitelist of the 250k auto-completable domains in iOS

#109
post #103

Earlier quoted context omitted.

Good idea! I’ve created an issue[0] that can be subscribed to, I will implement the feature soon. [0]: https://github.com/b0o/apple-autofill-domains/issues/1

Random q: why fetch depth 20?

That’s actually a bug, thank you. It will break as soon as the last modification to the data file is more than 20 commits behind HEAD. I used 20 because it made the workflow function (it was working on my local machine but not when I pushed to GitHub because the default depth is 1). I need to update it to check for the last commit that modified the json file rather than searching through the entire commit history.
Post reply on HN