If you have issues with google hiding the www-prefix - can you give a reasonable explanation what it means that some webpages start with www. and others don't? (an explanation that makes sense for a user, not one of technicalities in the implementation)
-
Show this thread
-
the honest answer is: having a www prefix or not has little practical meaning from the user's side, it's a convention that some people like and others dislike. hiding it removes a source of confusion.
6 replies 1 retweet 16 likesShow this thread -
Replying to @hanno
Do you know how they decide whether or not to hide or add it? Flaws in this heuristic would be what's relevant to users - when, if ever, does it break things?
2 replies 0 retweets 0 likes -
Replying to @RichFelker
I don't know, but I've read it causes some weirdnesses (e.g. removing www not as the leftmost label). I think these are mere bugs and yeah, it probably would make sense to have the exact behavior properly defined.
1 reply 0 retweets 1 like -
Replying to @hanno
Somehow it seems to avoid dropping the www on sites where the non-www doesn't work, and to add the www on sites that need it if you omit protocol, but not if you include protocol.
1 reply 0 retweets 0 likes
I'm not sure what happens on sites where both www and non-www exist and are different.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.