Earlier quoted context omitted.
This is what my dig shows `transfer.sh. 2 IN A 0.0.0.0`
Probably your DNS blocking it then
X0.at: upload files from cURL
41–50 of 93 posts
Re: X0.at: upload files from cURL
#42I like the simplicity of it. One PHP file, throw it on a server with Apache and rock and roll. Other comments are right to point out that this site is setting itself up to be abused. My feeling is that this is intended to be a demo. I doubt the creator is trying to provide a real service here. And they might be in for a rude awakening if it gains traction. But, it looks like they intend this to be open source. Anyone…
Surely the author is bearing the liability of getting burned by not specifying a licence.
Re: X0.at: upload files from cURL
#43Re: X0.at: upload files from cURL
#44Re: X0.at: upload files from cURL
#45I like the simplicity of it. One PHP file, throw it on a server with Apache and rock and roll. Other comments are right to point out that this site is setting itself up to be abused. My feeling is that this is intended to be a demo. I doubt the creator is trying to provide a real service here. And they might be in for a rude awakening if it gains traction. But, it looks like they intend this to be open source. Anyone…
>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.
Re: X0.at: upload files from cURL
#46I like the simplicity of it. One PHP file, throw it on a server with Apache and rock and roll. Other comments are right to point out that this site is setting itself up to be abused. My feeling is that this is intended to be a demo. I doubt the creator is trying to provide a real service here. And they might be in for a rude awakening if it gains traction. But, it looks like they intend this to be open source. Anyone…
>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.
Re: X0.at: upload files from cURL
#47I like the simplicity of it. One PHP file, throw it on a server with Apache and rock and roll. Other comments are right to point out that this site is setting itself up to be abused. My feeling is that this is intended to be a demo. I doubt the creator is trying to provide a real service here. And they might be in for a rude awakening if it gains traction. But, it looks like they intend this to be open source. Anyone…
>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.
Re: X0.at: upload files from cURL
#48I like the simplicity of it. One PHP file, throw it on a server with Apache and rock and roll. Other comments are right to point out that this site is setting itself up to be abused. My feeling is that this is intended to be a demo. I doubt the creator is trying to provide a real service here. And they might be in for a rude awakening if it gains traction. But, it looks like they intend this to be open source. Anyone…
>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.
Re: X0.at: upload files from cURL
#49Yeah this is asking for trouble. We only had a small demo on our homepage where users could upload media files and they were deleted after 24 hours and still some people managed to abuse it and nearly got our site killed, domain blacklisted in Google with a big red screen of death. I don't want to spam any links here but if you are interested please do look at my last post about the dangers of doing this and lessons…
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.
Re: X0.at: upload files from cURL
#50Yeah this is asking for trouble. We only had a small demo on our homepage where users could upload media files and they were deleted after 24 hours and still some people managed to abuse it and nearly got our site killed, domain blacklisted in Google with a big red screen of death. I don't want to spam any links here but if you are interested please do look at my last post about the dangers of doing this and lessons…
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.