🏗️ [PROPOSAL] ONEHACK GITHUB ORG — Save Our Scripts From Dying In Old Threads

[Guile]

[DISCUSSION] COMMUNITY GITHUB ORG — One Permanent Home For Every Script Ever Shared

Every banger script someone drops on OneHack dies within months. Link rots, thread gets buried, script stops working — and six months later another newbie asks for “the bot someone shared once.” We keep losing our own tools.

The fix: one shared GitHub org (free shared code folder, with edit history) the community owns. Scripts get parked, polished, patched, and kept alive together — instead of dying alone in a 2023 thread.

---

🪦 The script graveyard — what's broken right now

Reality	Why it sucks
Scripts buried in 400 Discourse replies	Search “netflix script” → 8000 unrelated posts
MEGA / Anonfiles / Pastebin links die	Gone within months, no backup
Same Python loop rewritten 50 times	Nobody can find the last guy’s version
Target site patches detection → script dies silently	Nobody updates it because it’s nobody’s job
OG member goes quiet → all their work vanishes with them	Tribal knowledge, zero memory
“Does this still work in 2026?” asked 9,000 times	Nobody knows because version history doesn’t exist

We have collective genius and zero collective memory. This proposal fixes that.

📦 What we'd actually build (the proposal in plain English)

A shared toolbox we all have keys to:

• One GitHub home for every community script
• Version history — every change logged. If new version breaks, roll back in one click
• Trusted contributors get edit access — proven members. Random PRs reviewed before merge
• One-click runnable — every script ships with README (what it does), requirements.txt (what to install), config.example (where to paste your settings)
• Live patches — site changes detection? Someone updates it. Everyone benefits the same day
• Private at first, public when stable — invite-only org while we sort the rough edges

Think Wikipedia, but for the community’s scripts. Or a shared garage where the tools never walk off.

🌱 What lives in the repo (real categories, not vibes)

This isn’t theory — here’s what would actually get parked there on day one:

• Cookie refreshers — Netflix, Spotify, Crunchyroll, Disney+ keep-alive scripts
• Account checkers — feed in a dump, get back which logins still work
• Auto-signup bots — for free-trial farming (NoteGPT, Poe, etc.)
• Course downloaders — Udemy, Coursera, Linkedin Learning scrapers
• AI API key rotators — switch between free tiers without manual fiddling
• SMS receiver automation — for phone-gated signups
• Browser fingerprint spoofers — for the trial loops
• Free-tier max-out scripts — Google Cloud, AWS, Azure $300 trial wringers
• Account farmers — Reddit karma bots, GitHub Student Pack auto-applicants
• VPS deployment scripts — one command, full setup, ready to run
• GroupBuy coordinators — track members, payments, delivery status
• CAPTCHA solver integrations — drop into any existing script

Half of these already exist in scattered threads. We just collect them in one place.

🪪 Who runs it & how someone earns the keys

The starting crew (5–10 maintainers):

• Picked by existing OG members (regular posters with track records)
• Handle the first batch of submissions
• Set the code review standard

How a new member earns commit access:

1. Start as contributor — submit a PR (pull request — proposed code change) to fix or add something
2. 3 quality PRs merged → upgraded to trusted contributor (can review others’ PRs)
3. 10 quality PRs + 6 months active → maintainer (can merge to main)

Bad code can’t slip in. Two-reviewer minimum for anything that touches main.

Boot conditions: Spam, malware, doxing, intentionally broken commits = removed by maintainer vote.

💸 The money question (be real about costs)

GitHub org itself is free. So is everything in Phase 1.

If we ever scale to running shared scripts 24/7 on a community server:

Provider	Cost	What you get
Hetzner CX11	~€4.51/mo	2 vCPU, 4 GB RAM, 40 GB SSD — solid baseline
Contabo VPS S	~$5.50/mo	4 vCPU, 8 GB RAM, 50 GB NVMe — more horsepower
Oracle Cloud Free	$0/mo	Always-free ARM VM, 4 vCPU, 24 GB RAM — yes really
Google Cloud trial	$300 free for 90 days	New email = new trial

Strategy: Start on Oracle Free Tier (literally costs nothing). If we outgrow it, ~20 members chipping in $1/month covers a beefy Hetzner box forever. No begging required.

🛣️ The roadmap (3 phases, real timelines)

Phase 1 — Boot the org (Week 1-2)

• Pick first 5 maintainers via community nominations
• Create the GitHub org
• Set up the README template + script submission format
• Migrate the 10 most-asked-about scripts from old Discourse threads

Phase 2 — Standardize (Month 1-2)

• Every script gets the standard format
• Build a simple install.sh wrapper so even non-coders can run anything
• Set up basic automated testing — “does this script still work today?” — runs daily, flags broken ones
• Onboard contributors via the 3-PR ladder

Phase 3 — Shared infrastructure (Month 3+)

• Spin up the Oracle Free Tier box
• Move scheduled jobs (cookie refreshers, monitors) onto it
• Set up donation address if/when we outgrow free tier
• Community decides if the org goes fully public

🤔 Real questions that need community answers

Before this gets built, the community has to call it:

Question	Options on the table
How do we pick first maintainers?	OG nomination / community vote / both
Public or invite-only org?	Invite-only → safer, slower / Public → bigger but exposed
Donations later?	Optional tips / monthly pledge / Patreon / never
What’s off-limits?	Malware / doxing / kid stuff = obvious nos. CC checkers? Phishing kits? Where’s the actual line?
Rogue maintainer removal?	Majority vote / unanimous / OG override
Where does the discussion happen?	Discord / Telegram / OneHack subforum

Drop your take below. This only works if the community wants it. Otherwise it’s just one guy with a GitHub link nobody uses.

🚪 If this goes live, here's how to plug in

When the org boots (assuming this thread gets the green light):

1. Star the org — bumps visibility, signals you’re in
2. Fork what you want — every script is yours to modify locally
3. Find an open Issue with the good-first-PR tag → submit a fix
4. 3 merged PRs → trusted contributor
5. Or just consume — pull, run, profit, no obligation to contribute

The whole point is lurkers benefit too. You don’t have to be a coder to use the scripts. You just have to know the door exists.

---

Summary: Our best scripts keep dying in old threads. A shared GitHub org would keep them alive, patched, and runnable for everyone — newbies included. Costs nothing to start (GitHub free, Oracle Cloud free). Step one: do we want this?

Drop +1 if you’re in. Tell me which script you’d want parked there first.
Drop -1 if you think it’s a bad idea. Tell me why — I want to be wrong if I’m wrong.

[wasif_farooqui]

Nice idea, but one hack will easily visible and became a target