@elfexecutieble Yeah. LLM started in IP theft. Knowledge unpaid for.
In life we spent resources and money to go to university and pay educators.
Many gracefully shared for free but the majority is pay for knowledge. Then LLMs came and stole everything.
@elfexecutieble Agreed. I raise the point about that this creative spark is very important in the age of code churning machines (AI). Very tough era where no one is safe. Closed source, open source, etc. No license or copyright law can protect you.
You are really simplifying this and boiling it down to fame or recognition. But that still misses the point. I addressed that in the article.
My whole point boils down to ethics and asking for decency. Writing open source for whatever motivation is not an invitation to be stolen from.
The problem is not the author, it is the unethical intentions of those who exploit.
My frustrated and angry posts about @radareorg no longer serve any purpose, so I’m deleting them.
I believe they acted with good intentions. They expressed goodwill, deleted the repo, and sought a positive resolution. I respect that, and it helps prevent fragmentation of the xSQL tooling family. Besides, what’s the point of holding onto a grudge?
For context, r2sql was mentioned during my REcon presentation last Saturday. It has also been in development for much longer than the GitHub history suggests. I typically start with a local repository and only later transition to GitHub after cleaning things up, often resetting the history in the process. I worked on r2sql (still a WIP, although I had to make the repository public prematurely) until the very last minute before my trip to REcon, but I didn’t have enough time to finish it to my satisfaction.
@radareorg seems to like the xSQL family, and because of that, if they’re interested, I’d be willing to move r2sql to their GitHub organization for deeper collaboration.
I still don’t encourage copying under the guise of “vibe coding” or “being inspired by” while directing an agent to cannibalize another repository. But in this case, @radareorg showed goodwill and genuinely sought to make things right.
Come to think of it, @radareorg shares a lot of open source tooling and ultimately has the same goal: serving the security community. I wish them nothing but the best in their efforts, and I hope we can collaborate more in the future.
@radareorg I also want to add that I, too, could have handled this better. I think it’s worth trying to assume people have good intentions until their actions prove otherwise. In this case, @radareorg’s actions spoke louder than words.
Just reverse engineered my Oura Ring 5 so I can control my computer like a wizzard. @ouraring please send my love to whoever buried a feature to stream live accelerometer data
I don't blame you. If you read my X profile, you see that I am not affiliated with Hex-Rays. I don't work with Hex-Rays. I make ZERO from Hex-Rays. All I get is a "BIG THANK YOU" and help the community. While, my account name is "allthingsida". I try to contribute to all RE platforms.
So, if you have issues with pricing, take it to the actual makers.
@radareorg , for full transparency, here's what makes sense and what I propose:
1. r2sql (older than what you published, but kept private just to properly polish it and make it clean. I don't like to rush), is moved to the radareorg GitHub repo
2. You get equal / full access to that repo and get to improve it as much as you wish, while keeping the spirit of collaboration and not fragment the xSQL family
3. Any planned improvements to the xSQL family (a lot of plans ahead), will also be passed over to r2sql.
4. 'libxsql' is not rocket science, but there's a reason it is abstracted out, as all 3 (now 4) xSQL tooling use it and benefit from all its changes and improvements.
5. Whether you want CMake or Meson for r2sql, is not a big deal. Both can co-exist.
6. Again, for r2sql, you get to do what you want. You know r2 best. But I can carry over all my plans and designs over to r2 and benefit that org, in as much as I try to improve the other 3 big RE platforms (IDA, BN and Ghidra).
I don't know what you mean tried to reach out. r2sql was done, and in private since 7 days ago. I even felt the liberty to mention your project in my presentation. I am not hard to reach if you really intend so. Anyway, I published my private repo. If true intentions where there, I could have even added you to the repo from the get go.
It is not too late. If you want to make this right, let's take it private and try again to reach out properly.
PSA: if you are still in @reconmtl and want a hands on (announced last minute)session related to my talk, then bring your laptop and let me walk you through how to use the xSQL family (IDA, BN, Ghidra) to vibe RE. Bring your Claude Code or Codex subscriptions with you.
Otherwise just buy 10$ credits from DeepSeek to use with DS Flash or Pro. 10$ goes a lonnng way, and configure it with your favorite harness (Claude Code, Codex, Pi, etc. ).
Meet me on Sunday at 1PM in Soprano C or check the updated REcon schedule.
I will delete this post later.
@saidelike As I said. Please refer to each xSQL product’s skill repo. It has all the guidance and agent or a human would need.
https://t.co/pSfjtSebGJ
Etc.
Huge respect to api monitor. It's such a beautiful tool for windows apps but hasn't been updated for ages. wanted to keep that spirit alive so built a fresh one.
Currently tracking 30k apis. very early alpha so expect some bugs.☺️
would love your feedback and bug reports.
repo: https://t.co/HRbXj5YyuK
@saidelike As of today there is probably 45% overlap and shared schema in the xSQL family. There are stuff only present in one RE backend but not the other. I am working on that. It is part of the future work mentioned in the slides.