Got something you’d like to tell us? Suggest it here and vote for other users’ ideas.
Completed
optimize CPU/RAM
Loving Kiyotaka! Noticed long sessions can slow my Mac. A few practical tweaks (similar to what TradingView does) could help a lot: Throttle & batch WebSocket updates (e.g., 10–20 Hz) and don’t render in the WS callback—render only via requestAnimationFrame., Keep data in bounded ring buffers (e.g., 10–20k points per series); avoid unbounded arrays., Downsample to viewport (≈ one point per pixel column) before drawing., Move parsing/indicators to a Web Worker; consider OffscreenCanvas for rendering., When the tab is hidden, pause rendering and lower ingest rate., These usually cut CPU/RAM use dramatically while keeping charts snappy.
Kiyotaka could be so much better
Shoutout to the devs for being so fast with the bug fixes and new releases. The pace of development is honestly impressive and the quality of the work is top-tier. However, it feels like there’s a bit of a disconnect between the current roadmap and what the community is actually asking for. While the new additions are great, I’d love to see the specific feature requests we’ve been voting for take center stage. The updates are awesome, but keeping the community’s needs at the forefront would make it even better.
Pls return the previous candlestick and footprint chart
The candlesticks on the chart now look so bad…
THE LANDING PAGE SHOULD BE LESS DENSE WITH INFORMATION AND MUCH MORE SIMPLER TO VIEW
When loading the site for the first time, the landing page appears to be dense with informations and strong conflicting yellow-ish colours, it would be great if the informations are minimized allowing for users the options to add the kind of analytics tools they'll need after they logging and more distinct colours are introduced (like the normal green for uptrend and red for downtrend on the charts) etc I attached a small table to highlight everything