Hacker News new | past | comments | ask | show | jobs | submit login

For those on the opposite side of the privacy and tax spectrum, there is also a portfolio tracker (which I wrote) that is doing the opposite:

A static HTML Website where you save your portfolio via a bookmark.

- No tracking (no cookies, no emails, no JS* )

- Fast (~ 2 kB download)

- Cross-Platform ;-)

http://www.cryptoport.net

* There is JS on the landing page to generate the link for your portfolio. The portfolio page itself is free of JS.




Nice idea, but you should support HTTPS. People are entering their balances and I for one wouldn’t wanna be snooped!


I fully agree, will probably happen within the next few weeks.


It likely will only take you an hour at most with LetsEncrypt. Why wait that long?


It's done!


Awesome! I'd also recommend having all HTTP requests redirect to HTTPS, but I know that can be a little tricky if you're not too familiar with configuring your web server, and can be difficult to fix if something goes awry.


Haha, I didnt think you'd read it! Anyway, I want to wait a little to see if there are problems and if not, I'm gonna redirect. I use an nginx reverse proxy, everything seems pretty straightforward, so it's more a matter of taking things one step at a time.


Nice! A single server-generated multi-series chart would be nice but if it takes away from the simplicity then that's fine. If you haven't already seen it you can get volume/price/marketcap between a start/end date. https://graphs2.coinmarketcap.com/currencies/bitcoin/1487234...


You mean an image that shows the top X price time series?

If so, I have a few questions:

- On a per-portfolio basis or just for the top 5 coins (+ maybe market cap)?

- update interval should be more like 2 minutes (like the site) or once per day is ok?

- start-time should be how many days back?

From a dev perspective, it would be nice if there were a solution to this that allowed for either A. time series caching (to avoid stressing CMC) or B. image caching (to avoid CPU load, this currently runs on a free gcp instance).


For me, personally:

- One aggregated portfolio position over time would be enough for me i think

- Once per day is fine

- Given crypto volatility, 1 year would work.

Maybe a combo of image caching and time series caching would make this economical. Image caching for aggregated portfolio position - and if you're generating the image everyday (or eventually more frequently) for many portfolios then you could calculate and cache the individual coin time series and use that cache to aggregate and generate many charts.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: