Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

X0.at: upload files from cURL

x0.at

Post reply on HN
Print view View original

51–60 of 93 posts

Re: X0.at: upload files from cURL

#51

Post by dheera »

gowld wrote: post #50
dheera wrote: post #49

Earlier quoted context omitted.

I once had a location-based file sharing service that also got blacklisted by Google with no recourse. I hate Google trying to police the internet with no timely appeals process. I wonder though if you could simply just block the Google crawler and bypass it. Or use a JavaScript to auto-POST something before the file gets sent for download. The Google crawler doesn't issue POST requests as far as I know.

By "police", do you mean "warn people about dangers" ?

There wasn't any danger. Nothing more than Google Drive or Dropbox. And they didn't have any way to contact them and explain. Way to heavy-handedly shut down a potential business idea.

Re: X0.at: upload files from cURL

#52

Post by xyzzy_plugh »

dheera wrote: post #51
gowld wrote: post #50

Earlier quoted context omitted.

By "police", do you mean "warn people about dangers" ?

There wasn't any danger. Nothing more than Google Drive or Dropbox. And they didn't have any way to contact them and explain. Way to heavy-handedly shut down a potential business idea.

Drive and Dropbox are at least moderated.

Re: X0.at: upload files from cURL

#53

Post by s_dev »

detaro wrote: post #48
s_dev wrote: post #42

Earlier quoted context omitted.

>the repo does not have a license file, which makes me a little uneasy. Surely the author is bearing the liability of getting burned by not specifying a licence.

How do they "get burned" by that? Not having a license means you don't get to use it and are violating their copyright if you do so (possibly except the things specified in Github ToS: look at the code on github)

So not having a license means a default one was used? Which licence is that?

Re: X0.at: upload files from cURL

#54

Post by tobylane »

umvi wrote: post #2

These are always nice little sites to have around, but they can't really grow much in popularity before users start abusing them to distribute illegal things at which point the site has to start doing more and more content moderation or be shut down.

Agreed. I was using it* for TravisCI, and having moved to Github Actions I'm glad they have uploads stored per run.

*this one and another few before it.

Re: X0.at: upload files from cURL

#55

Post by unglaublich »

gowld wrote: post #50
dheera wrote: post #49

Earlier quoted context omitted.

I once had a location-based file sharing service that also got blacklisted by Google with no recourse. I hate Google trying to police the internet with no timely appeals process. I wonder though if you could simply just block the Google crawler and bypass it. Or use a JavaScript to auto-POST something before the file gets sent for download. The Google crawler doesn't issue POST requests as far as I know.

By "police", do you mean "warn people about dangers" ?

More like taking suspects into custody.

Re: X0.at: upload files from cURL

#56

Post by mhitza »

derefr wrote: post #32
southerntofu wrote: post #21

Earlier quoted context omitted.

> Uploading files without auth layer - is asking for trouble IMHO. If you make it super user-friendly and advertise it as the next Megaupload, sure. But if you keep a small audience of good-faith users it's not asking for problems. If you can teach me to make my file upload as hacker-friendly as this service while implementing auth, i'd be glad. Here the entire point is you don't need further configuration/credential…

This is incompatible with using curl as your client, but one “hacker-friendly way to do auth” is to use Github’s public SSH keys API. You can stand up an (SCP/SFTP-subprotocol-only) SSH server, and tell the user to log in with their GitHub username + GitHub SSH key. Then configure your SSH server to call[1] a check on GitHub’s API to map the provided username to the GitHub user’s set of public SSH keys. From there, t…

That's a neat idea, but I would try to simplify it a bit. Now, the details are fuzzy as I haven't set up anything like this but I know the theory behind it.

You could setup a website which accepts file uploads at username:file_signature@example.com , when a request is accepted you retrieve the public ssh key for "username" and validate that the "file_signature" is valid for the file uploaded.

It's a bit unintuitive to sign files with your SSH key but possible https://superuser.com/a/1616656/51984

Re: X0.at: upload files from cURL

#57

Post by rogual »

apayan wrote: post #43

If you like the convenience of transferring a file temporarily into the cloud to download it elsewhere (great for getting stuff out of a rancher environment), check out patchbay[0]. It uses what it calls 'HTTP channels' so if you start a POST request to a patchbay URL, it will block until a corresponding GET is made to the same endpoint which will receive the data from your POST. The operation can be done in reverse…

This is brilliant, thank you!

Re: X0.at: upload files from cURL

#58

Post by planetafro »

xyzzy_plugh wrote: post #52
dheera wrote: post #51

Earlier quoted context omitted.

There wasn't any danger. Nothing more than Google Drive or Dropbox. And they didn't have any way to contact them and explain. Way to heavy-handedly shut down a potential business idea.

Drive and Dropbox are at least moderated.

Source? ...moderated via automation or human?

Re: X0.at: upload files from cURL

#60

Post by pokoleo »

southerntofu wrote: post #21
the_arun wrote: post #14

Uploading files without auth layer - is asking for trouble IMHO. Change without audit trail will encourage wrong doers. But I get the idea, this is an example for a file upload in a simple way using Curl or other tools.

> Uploading files without auth layer - is asking for trouble IMHO. If you make it super user-friendly and advertise it as the next Megaupload, sure. But if you keep a small audience of good-faith users it's not asking for problems. If you can teach me to make my file upload as hacker-friendly as this service while implementing auth, i'd be glad. Here the entire point is you don't need further configuration/credential…

Try using basic auth:

curl -u username:password https://

Post reply on HN