Netcat / easier command line pasting about paste

[lucko]

This is a nice idea, thanks!

Functionality to support this has been added in:

• lucko/paste-netcat@8f7bce0
• lucko/bytebin@5150d0f

You can now upload as below:

# Pipe in some output from any command
> echo "Hello world" | nc nc.pastes.dev 1337

# Upload the contents of a file
> cat example123.txt | nc nc.pastes.dev 1337

Bit of a childish port number but I thought it'd be easier to remember 😛

See https://github.com/lucko/paste-netcat/ for more info on the implementation. I thought it was better to have a separate service that handles the netcat connections and proxies them to the normal HTTP storage API (bytebin). You could even standup your own instance of paste-netcat (e.g. inside a firewall) but still proxy out to the pastes.dev service.

In theory it supports the same content size limits as bytebin - currently configured to a max of 10mb post-gzip. The paste-netcat server handles compression before forwarding the request on. All of which means it should be able to handle reasonably large plaintext files with no issue.

I've also updated the readme with this info :)

Thanks again!

[clrxbl]

Hm, nc.pastes.dev doesn't seem to be working for me?

/tmp/server via ☕ v17.0.1
❯ cat paper.yml | nc nc.pastes.dev 1337

/tmp/server via ☕ v17.0.1 took 30s
❯

[lucko]

Ah! I was testing with netcat on macOS, which has some subtle differences compared with other versions (e.g. on Linux machines)

Should be fixed by lucko/paste-netcat@8673ada :)

Let me know if that works

[clrxbl]

Works! Another suggestion would be to add the ability to specify a language for syntax highlighting until there's some auto detection.

e.g. netcat to nc.pastes.dev/yaml for YAML

[lucko]

Sweet!

Unfortunately netcat only works with hostnames & ports, not URLs - that's a HTTP thing.

Only options are:

1. more subdomains (bit of a pain)
2. more ports (hard to remember)
3. some sort of header in the submitted content - but at that point you're better off using curl

echo "test: 123" | curl -d @- -H 'Content-Type: text/yaml' https://api.pastes.dev/post

Auto-detection is also a bit tricky, but I'll elaborate more on that another time, on the other issue.

[clrxbl]

Sweet!

Unfortunately netcat only works with hostnames & ports, not URLs - that's a HTTP thing.

Only options are:

1. more subdomains (bit of a pain)
2. more ports (hard to remember)
3. some sort of header in the submitted content - but at that point you're better off using curl

echo "test: 123" | curl -d @- -H 'Content-Type: text/yaml' https://api.pastes.dev/post

Auto-detection is also a bit tricky, but I'll elaborate more on that another time, on the other issue.

Subdomains seem somewhat doable? Because you can have wildcard subdomains & SSL records which would make the hosting part fairly simple.
Something like yaml.nc.pastes.dev could work.

[lucko]

The server doesn't know which subdomain the request was made from.

This is only possible for HTTP servers because of the Host header - whereas netcat does the DNS resolution on the client side and then opens a direct TCP connection.

[clrxbl]

The server doesn't know which subdomain the request was made from.

This is only possible for HTTP servers because of the Host header - whereas netcat does the DNS resolution on the client side and then opens a direct TCP connection.

Ahhhhh, okay. Makes sense.