Re:Rethinking J-school
by logn on Saturday April 27, 2013 @11:44PM
(#5620113)
There have been a lot of medium.com links lately. On Firefox version 20 on Mac, the text always takes forever to load. This doesn't happen in other browsers and in Firefox it's the only site I ever notice this with.
[ Parent
| on HN ]
Wouldn't be surprised if some developers laughed at us for using Firefox. Especially companies like Twitter/Medium.
Not at all, we just hadn't noticed any problems. We use typekit so I can't think why it'd be an issue, but rest assured we'll look into it.
Why would you think that?
Re:Rethinking J-school
by AdamTReineke on Sunday April 28, 2013 @02:29AM
(#5620399)
Chrome is the browser of choice these days. [Posted from IE10.]
I run noscript in Firefox for casual browsing and reading. I don't do it out of paranoia. I do it because most sites load much faster. The number of external scripts loaded on media sites is usually the bottleneck, with 20+ not uncommon.
We (Medium) use async snippets for the few external scripts we load (KISS and GA) and our JS is deferred to the end of the document. Stylesheets and typekit fonts will block, though, unfortunately.
This'll probably be the only chance I get, so I have to ask...
Why do all links on medium point inwards?
Arguments made by those who don't know better are:
1. To track clicks on outbound links
2. To preserve "pagerank" or some such think.
Neither of these are strong arguments since you can track outbound clicks with G.Analytics or any other analytics service worth using, and outbound links have about zero impact on pagerank of the linking page.
What reason could possibly be so great that you choose to break the web for it?
It was added to block referrers on unpublished drafts. We have been meaning to take it out for published posts, but for a couple of reasons it's not as trivial as flipping a flag.
"break the web" is a little melodramatic though.
Thanks for the explanation. I don't think its melodramatic at all. Links are the foundation of the www.
Thanks for the report, we hadn't noticed any problems. Will look into it.
Thanks. My comment got some upvotes so I figure others are having the same problem. It loads perfectly in Chrome and Safari though. You might share your results with the Mozilla community if you figure it out.