proxy.js.org

[NanduWasTaken]

• There is reasonable content on the page (see: No Content)
• I have read and accepted the Terms and Conditions
• The site content can be seen at https://proxy-r2c4.onrender.com (might take a second to load)

The site content is a CORS-free json PROXY api with zero hassle. Source Code At https://github.com/NanduWasTaken/Proxy

[MattIPv4]

Given that this is an open proxy, I do not believe this can be compliant with section 4 of the Terms and Conditions for JS.org. @indus thoughts?

[NanduWasTaken]

🔍 Compliance with JS.ORG §4 – Rights and Duties of the User

Here's an overview of how my project aligns with the JS.ORG terms, specifically Section §4.

❓ Prohibited Content / Risk	✅ Am I Doing This?	💬 Notes
Piracy (warez, MP3s, software, etc.)	❌ No	I host no files/media, only JSON API proxy.
Phishing, scams, malware, or viruses	❌ No	No harmful or deceptive content involved.
Copyright offense	❌ No	No copyrighted content is being proxied or served.
Dubious business models (e.g., pyramid schemes)	❌ No	Not monetized; completely free and open-source.
Unlawful, obscene, threatening, abusive, or libelous	❌ No	Purpose is strictly developer tooling.
Content that promotes or enables criminal activity	❌ No	Project is technical and legal in intent.
Pornographic or adult-only material	❌ No	Not applicable at all.
Unsecured Web 2.0 platforms (e.g., forums without captcha)	⚠️ Borderline	It's a generic proxy — adding rate limits and blacklist to prevent abuse.
File or image hosting	❌ No	No storage or hosting — real-time HTTP forwarding only.
Other illegal or harmful content	❌ No	Proactively keeping usage safe and clean.

✅ Steps I would take to remain compliant:

• Adding rate limiting to prevent abuse.
• Implementing a domain blacklist to restrict proxy access to problamatic APIs.
• Adding a clear disclaimer on the homepage about intended usage (not for malicious purpose).
  (These changes will roll out shortly after hearing your feedback)
  Is there any more actions needed from me to remain compliant to the §4?

[indus]

I don't feel comfortable allowing an open proxy without any control or influence: ❌ No

But there are a variety of similar services that may fit better.

[NanduWasTaken]

I don't feel comfortable allowing an open proxy without any control or influence: ❌ No

But there are a variety of similar services that may fit better.

"without any control or influence"
What do you mean by that anyway???? I already addressed the potential issue that come with it and how I can deal with it to comply with your TOS, The Abuse of this service is pretty much near zero with those restrictions, I don't get why you quote it "without any control or influence", Security measures is being implemented(not released becuz I wanted feedback)... What is the real reason here??

[indus]

What I mean is that I (!) have no insight nor control over what your proxy proxies. If there is a high percentage of stuff unrelated to JS or content that is against the ToS  and you are fine with it I may not even notice.I think I'm free to decide what to accept and what I reject when I have the feeling it may cause trouble. Why don't you just buy a domain and do whatever you want with it.

[NanduWasTaken]

I understand your concern and respect your discretion....

That said, respectfully, I don't think it's fair to assume full responsibility or preemptively reject a project based on what might happen. JS.ORG is meant to support JS-related projects, and I’d argue that a proxy to help developers overcome CORS issues absolutely fits within that mission. You’re not expected to control or police every JS project using your domains—no one can.

Furthermore, Let's be real, no one can have insight on what's happening on every single project here and any project only have to go through checkup when registering for the js.org subdomain, after that anyone can change it into a online drug cyndicate on FBI no. 1 wanted list without you guys knowing.

"If there is a high percentage of stuff unrelated to JS or content that is against the ToS and you are fine with it I may not even notice" -- Mate this is just an proxy taking in and spiting out json... wdym by content not related to JS, it doesn't hold onto any content.

For your credit, Yes my proxy fetches html of pornhub when url query is given through a browser, but I am working on it 🤝🙏

This project is transparent, documented, and built for the dev community, not abuse. I’m more than happy to make changes or improvements if needed, but a blanket rejection feels counter to the spirit of open development.

Either way, I appreciate the time and effort you put into brutally rejecting me, and I’ll explore alternatives if necessary.

Cheers Nandu 🥂

[MattIPv4]

You’re not expected to control or police every JS project using your domains—no one can.

That's exactly why we have the pull request process and ask for information about what the project is -- we do actively filter what requests we accept to make sure we believe they're related to the JS ecosystem/community, and don't pose a threat to the reputation of the JS.org domain as a whole.

Let's be real, no one can have insight on what's happening on every single project here and any project only have to go through checkup when registering for the js.org subdomain, after that anyone can change it into a online drug cyndicate on FBI no. 1 wanted list without you guys knowing.

We keep an eye on the traffic going to subdomains pretty regularly and do take action if we notice content that we didn't approve (see for example #9735). We also do annual (ish) cleanups where we verify that every single subdomain for JS.org has legitimate content on it still.

So, please don't tell us how we run our own project 👍

[NanduWasTaken]

🙏 I never told you how to run your project, I am just pointing out my frustration

I get that you're trying to maintain the integrity of the JS.ORG ecosystem, and I respect that. I was just frustrated because it felt like the rejection wasn’t really about the actual content or intent of the project, but more a blanket “what if” scenario.

Me: Hey this is my proxy.
Maintainers: That's a problem, it's a open proxy... We don't have any insight
Me: I can make restrictions and blacklist to prevent abuse so it is clean
Maintainers: Screw You. closes the pr
(Now we are arguing lmao)

I understand this is your project and your call at the end of the day. I wasn’t trying to tell you how to run things — just expressing the frustration of being shut down without any chance to prove the project’s value or adjust it to meet expectations.

Anyway, I’m not trying to start a war with u guys — Appreciate the response regardless.
Thanks For Replying Even Through it's for arguing 😭 it's a lot better than getting ignored🙏

Cheers 🥂
Nandu