400: Malicious Attacks

[moore-bryan]

I've used this for quite some time, fully understanding it could go away at any moment, and now that it has I miss it dearly; any chance this is going to get back up and running?

Error message on site:

400
URL shortening temporarily disabled due to malicious attacks. Contact in case of any questions/issues

[amitt001]

Hi @moore-bryan, thanks for reaching out.

To give more context for disabling the new URL shortening, I had to do it due to the multi-faced attack on the website. Malicious links and large scale DDoS attack were the major issues. Since I'm the sole maintainer of the project. I tried to manage for some time but it became too difficult to manage it with my limited resources and a day job.

I don't have anything planned to bring the URL shortening back at this moment but soon I may look into finding a solution.

For now, I can suggest some alternatives. You can either try https://tinyurl.com/ or if you are up for a challenge you can run your own URL shorter using pygmy code 😉

[moore-bryan]

Thanks for the follow-up Amit... Although sad, I completely understand not having time to maintain what, essentially, can be a hobby. One of the main reason I loved your tool was, AFAIK, tinyurl isn't open souce. I didn't check yet; do you have a wiki on how to deploy it on one's own? Thanks, again, for the reply and all the work you put into this great tool! -----Original Message-----From: Amit Tripathi <notifications@github.com

Reply-To: amitt001/pygmy <

reply@reply.github.com>To: amitt001/pygmy <pygmy@noreply.github.com>Cc: Bryan Moore < moore.bryan@gmail.com>, Mention <mention@noreply.github.com>Subject: Re: [amitt001/pygmy] 400: Malicious Attacks (#48)Date: Sat, 11 Jul 2020 13:44:38 -0700 Hi @moore-bryan, thanks for reaching out. To give more context for disabling the new URL shortening, I had to do it due to the multi-faced attack on the website. Malicious links and large scale DDoS attack were the major issues. Since I'm the sole maintainer of the project. I tried to manage for some time but it became too difficult to manage it with my limited resources and a day job. I don't have anything planned to bring the URL shortening back at this moment but soon I may look into finding a solution. For now, I can suggest some alternatives. You can either try https://tinyurl.com/ or if you are up for a challenge you can run your own URL shorter using pygmy code 😉 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[amitt001]

Thanks @moore-bryan for encouraging words. I appreciate it :)

The project's README mentions step to build the project and run it. It has both manual step as well as docker step.
The setup that's running pygy.co website is

1. nginx webserver
2. postgresql database running in docker with fixed volume
3. docker-compose
4. Gunicorn web-server in docker for both ui template engine and backend

If there is interest I can write a blog detailing pygy.co setup.

[moore-bryan]

I just did the Docker setup today and it seemed to work flawlessly; time to learn Docker. ;-) You're very welcome... you put in some hard work and generated some great code; I hope it all works out! -----Original Message-----From: Amit Tripathi <notifications@github.com

Reply-To: amitt001/pygmy <

reply@reply.github.com>To: amitt001/pygmy <pygmy@noreply.github.com>Cc: Bryan Moore < moore.bryan@gmail.com>, Mention <mention@noreply.github.com>Subject: Re: [amitt001/pygmy] 400: Malicious Attacks (#48)Date: Mon, 13 Jul 2020 13:18:16 -0700 Thanks @moore-bryan for encouraging words. I appreciate it :) The project's README mentions step to build the project and run it. It has both manual step as well as docker step. The setup that's running pygy.co website is 1. nginx webserver 2. postgresql database running in docker with fixed volume 3. docker-compose 4. Gunicorn web-server in docker for both ui template engine and backend If there is interest I can write a blog detailing pygy.co setup. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.