Advertise here: Contact FM.
var noscriptoff=true;
<script src="http://mefi.us/checkfornoscript.js"></script>
<script>
if (typeof noscriptoff=='undefined' || !noscriptoff) {
var n=document.createElement('div');
n.appendChild(document.createTextNode('Looks like you might have mefi.us blocked using NoScript. mefi.us is a new domain for serving scripts on MetaFilter. Please allow it to get full functionality.');
document.getElementById('ajaxcontentarea').insertBefore(n,document.getElementById('ajaxcontentarea').firstChild);
}
</script>images.metafilter.com, scripts.metafilter.com, and styles.metafilter.com. Chances are good that *.metafilter.com was enabled in NoScript so you didn't need to know about these domains. The issue was that every request for an image, script, or stylesheet carried the burden of all *.metafilter.com cookies. By switching to a new domain, the requests are cookie-free and milliseconds faster.Browser: Hi www.metafilter.com, can I have the root page.... and so on. Notice with every request from your browser to www.metafilter.com, all the cookies you have associated with metafilter.com are sent along with your request. And they're not needed by the server just to retrieve an image or a script that never changes.
www.metafilter.com server: Sure, here's your page, and here are a bunch of cookies for metafilter.com for you to remember.
Browser: (Notices there are images on the page that are on www.metafilter.com). Hi www.metafilter.com, can I have the first image please? And here's a copy of all the cookies you sent me for metafilter.com.
www.metafilter.com server: Here's image #1.
Browser: Hi www.metafilter.com, can I have the second image please? And here's a copy of all the cookies you sent me for metafilter.com.
www.metafilter.com server: Here's image #2.
Browser: Hi www.metafilter.com, can I have the root page.In the glorious new way of doing things, your browser isn't wasting time and bandwidth sending a copy of all the metafilter.com cookies to the server when it's just going to ignore them anyway. Stuff that does still need these cookies will still come from www.metafilter.com, so it'll get them.
www.metafilter.com server: Sure, here's your page, and here are a bunch of cookies for metafilter.com for you to remember.
Browser: (Notices there are images on the page, that are on mefi.us). Hi mefi.us, can I have the first image please? [Note lack of cookies for metafilter.com here, because this request goes to mefi.us instead]
mefi.us server: Here's image #1.
Browser: Hi mefi.us, can I have the second image please?
mefi.us server: Here's image #2.
I've been running the plain white theme so long now that it took me a minute to remember that mefi has colored pages.
By the way, here are the things that won't work if you have mefi.us blocked: ...
- b/i/link HTML buttons for posting/commenting
googleapis.com and metafilter.com but block mefi.us. You should still be able to favorite things. The favorites code makes Ajax calls and has to be hosted at whichever domain you're on due to JavaScript's Same origin policy.googleapis.com and metafilter.com but block mefi.us. You should still be able to favorite things."
posted by Confess, Fletch at 9:54 AM on June 12