[DOES NOT WORK] Vain attempts at getting noscript streaming to work

[TheTechRobo]

This PR contains my broken and not-quite-finished support for noscript streaming.

It's so fucking lame what I got stuck on: the link to the archived version cannot be added using the CSS content property.

I'm keeping this PR open with the glimmer of hope that maybe I or someone else will think of something - or maybe position: running will finally have proper browser support (I think it would be a solution to this problem, but it looks like it may only be available to page margin boxes).

Would partially f​i​x #66

[TheTechRobo]

There are two options I can think of from here, unless something radically amazing comes up (a way to change an <a> or add one where it should be):

1. Send the loading messages in a div with a unique ID, then set display:none and generate another once there is new information (VERY inefficient client-side as despite not being rendered the previous divs would still be part of the DOM)
2. Make a long-lived request for an iframe for each of the service responses that will eventually resolve to an <a> (Inefficient server-side with memory usage as the requests will last so long; leads to potential memory issues, performance issues (so many coroutines), and browser timeouts)

Both of the available options seem subpar to me.