Training people to think confusing URLs are OK seems like a bad idea?
-
-
Replying to @tnare @lorenzofb
Researching ways to convey the information contained in URLs in a understandable way seems like a good idea to me. Training people to even look at the address bar doesn't seem to be working.
1 reply 0 retweets 0 likes -
Replying to @taviso @lorenzofb
I don't disagree with researching ways to better convey the information contained within a URL. Having humans decode what are effectively RPC invocations is a losing battle. Before we get there though, let's give the people that DO check the URL a fighting chance?
1 reply 0 retweets 1 like -
Replying to @tnare @lorenzofb
What feature of URLs are you proposing deprecating to solve the problem? Remember, attackers will continue using them anyway.
1 reply 0 retweets 0 likes -
Replying to @taviso @lorenzofb
I am not recommending deprecating any features. I am recommending exposing the information contained in a URL in some undetermined user-friendly way. 1/2
1 reply 0 retweets 0 likes -
This is orthogonal to my point that in the meantime we should make URLs behave the way users expect. If I'm on a website claiming to be http://qz.com yet is showing http://google.com in the bar), I will become desensitized to that mismatch. 2/2
1 reply 0 retweets 0 likes -
Replying to @tnare @lorenzofb
So the feature you want to deprecate is hosting safe user generated content? That's going to be a tough sell, it's a big part of the modern Internet.
1 reply 0 retweets 0 likes -
Replying to @taviso @lorenzofb
Maybe this is where the fundamental rub is. A URL is exposing who am I getting the content from, not who produced said content. Those two things used to largely match, but that relationship has broken down.
1 reply 0 retweets 0 likes -
So now I can get http://qz.com content, served from http://google.com . But because with AMP the relationship between content-origin and URL has broken down, you no longer have any idea where the content came from.
1 reply 0 retweets 0 likes -
Replying to @tnare @lorenzofb
How is that any different from https://twitter[.]com/qz/status/1039566323964174336 - The content is served by twitter, so https://twitter.com is displayed in the address bar. The content was written by and is branded "QZ". It's third party content hosted by twitter, right?
3 replies 0 retweets 0 likes
If you argue everyone should stop hosting third party content on their domain because users get desensitized to author/host mismatches, etc, I think that is a radical position with zero evidence to support it.
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.