Vector35 / Vector35/binaryninja-api
action system log
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Similar to #2260, we've long discussed adding a telemetry system that would allow users to record a log of their actions for submitting to Vector35. This would also help when trying to discover what actions are behind what user interface.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the related issue #2260 and clarifying the long-discussed telemetry requirements from this issue. Identify the project entry points for recording user actions, then define what a complete action log must contain and how users would submit it to Vector35. Done means the telemetry scope and user-facing workflow are specified well enough to implement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools, reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100