server render the metadata

[okdistribute]

cc @laurengarcia

[laurengarcia]

looks fine, but if user (developer) has the electron-webrtc module installed, Haus is going to use that still, isn't it? lets either nuke it or parameterize it <-- i don't care either way, but the way it is now it is very ambiguous.

[okdistribute]

I took out the electron-wrtc part in a separate commit. It needs more thought in haus.js and probably should use hybrid-swarm or a variation that can handle multiple keys, if we are going to use wrtc in the backend.

[laurengarcia]

ok im cool with this then.

[okdistribute]

@laurengarcia okay merged, wondering how it's coming on the archive api with those two methods that will abstract out the stream transport type?