HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
radare
r2hate
HISTORICAL RECORD2019–2020
radare / r2hate · Not publicly available

r2hate

Discover this repository through its Hacker News conversations.

2Distinct people
2Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month2 dated mentions

Observed mentions: 2019-01-06 09:07:45 UTC to 2020-12-13 17:14:11 UTC.

012019-01-01 00:00:00 UTC to 2019-02-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 20192019-02-01 00:00:00 UTC to 2019-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-01 00:00:00 UTC to 2019-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-01 00:00:00 UTC to 2019-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-05-01 00:00:00 UTC to 2019-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-06-01 00:00:00 UTC to 2019-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-01 00:00:00 UTC to 2019-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-08-01 00:00:00 UTC to 2019-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-09-01 00:00:00 UTC to 2019-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-10-01 00:00:00 UTC to 2019-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-11-01 00:00:00 UTC to 2019-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 20192020-01-01 00:00:00 UTC to 2020-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-02-01 00:00:00 UTC to 2020-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-01 00:00:00 UTC to 2020-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-01 00:00:00 UTC to 2020-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-05-01 00:00:00 UTC to 2020-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-01 00:00:00 UTC to 2020-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-07-01 00:00:00 UTC to 2020-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-01 00:00:00 UTC to 2020-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-09-01 00:00:00 UTC to 2020-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-10-01 00:00:00 UTC to 2020-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-11-01 00:00:00 UTC to 2020-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-12-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 2020

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 20192019-01-01 00:00:00 UTC2019-02-01 00:00:00 UTC101
Feb 20192019-02-01 00:00:00 UTC2019-03-01 00:00:00 UTC000
Mar 20192019-03-01 00:00:00 UTC2019-04-01 00:00:00 UTC000
Apr 20192019-04-01 00:00:00 UTC2019-05-01 00:00:00 UTC000
May 20192019-05-01 00:00:00 UTC2019-06-01 00:00:00 UTC000
Jun 20192019-06-01 00:00:00 UTC2019-07-01 00:00:00 UTC000
Jul 20192019-07-01 00:00:00 UTC2019-08-01 00:00:00 UTC000
Aug 20192019-08-01 00:00:00 UTC2019-09-01 00:00:00 UTC000
Sep 20192019-09-01 00:00:00 UTC2019-10-01 00:00:00 UTC000
Oct 20192019-10-01 00:00:00 UTC2019-11-01 00:00:00 UTC000
Nov 20192019-11-01 00:00:00 UTC2019-12-01 00:00:00 UTC000
Dec 20192019-12-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
Jan 20202020-01-01 00:00:00 UTC2020-02-01 00:00:00 UTC000
Feb 20202020-02-01 00:00:00 UTC2020-03-01 00:00:00 UTC000
Mar 20202020-03-01 00:00:00 UTC2020-04-01 00:00:00 UTC000
Apr 20202020-04-01 00:00:00 UTC2020-05-01 00:00:00 UTC000
May 20202020-05-01 00:00:00 UTC2020-06-01 00:00:00 UTC000
Jun 20202020-06-01 00:00:00 UTC2020-07-01 00:00:00 UTC000
Jul 20202020-07-01 00:00:00 UTC2020-08-01 00:00:00 UTC000
Aug 20202020-08-01 00:00:00 UTC2020-09-01 00:00:00 UTC000
Sep 20202020-09-01 00:00:00 UTC2020-10-01 00:00:00 UTC000
Oct 20202020-10-01 00:00:00 UTC2020-11-01 00:00:00 UTC000
Nov 20202020-11-01 00:00:00 UTC2020-12-01 00:00:00 UTC000
Dec 20202020-12-01 00:00:00 UTC2021-01-01 00:00:00 UTC101

What Hacker News says

2 sources
A quick update. I think I've got a better picture of what's going on. Firstly, the fortunes mess. It turns out that this is unrelated to the Rizin fork. That fortunes PR happened because of a tweet, which gained moderate popularity, on November 26th, criticizing the fortunes.nsfw file. (Please do not harass this person over their tweet.) ...which occurred after the fork. As far as I can ascertain, the fortunes mess simply doesn't play into this. Unfortunately, this same person seems to think the fork is about that, which is understandable, due to the apparent timelines. On December 6th, they accused Rizin of being an elaborate troll. (I repeat: please do not try to find these tweets and harass them. Disagree in your head if you need to.) THIS tweet is the source of the Reddit comment that is so intriguing. But it's wrong. This isn't about
Read the rest
fortunes.nsfw. The Rizin announcement may be vague, but it's honest: it's really about major disagreements, both technical and otherwise. But I will get to that later. --- OK, part 2. I was wrong to conclude that the Github team was representative of all of the users that are moving to Rizin. It turns out it's more. So far, you can additionally see pull requests from kazarmy (#2 contributor to radare,) yossizap (#11 contributor to radare.) In addition, because this fork is so relatively new, there are almost certainly other developers who have moved or will move over. An especially strong signal of this is how many of the developers who are high up in the contributors list do not appear recently in the Radare2 pull requests; a majority of open pull requests right now are actually from pancake themselves. In addition, today I can see there are more users on the GitHub team, including Cutter developer "karliss" and Github user "kazarmy", Khairul Azhar Kasmiran. In addition, we can now see user "officialcjunior", Aswin C, one of the top contributors to the r2book in the last year. --- And finally. The real reason. To most people reading these comments, we are outsiders, but there is a clear sentiment within the r2 community that it is unwelcoming, and there is some strong evidence for this. For example, there was apparently, at some point, a repository dedicated to... collecting Radare2 hate into Github issues. This is oddly condescending, but what's more concerning is that this seemed to be a way of getting back at anyone who said anything negative about the project. https://web.archive.org/web/20180612221427if_/https://github... Mention of r2hate exists on social media. A very well-respected engineer also noted, "...i've been informed that they coped by mocking me in private." Interesting indeed. If you keep digging you can find more and more evidence that the unprofessionalism of how radare2 was being ran was becoming a drain on the project, and that the issues that lead to its forking are multi-faceted, but absolutely include technical disagreements. Here are some quotes. I have changed the wording slightly to discourage people from harassing folks, but you can find them if you try hard enough. If you must, please do not interact; it's bad netiquette. I'm just trying to illustrate the problem. > ignoring everyone's thoughts or feelings or ideas when you don't "get" them 100% is part of why people were calling you an asshole > In all seriousness that is unbelievably childish. I can just imagine them linking to this exact tweet in one of those "issues" and chuckling about how we're the ones being dicks here without realizing the irony of posting "hatemail". You can find quotes and threads about it all over. And some of them are people I really respect and trust. There is also some interesting discourse about Radare2's technical direction, including this comment that seems to have resonated with a couple of people despite being hidden on an old April fools PR. https://github.com/radareorg/radare2/pull/16392#issuecomment... In other words, this isn't a stunt or a knee-jerk reaction. Rizin is likely the fork you want.
In Rizin – a free and open-source Reverse Engineering framework

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.