I see writing posts and commenting as two separate ways of contributing. These are 2 different styles.
I prefer writing high-quality content (posts) instead of commenting. It is not in my nature to write comments (and this style of contributing).
It does not mean that I am not putting high effort into writing posts - quite the opposite. When I write long content I put all my heart into it and many hours.
What I mean is that I would love to meaningfully contribute and gain karma by doing "content" the way I like and prefer and not being forced to comment.
Unless your ideas are a monolith ("Read my 2000 word essay or nothing!") then maybe reply to other posts with relevant snippets of your work and link to the longer content.
At the end of the day, the whole should be greater than the sum of the parts but if your content is good you'd expect your parts (shorter sub-ideas) would at least be clear and well-written enough to draw some upvotes as comments.
Also, even if "good" posts are rare (which as others have said sounds pretty arrogant), you should be able to post comments that are helpful clarifications or corrections on those posts.
I get that you'd prefer to gain karma by posting not commenting but the gating method is based on comment karma to earn the right to get posting karma.
I think you're stuck, until you either earn comment karma or find channels to write content on which gains karma.
It is implemented, but it's embedded in the product at https://vidocsecurity.com/. I was thinking about extracting that part and creating a standalone API for it
Not at this time, I only thought about releasing it as an API for companies to use within their own products (my API would only return JSON file with all of the nodes and edges from graph)
I am a co-founder of https://vidocsecurity.com/ - one of our main features is validating security issues. To validate the security issue you need to find relevant context - let's say we detected a potential security issue in file "test.ts" in function "doStuff". We would need to find what other functions in the repository reference this function and do it recursively to build a call tree. Then we use LLM to validate each branch of the tree to understand if the issue could be exploitable.
It took me a couple of months to solve the context fetching and I managed to solve it in a way that is really easily extendable to other languages. At this moment we support Typescript, JS, Python, Go, Ruby, and Rust. I can add many more languages.
I talked with other founders and understood that what I built might be valuable to other companies as they rely on supporting as many languages as possible. This post is my attempt to understand if it is a real problem or if I just imagined it myself.
