Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GoTiny is shutting down #11

Open
robvanbakel opened this issue Nov 3, 2023 · 8 comments
Open

GoTiny is shutting down #11

robvanbakel opened this issue Nov 3, 2023 · 8 comments

Comments

@robvanbakel
Copy link
Owner

Unfortunately, GoTiny is shutting down due to an increasing number of phishing and scamming attempts. Despite my efforts to prevent illegal activities from happening via GoTiny, the situation has become unmanageable and is forcing me to stop making the API publicly available.

@robvanbakel robvanbakel pinned this issue Nov 3, 2023
Repository owner locked and limited conversation to collaborators Nov 3, 2023
Repository owner unlocked this conversation Nov 3, 2023
@jessiejs
Copy link
Contributor

jessiejs commented Nov 4, 2023

Will existing GoTiny links still work?

@jhorner6511
Copy link

Well this sucks balls.

@robvanbakel
Copy link
Owner Author

Will existing GoTiny links still work?

@jessiejs Previously shortened links will open a page displaying the URL it would have originally been redirected to. This way, no existing data is lost and users can still manually navigate to their destination.

@ghost
Copy link

ghost commented Nov 16, 2023

I believe that using a load limiter could help (1 request per second). I recommend search about the "express-rate-limit" and "express-slow-down" libraries. Redis as a form of storage would be great, there are several free options, like:

https://render.com/
https://upstash.com/

@ghost
Copy link

ghost commented Nov 16, 2023

Unfortunately, GoTiny is shutting down due to an increasing number of phishing and scamming attempts. Despite my efforts to prevent illegal activities from happening via GoTiny, the situation has become unmanageable and is forcing me to stop making the API publicly available.

Blocking malicious domains would not be a good idea? Before registering a resource, check if the domain exists in a table (black list) in DB or hard coded?

@jhorner6511
Copy link

jhorner6511 commented Dec 3, 2023

There's actually no need for you to shut down the website. You just have to add a no liability clause in your terms of service. Just think of how many dingdongs use Bitly, and yet, they keep chugging along. Why? Because of their zero liability clause. Even better if you have a no logs policy. You cannot be held criminally liable for something you have no knowledge of. It's unfortunate but there's scammers everywhere on every website on the planet. People use Google all the time to scam other people. But have you ever seen Google sitting in front of Congress due to their users engaging in criminal activity while using their services? Nope.

Just had a zero liability clause on your website and fire that bad boy up again.

@MagicGamerRMG
Copy link

rip GoTiny :/

@Nusab19
Copy link

Nusab19 commented Dec 15, 2024

As @jhorner6511 has suggested, you can just add a "No Liability" to this service. And then add a rate limit, this way, you probably don't need to shut this service down.

Another thing I have noticed is that, you are creating new short links for every long url. ( even if the link was shortened previously )
So, you can check if a shortened version of the url already exists in the database.

But if you say that "storing the links in the database" can possibly make you liable, I have a workaround for that too. I'd love to help you throughout this process.

You made a great tool and you should not HAVE to shut it down. ❤

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants