[J. McCarthy]

A mycode display would be cool as well if it read the
https://hackforums.net/btcv.php Prices

[Mr. Robot]

I see what others are saying and like the [help ] or [spoiler] tags it would be awesome to be able to put like
[btcv]
[btcv-current]
[btcv-usd]

For example, btcv would be current price and possibly updated even on posts? Maybe not depending on loads or something however -current would be whatever the price was when they made the post.

[Lante]

I see what others are saying and like the [help ] or [spoiler] tags it would be awesome to be able to put like
[btcv]
[btcv-current]
[btcv-usd]

For example, btcv would be current price and possibly updated even on posts? Maybe not depending on loads or something however -current would be whatever the price was when they made the post.

Yeah that was one of my understandings as a possible application after reading Omniscient's response. A tag that would pull and display the current price based on the timestamp of the post itself. It would greatly benefit the Crypto Currency discussions. No need to open Preev or Bitstamp or BTC-e or Bitcoinwisdom or whatever site people use to quickly check the current price, just a tag :)

Updating posts containing the tag would be too resource-intensive though for the DB, and would create inconsistencies in people using that tag (not sure if that's what your first sentence hits towards or not, forgive me if not). If someone were to use the tag to display a price of $1000, and that post was made a week ago, then the current price would override it and the displayed price wouldn't be on par with what the person is writing about it.

[J. McCarthy]

Yeah that was one of my understandings as a possible application after reading Omniscient's response. A tag that would pull and display the current price based on the timestamp of the post itself. It would greatly benefit the Crypto Currency discussions. No need to open Preev or Bitstamp or BTC-e or Bitcoinwisdom or whatever site people use to quickly check the current price, just a tag :)

Updating posts containing the tag would be too resource-intensive though for the DB, and would create inconsistencies in people using that tag (not sure if that's what your first sentence hits towards or not, forgive me if not). If someone were to use the tag to display a price of $1000, and that post was made a week ago, then the current price would override it and the displayed price wouldn't be on par with what the person is writing about it.

I didn't think about updating tbh that makes sense

While you could timestamp probably would just get confusing

[minimalist]

Would this be adequate?

Code

https://min-api.cryptocompare.com/data/pricehistorical?fsym=BTC&tsyms=USD&ts=1479168000

returns BTC/USD price data for Nov 15, 2016 @ 12:00AM:

Code

{"BTC":{"USD":711.53}}

and

Code

https://min-api.cryptocompare.com/data/histoday?fsym=BTC&tsym=USD&limit=0&e=CCCAGG&toTs=1479168000

returns BTC/USD opening and closing data for Nov 15, 2016:
Spoiler (Click to View)

Code

{"Response":"Success","Type":100,"Aggregated":false,"Data":[{"time":1479081600,"close":704.8,"high":707.73,"low":699.15,"open":702.72,"volumefrom":40781.6,"volumeto":28749513.85},{"time":1479168000,"close":711.53,"high":716.37,"low":700.37,"open":704.8,"volumefrom":44753.15,"volumeto":31947044.36}],"TimeTo":1479168000,"TimeFrom":1479081600,"FirstValueInArray":true,"ConversionType":"direct"}

I feel like the historical day request returns too much data.
https://www.cryptocompare.com/

[Charger]

I like what Minimilaats suggested. It seems to be what Omni was looking for.

[Armada]

Not gonna lie, It's a nice suggestion, however, people shouldn't be lazy and just click https://hackforums.net/btcv.php

I would say even adding this function to the top of the crypto forum would also be very helpful to many members.

I see what others are saying and like the [help ] or [spoiler] tags it would be awesome to be able to put like
[btcv]
[btcv-current]
[btcv-usd]

For example, btcv would be current price and possibly updated even on posts? Maybe not depending on loads or something however -current would be whatever the price was when they made the post.

I like this suggestion as well, but the suggestion of the price updating in posts might get messy for historical data. Being the price changes so constantly, and at so drastically at times, it could lead to a lot of confusion.

Would this be adequate?

Code

https://min-api.cryptocompare.com/data/pricehistorical?fsym=BTC&tsyms=USD&ts=1479168000

returns BTC/USD price data for Nov 15, 2016 @ 12:00AM:

Code

{"BTC":{"USD":711.53}}

and

Code

https://min-api.cryptocompare.com/data/histoday?fsym=BTC&tsym=USD&limit=0&e=CCCAGG&toTs=1479168000

returns BTC/USD opening and closing data for Nov 15, 2016:
Spoiler (Click to View)

Code

{"Response":"Success","Type":100,"Aggregated":false,"Data":[{"time":1479081600,"close":704.8,"high":707.73,"low":699.15,"open":702.72,"volumefrom":40781.6,"volumeto":28749513.85},{"time":1479168000,"close":711.53,"high":716.37,"low":700.37,"open":704.8,"volumefrom":44753.15,"volumeto":31947044.36}],"TimeTo":1479168000,"TimeFrom":1479081600,"FirstValueInArray":true,"ConversionType":"direct"}

I feel like the historical day request returns too much data.
https://www.cryptocompare.com/

Sounds like exactly what Omni was looking for. 🙂