This is a great idea. My two cents:

1. An accounts system would be great so that I could just run ``python experiment.py | seashells u=almostarockstar p=hunter2`` or similar with keys, and then have a bookmark on my phone to view seashells.io/u/almostarockstar.

2. A self hosted / open source option would be awesome.

3. A way to view other peoples public seashells urls would make this interesting.

4. Possible options to allow html output which could be paired with a css file attached to your account.

Can't wait to set this up with my own experiments (evolutionary computation).

Maybe use Flask and do cert based auth? A username and password is pretty clunky, and a bit of a pain IMO for sub-10 user projects.

An accounts system is coming in the next version. The public seashells URLs / HTML/CSS output ideas sounds neat, I'll add them to the potential features list!

I'm not sure if the code is going to be open-sourced, but I'm adding TLS and also client-side encryption in the next version.

The HTML idea is neat, but something to bear in mind unless you host this content on a separate domain/subdomain (think githubusercontent.com vs github.com) any Javascript embedded in that HTML will be able to read/write cookies, make XMLHttpRequests, etc against the seashells.io domain. Which could in turn cause some fairly serious security issues with any accounts system you plan on adding.

But seeing as view urls are quite shortlived by the sound of it, you shouldn't have too much of a problem moving their location from seashells.io/v/{url} to something like v.seashells.io/{url} if you do end up introducing some kind of HTML mode.

You should never provide passwords on the command line, since command lines can be shown/stored in any number of places (examples: shell history, process listings).

A slack style webhook token would be secure and clean looking.

Super useful to keep checking the compile status when going out dancing :)

Any plans to open source the server?

+1 to this. I'm not sure I'd want to use this externally, but it would be rad to use this for some internal services on my home network.

i don't see how this does anything i can't just do using initD, which routes the pipes to sockets automatically.

What's the actual benefit of using this, compared to just using init and taking care of that little html myself?

I've been linux for about 10 years and I would have no idea to do what you just said. The benefit is obviously that it is extremely straightforward to use.

Fantastic job!