Without TLS, absolutely anyone along the link (not just curl.io) can inject some BS into your command line if you choose to copy-paste.

If you don't trust curl.io, fine. But without TLS the list of people you need to trust is not only curl.io, but everyone else in the tubes too.

Hey, I'm not sure that the SSL certificate will change something in the trust of the website, because the file will be hold by the website anyway. So according to me, I think you have to encrypt your file before sending it to the server, that you'll be sure to be the only one who can read your file (and other people who you give your passphrase).

I've updated the website with gpg encryption w/ passphrase FYI.

While active attacks are still possible, TLS prevents passive attacks (eg: eavesdropping).

you're right but it should increase the level of trust along the way, no? or do I not undestand SSL correctly?