Thanks! Yeah that's true, it fetches the crypto balance from your exchange and calculates the USD balance using coinmarketcap.com. In a future update I'll add the option to use the USD balance from the exchange, if present. Thank you for your feedback!
Kind of makes sense, it probably recognizes it because multiple relevant APIs are hit.
Unfortunately, for me personally this makes it impossible to trust the application.
I have Little Snitch running and the only two connections the application attempted to make were for coinmarketcap.com that is setup as the "exchange" to get the current market price and the exchange I currently use when I added my wallet.
I know bitbar, but with all the plugins installed, it's pretty bloated. I wanted a tool that unites all exchanges and wallets in a lightweight interface.
No, it's not intentional. I have seen it but it is variable. On one computer it never happens and on another it happens like you said and on another it's always slow.
The way this works is that I add points to an array while dragging. There is a loop that adds a point and draws a line to the last point. I think that interval of drawing is what slows it down but that is just what I felt like it had to be.
Having written numerous large .js files in my time, a contributing factor is that it's an enormous pain in the ass to split javascript up into smaller files. You have to update a bunch of <script> tags everywhere, or depend on a specific module loader (which means all the libraries and existing code have to be updated to support that module loader, in some cases including third party code), or...
I eventually wrote a stripped-down loader for JSIL to address this problem (so I wouldn't have to force end-users to adopt something specific like require.js or something), but there are still real usability issues for maintaining a codebase full of small .js files (like the near-fixed overhead per-request for javascript). Ideally ES6 module loading will address some of this, and for the rest, I guess everyone will have to adopt a build process for javascript (ICK) and give up on instant reloads after file changes.
kevingadd pretty much sums up why I did one file. I do agree that such large files to get hard to maintain. To help with that I used regions, though I admit since it's a VS only feature it's of limited use.
No thanks. I definitely don't want a site to have the ability to set my clipboard. It will be much easier to help spread malicious links (visiting a site using paste and go). Plus what about the annoyance of having something in your clipboard that you were going to paste somewhere then due to visiting another site it gets wiped?
