Unfortunately, Memestreams does an RFC-violating combination of the two. It responds to resources that require login with a 401, but without specifying the WWW-Authenticate header to tell the browser how to send the credentials back.

Noted.. "Oops." I'll fix it at some point.

RE: Memestreams and HTTP Authentication