Case study
Terminal: a Rust terminal informed by TradingView chart research
An independent Rust market interface uses REA browser-scenario research on public logged-out TradingView chart interactions. The notes retain observed/documented/inferred/unknown labels; the result supplies its own chart engine and data providers rather than recovering TradingView or Bloomberg server software.
- Targets
- App · Website
- Category
- Community REA investigations
- Relationship
- Author-reported mixed workflow
- Sources reviewed
Requirements & limits
- Prerequisites: Source builds need Rust and the documented platform graphics setup. Data can use an offline sample or external providers; brokerage connectivity is optional and requires the user's own provider/account setup.
- Attribution: REA captured browser scenarios from a public logged-out chart. Login-only behavior, some pointer gestures and unavailable interactions remain unknown.
- Limits: Scanned disclosure PDFs are not OCR-processed; unofficial data endpoints are rate-limited and upstream filing-use terms still apply.
- License: No project-wide license was identified in the reviewed root/README; repository access does not grant rights to external market data.
About this entry
The description was reviewed against primary sources.
Primary sources
- README.md GitHub · michaelshimeles/terminal · Revision 94bb329
- docs/analysis/README.md GitHub · michaelshimeles/terminal · Revision 94bb329
More in Websites
- BaoCut Design: porting reconstructed canvas and design-system editors · Case study
- whatsapp-web-reveng: documenting the legacy WhatsApp Web protocol · Case study
- Ruffle: a Rust reimplementation of Adobe Flash Player · Case study
- Littlebird.ai static home-page rebuild · Case study
- Sheypoor MCP: mapping marketplace APIs from browser traffic · Case study
- ZCode-Android: reconstructing the ZCode remote-control client · Case study