clash-freenode points at a subscription link and a node count
Free, regularly updated shared subscription links for unrestricted internet access. One-click subscribe for SSR/Clash/V2Ray. Please do not abuse.
At a glance
- What is it?
- clash-freenode is a two file notice board for a free Clash, V2Ray and SSR subscription: the working address lives on free.datiya.com, the daily table has read 14 nodes since 2026-10-23, and nothing about the servers behind the feed is recorded anywhere.
- Who is it for?
- Treat clash-freenode as a pointer, not a service: it names where the free Clash, V2Ray and SSR subscription lives and how large it claims to be, and nothing beyond that. Before letting it carry daily traffic, confirm that free.datiya.com resolves from your network, that the channel at t.me/freenodedaily still posts, and that the address you imported works today, because the repository keeps no fallback host, no version and no record of who operates the servers it points at.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- OpenRunner/clash-freenode6,531 ★ · +73
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| OpenRunner/clash-freenode | 6.5k | 6.5k |
73 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Two files at the top level and nothing to build
The default branch is main, and the whole repository is two entries: README.md and featured.jpg. There is no package manifest, no client build, no config directory, no dependency list and no tagged release. That single fact shapes everything else here. What gets published is a short Chinese instruction sheet rather than a set of proxy endpoints, so there is no artifact to install and nothing to compile. The image at the root is the only binary object in the tree, which fits a landing page aimed at someone scanning a search result instead of a developer cloning a tool. A reader who expects a folder of ready configs will find nothing past the note table and three numbered steps.
The working address sits on free.datiya.com, not in the tree
The opening move in the README is a redirect: the newest subscription address has to be fetched from https://free.datiya.com/, and a Telegram channel at https://t.me/freenodedaily is offered for the same feed. No address string is committed to the repository itself, so the link that matters rotates on a schedule the repo does not control. The repository is a signpost that outlives the pointers it carries, and that is why a dead address is a routine outcome rather than a defect worth filing. The split of responsibility is clean: the site serves the payload, the repository carries the instructions, and nothing in the tree records which address was current on which day. The daily node table is the only dated history kept on the page.
Fourteen nodes across eleven days, with no row level detail
The single table with real content counts nodes per day. Every row from 2026-10-23 through 2026-11-02 reads 14, including the date the header marks as its last update, 2026-11-02. A flat column across eleven days shows the output size held constant while the individual servers behind it may well be replaced, and nothing in the table distinguishes those two cases. What the table never offers is any entry level detail: no node name, no host, no country, no protocol tag per row, no latency figure and no expiry date. The project description advertises SSR, Clash and V2Ray formats and asks readers not to abuse the nodes, but no file maps those formats to specific entries. The count is a size report, not an inventory.
git pull is the only command the whole guide contains
For anyone who already cloned the repository, the documented refresh path is a git pull, or the sync control on the GitHub page. That is the entire command surface the documentation offers:
git clone https://github.com/OpenRunner/clash-freenode.git
cd clash-freenode
git pullAfter the pull the working tree still holds README.md and featured.jpg, so a successful update changes prose and one table row instead of adding endpoints. A fetch therefore cannot repair a dead subscription. It can tell you that another day was logged, and nothing more. There is no tag, no branch that carries the current address, and no machine readable file a client could read directly, so a clone stays informative rather than operational.
Picking a client is the one step the guide never names
The first run path is three numbered steps: visit the site for the latest subscription address, download the matching client software, import the address. Step two carries the whole weight of that choice, and the README keeps it that short. No operating system is named, no client program is named, and no version is given, so a reader on Windows, macOS, Linux or a phone follows the same instruction with no fork in the path. Nothing states whether the feed is a Clash YAML, a base64 list or an SSR set, even though the project description names those three formats. No screenshot is labelled with a particular client interface, so import is assumed to be a single action inside software the reader already has installed.
A dead link and an unreachable site each have one documented answer
Two failure modes are covered. A subscription link that will not load gets the same instruction handed to a new user: fetch the current address from free.datiya.com again, on the assumption that the old string expired. If that update address itself cannot be reached, the instruction is to open an Issue on the repository. That second route is the only support channel named anywhere, and no mirror, cached copy or alternate host is listed as a fallback for it. No file records which addresses have been handed out, so there is no archive to recover a working string from, and an Issue thread becomes the only durable trace of an outage. Cloned copies are told to pull or use the sync control, which is how a stale local copy catches up to the notes.
Updates land as commits on main, never as versions
There are no releases, no tags and no version string, and the last push to the repository is dated 2026-11-01, one day before the date carried in the README header. Changes reach readers as ordinary commits, which means a client importing the feed has no way to notice a format change on the site side, and a reader has no version to compare against when something breaks. The two dates also disagree in a small but visible way: the header claims an update later than the last push, so the freshness mark on the front page is not proof that anything was published at that moment. Verification has to come from the site and the channel instead.
CC BY-SA 4.0 covers the notes, and nothing identifies the servers
The licence line names CC BY-SA 4.0, which covers the text and the image held here, but the documentation attaches no provenance to the endpoints the feed points at. There is no operator, no hosting arrangement, no retention note, no uptime figure and no expiry for an individual entry. A reader cannot learn who runs a node, in which country it sits, how long it is meant to last, or whether the address is shared with anyone else. The request not to abuse the nodes is the only stated norm, and no privacy note covers what a client reveals by pulling that address. For something meant to be pasted into a client and used for daily traffic, those omissions are the practical ceiling on what this repository states.
Editorial conclusion
Treat clash-freenode as a pointer, not a service: it names where the free Clash, V2Ray and SSR subscription lives and how large it claims to be, and nothing beyond that. Before letting it carry daily traffic, confirm that free.datiya.com resolves from your network, that the channel at t.me/freenodedaily still posts, and that the address you imported works today, because the repository keeps no fallback host, no version and no record of who operates the servers it points at.
Frequently asked questions
Where do I get the current subscription address from clash-freenode?
The README sends readers to https://free.datiya.com/ for the latest address and to the Telegram channel at https://t.me/freenodedaily. No address string is committed to the repository itself.
How many nodes does clash-freenode list, and does that count change?
The daily table reads 14 nodes for every date from 2026-10-23 through 2026-11-02, and the header marks 2026-11-02 as its last update. The count is identical on all eleven rows.
Does cloning clash-freenode give me the node list itself?
No. A clone holds only README.md and featured.jpg, and the documented refresh is git pull, so the repository delivers instructions and a count rather than proxy endpoints.
What should I do when the clash-freenode subscription link stops working?
The documented answer is to fetch the newest address from free.datiya.com again, and if that update address cannot be reached either, to open an Issue in the repository. No mirror is offered.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/openrunner-clash-freenode)Star history chart for your README
[](https://hysenlabs.com/projects/openrunner-clash-freenode)Was this useful?