48 points by EvanZhouDev 8 days ago | 17 comments on HN
| Mild positive Moderate agreement (3 models)
Product · v3.7· 2026-03-16 00:02:04 0
Summary Free Expression & Knowledge Access Champions
This GitHub repository for an open-source OpenAI OAuth project instantiates multiple UDHR rights through its structural design and content. The public code repository directly supports Article 19 (freedom of expression and information sharing), Article 20 (freedom of association through collaborative development), and Article 26 (education through free technical knowledge access). The platform infrastructure provides HTTPS encryption, accessibility compliance, and no third-party tracking, supporting Articles 3 and 12 (security and privacy). Overall, the content champions human rights through transparent, open-access knowledge sharing and inclusive collaborative development practices.
Rights Tensions1 pair
Art 12 ↔ Art 19 —Public repository prioritizes freedom of expression (Article 19) and information access over privacy (Article 12), requiring users to choose between participating in collaborative knowledge-sharing or maintaining data privacy.
I feel like this will have a short shelf life. OpenAI is going to notice traffic through that Codex endpoint that doesn't match its usage patterns and lock it down.
There were rumors about OpenAI preparing for sign in with OpenAI to let users use their OpenAI allowances with apps, si this is basically it. The question is, how long before OpenAI bans this or makes it official.
1- It's against the ToS obviously. The analogy I've used in the past that seemed to catch on is that it's like going to an all you can eat buffet, bringing your whole extended family and trying to pay once.
2- Legals and ethics aside, don't build products that competitively rely on this, the moment they patch it you will be out of business, it's like making a business out of blackhat SEO during the Google era. At least if you are going to do it, cash out quick, you are in the rug pull space.
Have some sense and taste, we are professionals here, if in your pesonal life you share your netflix account, bypass DRM, throw cigarrette butts on the floor, cut in line or use handicapped spot without being handicapped, that's one thing, we all do something marginally wrong every once in a while. But on a professional setting, these go from being normal personality traits to being red flags that will silently leave you marginalized from serious software.
I'm extrapolating here, but it's a pattern I see very often in other areas where it's even wronger. For example lots of people use unofficial APIs instead of using Meta APIs, they connect to WhatsApp unofficially (See OpenClaw crowd), instead of following the procedures in place to reduce spam (and let Meta monetize of course). Even worse is people that want to scrape Facebook, sure it's a pain, but most the API stringency comes from the Cambridge Analytica scandal, if you do this shit and you then complain about Meta you are being hypocritical, can't have it both ways.
I know we are in hacker news, but there's a lot of nuance. Running youtube-dl to download some cat videos isn't the same as hosting youtube-dl as an API and charging 5$/mo or building a business on top of it.
I believe that OpenAI has to a certain extent allowed such usage (see: OpenCode, OpenClaw which have OpenAI OAuth built-in). This just opens it up to other developers!
Sign in with OpenAI will be nice. That being said, I feel like it might be difficult/not open to use for casual devs. Hopefully OAI leaves this up, as they've allowed it for OpenCode. https://x.com/opencode/status/2009805930377167233
I find it hard to believe they'll make it official completely, as that's basically giving away free API credits. If they really wanted the benefits of having free API credits they would just do that directly (but I doubt they'd do that in their current situation).
This occurred in response to Anthropic cracking down on a similar loophole, which tbh made me take it as more of an opportunistic marketing opportunity rather than a generalizable position.
Not disagreeing with you (and based on your other comments you're probably aware of this info) - just adding context on why this is a pretty interesting gray area and I'm similarly curious whether OpenAI will explicitly allow, disallow, or maintain ambiguity towards it.
The repo does explicitly say to only use this for personal or experimental projects.
That being said, OpenCode is relying on this in a "professional" context without any issue so far. I am not saying that is proof this is _not_ against ToS, but it does show perhaps OAI is ok with such usage.
This is a way to let users use the Codex-app to Codex-model interface that the 20$ subscription uses so that other apps can use the OpenAI API without paying per token.
What you are describing is SSO with OpenAI as an identity provider
High A:free_expression P:information_access F:transparency
Editorial
+0.35
SETL
-0.14
Repository title and description ('Free OpenAI API access with your ChatGPT account') express developer's intention and provide informational content. Code itself constitutes expression of technical knowledge and methodology.
FW Ratio: 50%
Observable Facts
Repository title and description publicly visible without authentication.
Code repository structure enables public viewing and downloading of source code.
No geographic restrictions or censorship mechanisms observed.
Page metadata indicates public repository status.
Inferences
Public code repository directly instantiates Article 19 right to seek and impart information.
Absence of access controls or geo-blocking supports freedom to receive information globally.
Technical transparency through public code enables informed scrutiny and knowledge sharing.
DCP's tracking audit (no third-party trackers) suggests content freedom without surveillance interference.
Medium P:cultural_participation A:technical_culture
Editorial
+0.20
SETL
+0.10
Repository represents participation in open-source technical culture and knowledge commons. Code sharing constitutes cultural contribution to developer community.
FW Ratio: 50%
Observable Facts
Repository contributes to open-source software culture.
Public code sharing enables cultural participation in developer community.
DCP indicates accessibility features supporting participation for diverse users.
Inferences
Open-source contribution represents participation in technical culture without gatekeeping.
Public knowledge sharing supports cultural participation in global developer community.
Accessibility compliance enables participation regardless of ability status.
High A:free_expression P:information_access F:transparency
Structural
+0.40
Context Modifier
+0.05
SETL
-0.14
GitHub's public repository infrastructure enables unrestricted access to code and documentation, supporting freedom to share and receive information. Global accessibility without geographic barriers maximizes information distribution. Public nature supports observability and transparency.
Medium P:assembly_freedom A:community_collaboration
Structural
+0.20
Context Modifier
0.00
SETL
+0.11
GitHub's pull request and issue systems enable peaceful assembly of developers around shared technical goals. Open repository structure removes barriers to participation.
Medium P:cultural_participation A:technical_culture
Structural
+0.15
Context Modifier
0.00
SETL
+0.10
GitHub platform enables participation in open-source culture without barriers. Public repository enables sharing of technical knowledge as cultural artifact.
Medium P:privacy_protection C:privacy_implications
GitHub's platform provides privacy settings; repository is public by default, requiring explicit user choice for privacy. Security headers (HTTPS, HSTS, CSP) protect data in transit. DCP notes no third-party trackers detected.
Public code repository enables access to technical knowledge without payment barriers; GitHub's accessibility features support inclusive access per DCP.