A source-backed Rankhog guide to r/opensource: public rules, community context, posting fit, and startup-promotion risk before you publish.
By Anthony Riera, founder and operator of Rankhog.
Subreddit guides combine public Reddit source URLs, captured rules, visible verification dates, and Rankhog's account-safety workflow.
Current public stats
Rules can change, so Rankhog keeps verification dates and the original public Reddit sources visible.
These are the highest scoring posts Rankhog observed in r/opensource over the past month, with what each one did differently. Rankhog watches this community continuously, so it sees posts when they are published and again as they climb.
Across 134 posts, the ones that did best tend to tell a personal story, break the body into short paragraphs, are written in the first person.
Why it worked
Why it worked
Why it worked
Why it worked
Why it worked
Why it worked
Why it worked
Why it worked
Why it worked
Why it worked
This community is for everything open source related, using the Wikipedia definition of open source. People post news, discussion, and projects connected to open source software. The rules say the sub is a place for discussion and news regarding the world of open source projects.
The rule called 'No Spam or Excessive Self-Promotion' is the one that decides whether your project announcement survives. The rule called 'Be On-Topic' adds a hard requirement that any linked code or repository must have a license file that is an OSI listed open source license. The rule called 'Use Correct Flairs' means your post needs the right flair or it can be removed. The rule called 'No Drive-By Posting / Karma Farming' tells you that posting and leaving without engaging is a removal risk. The rule called 'No Sensationalized Titles' matters if you are linking to an article about your project.
A good post here is an honest story about something open source you built or are building, with a repository that carries an OSI approved license. The top posts show that people respond well to founders who open sourced a real product under a known license like MIT, or who built a useful directory and shared it. Use the Promotional flair when you share your own project. Write a title that matches the article or project without hype. Then stay in the thread and answer questions, because the rules want you to engage rather than drop a link and leave.
Avoid anything the rule 'No Spam or Excessive Self-Promotion' calls out, such as using the sub as a link farm for your project, website, or channel. Do not post AI generated content, because the rule 'Memes & Low-Effort Posts' says all AI generated content is low effort and ban worthy. Do not link a repository that lacks an OSI listed license file, since 'Be On-Topic' requires it. Avoid sensationalized or rewritten titles when you link to an article, per 'No Sensationalized Titles'. Do not post and run, because 'No Drive-By Posting / Karma Farming' says drive by posts may be removed. Do not link to aggregations or newsletters, because 'No Link Aggregations' says to link to the actual story.
Want the version that does not run out? Subscribers get unlimited tool runs and more careful checks before posting.
Get my free Reddit SEO auditStart your 3-day free trial. Card required. $99/month after trial. Next, connect a verified Reddit account; no strategy starts until you explicitly start Rankhog.
Yes, if you keep self promotion to a reasonable degree and use the Promotional flair. The rules say they are a little more forgiving than Reddit's under ten percent guideline, but they do not want you using the sub as a link farm.
The repository must have a license file and that license must be OSI listed. The rules state this explicitly and say linked code must comply.
Use the Promotional flair when you are sharing a project, yours or otherwise. The rules define this flair for exactly that purpose.
No. The rules say all AI generated content is low effort and ban worthy.
Use the Alternatives flair, which the rules say is for soliciting suggestions of open source software that fulfills a need.
Technical product and developer communities
A source-backed Rankhog guide to r/InternetIsBeautiful: public rules, community context, posting fit, and startup-promotion risk before you publish.
Technical product and developer communities
A source-backed Rankhog guide to r/webdev: public rules, community context, posting fit, and startup-promotion risk before you publish.
Technical product and developer communities
A source-backed Rankhog guide to r/reactjs: public rules, community context, posting fit, and startup-promotion risk before you publish.