nwtgck / piping-server

Infinitely transfer between every device over pure HTTP with pipes or browsers
MIT License
2.93k stars 153 forks source link

Self hosted piping with ui #445

Open farfromrefug opened 3 years ago

farfromrefug commented 3 years ago

I am very interested by your project. Especially thinking about using it to transfer files between my local network devices. Is there a docker or something for the server + piping ui ? Thanks

nwtgck commented 3 years ago

Thanks.

Actually, I had also the same idea. But I don't do that because of a security reason.

Suppose https://ppng.io/ has a richer UI like Piping UI. Piping Server is designed for integrating HTTP seamlessly. For example, you can see https://ppng.io/myimage.png transferred image data. Suppose you open https://ppng.io/myweb.html and a web browser can interpret as HTML and run a script in the HTML. Although Piping Server has a feature for not interpreting and not sniffing a text as HTML for browser, I should not make the simple Web UI on Piping Server richer.

So, Piping Server and Piping UI should have different domains. Let me know If you have some idea to solve the security problem.

farfromrefug commented 3 years ago

I understand (i think the issue). Although from a user point of view this is not an issue. When used on a local network to simply share files, you dont care as the network is not opened to the outside. Another solution would be to automatically use a password and store it client side as a cookie or something. That way you dont always have to enter it.

Just for why i am really interested by your project. Right now i use snapdrop to share files. But it uses webrtc which makes it not work with privacy enhanced browsers like bromite or chromium ungoogled. Yours should work anywhere

nwtgck commented 1 year ago

Recently I'm interested in Caddy 2 because it may allow us to do what you want.