11–20 of 31 posts
Earlier quoted context omitted.
In today's climate I would be extremely weary of npm installing any core bitcoin tech without a serious line by line audit of the source.
Why would this be more true of npm than any other package manager for any scripting language?
Earlier quoted context omitted.
All libraries expose an API, which is its set of public functions.
Sure but it seems strange way to discuss it. Unless it's an API that wraps some existing library.
Anyway, I'm not trying to nitpick or keep this side-discussion alive. But I'm genuinely curious how most people classify the difference between api and library.
Also on a sidenote, who's downvoting all the comments and the thread itself? This seems like a really cool project and it doesn't look like anyone's posted anything completely irrelevant here.
Earlier quoted context omitted.
Sure but it seems strange way to discuss it. Unless it's an API that wraps some existing library.
I believe haakon is correct on this one, unless I'm missing something. We just got into an argument at my work over the correct usage of the term "api", but found this post to back up my arguments - http://stackoverflow.com/questions/8772746/difference-betwee... Anyway, I'm not trying to nitpick or keep this side-discussion alive. But I'm genuinely curious how most people classify the difference between api and libra…
The thread itself, no clue, how can you even see that? I'd assume there's quite a bit of people who get tired of hearing about bitcoin though. It's a bit like how I really, really didn't feel like hearing about social media being the biggest thing ever years back, until it became something actually substantial recently.
As for the comments, all I see is 'oh cool, awesome'. HN doesn't like that, you just use upvoting to show appreciation.
Anyway, I can't help but say it's pretty awesome, too. Bitpay's definitely been doing some great open-source work to create a bitcoin library that works as well (and similarly) in the browser as server side, it's really nice to work with and very comprehensive, too. I wish they had a little showcase page going where they point you to projects that use it, though. Their own Copay does for example, a shared wallet which I've tried a couple times, works very nicely.
Looks awesome. Cryptocurrency development has seemed pretty intimidating to me but this is probably the going to be the push that gets me started supporting tip sharing features on my site.
- https://github.com/bitcoinjs/bitcoinjs-lib (one of the best)
- https://github.com/indutny/bcoin (Indutny's work is found throughout Node.js and is the basis of elliptic curve cryptography in Bitcore)
- https://github.com/ryanxcharles/fullnode (ex-developer of Bitcore and now engineer at Reddit behind Reddit's crypto currency initiative)
- http://cryptocoinjs.com/ (disclosure: I started this one)
Here is an older article that I wrote about understanding how an Address is created (still valid, but using an older version of bitcoinjs-lib): http://procbits.com/2013/08/27/generating-a-bitcoin-address-...
The cool thing is that you can use test Bitcoins without any risk to learn how to program for Bitcoin. Use these faucets: http://tpfaucet.appspot.com/ and http://faucet.xeno-genesis.com/
Here is a very simple wallet that I built to demonstrate how easy it is to build one: https://github.com/coinbolt/simple-wallet
Finally, an open source app to test the purchasing experience of Bitcoin: https://github.com/coinbolt/catshop
Looks awesome. Cryptocurrency development has seemed pretty intimidating to me but this is probably the going to be the push that gets me started supporting tip sharing features on my site.
As well as ChangeTip: https://www.changetip.com/
It might be what you're looking for, unless you want to custom build something. In that case also give Chain.com a look as well as Blockcypher.com.
Coinbase also has some nice developer products, their api: coinbase.com/docs/api/overview
and if you want to do anything relating to raw bitcoin data (the blockchain and all transactions) i.e., run a node, I'd recommend Toshi.io, an open-source node that is very easy to query. Quite a few people run this thing on an AWS tier.
Hope that helps if you want to dabble with a bitcoin project for your site :)
Earlier quoted context omitted.
Sure but it seems strange way to discuss it. Unless it's an API that wraps some existing library.
I believe haakon is correct on this one, unless I'm missing something. We just got into an argument at my work over the correct usage of the term "api", but found this post to back up my arguments - http://stackoverflow.com/questions/8772746/difference-betwee... Anyway, I'm not trying to nitpick or keep this side-discussion alive. But I'm genuinely curious how most people classify the difference between api and libra…
Who else? Bitcoin haters and deniers like patio11. Such kinds of irrational and emotional people are everywhere, including HN. Keep in mind they can be good and logical at other things, but get emotional on one particular subject. Bitcoin shakes some of the foundations everyone on Earth has or has had at some point (like the concept of money, the justifications for inflation, etc.), and a lot of people don't like change.
It's an exciting time to be a JavaScript developer for Bitcoin. There are a number of JavaScript libraries for Bitcoin. Here is a comprehensive list of alternatives to Bitcore: - https://github.com/bitcoinjs/bitcoinjs-lib (one of the best) - https://github.com/indutny/bcoin (Indutny's work is found throughout Node.js and is the basis of elliptic curve cryptography in Bitcore) - https://github.com/ryanxcharles/fullnod…
I think that's a pretty important thing to clarify if you're creating/signing transactions via JS.
Earlier quoted context omitted.
Sure but it seems strange way to discuss it. Unless it's an API that wraps some existing library.
I believe haakon is correct on this one, unless I'm missing something. We just got into an argument at my work over the correct usage of the term "api", but found this post to back up my arguments - http://stackoverflow.com/questions/8772746/difference-betwee... Anyway, I'm not trying to nitpick or keep this side-discussion alive. But I'm genuinely curious how most people classify the difference between api and libra…
JMS is an API [1], [2].
ActiveMQ [3] is an implementation of the JMS API.
Commons BeanUtils [4] is a library. The library itself has an API (that's how we interact with the library).
There is a semantic difference between the "JMS API" and the "BeanUtils API".
The former is just an API. It's a standard. It has no implementation. Implementations are all expected to utilize the API.
The latter is a library, but we need to talk to the library - and we do that through its API. However, the API that BeanUtils exposes is not standardized. It's by and large local to BeanUtils.
I hope this helps. Sorry it's so Java centric.
[1] http://en.wikipedia.org/wiki/Java_Message_Service
[2] http://docs.oracle.com/javaee/6/tutorial/doc/bncdr.html
This looks more like a library than an API. I wonder why the decision was made to market it this way.