How is the Flexcoin API going? From what I can tell there's no API yet. Once an API is in place then I can add support for flexcoin balances in CryptFolio as requested by your users: https://bitcointalksearch.org/topic/m.1993478
Your API should have a secret-based method that returns the users' current balance in each currency. This API must be read-only, it must not be possible to make transactions with this "get balances" API. Mt.Gox, BTC-e and Vircurex all do it very well.
You should also fix your password length, the fact that a password can only be a maximum of 20 characters suggests you are storing it in plaintext and not hashing it.
Topic: Flexcoin API -- need some feedback... (Read 1592 times)
I completely hear you ... and you're 1000% correct... but I don't want to include functionality that won't be needed, it will lead to code bloat... which always means more security problems.
Another major reason I need some sort of target list is due to our marketing of the API .. if mobile is huge.. then I would like the ability to pitch it to mobile developers.
Another major reason I need some sort of target list is due to our marketing of the API .. if mobile is huge.. then I would like the ability to pitch it to mobile developers.
DRM? Sounds like a bad idea.
Smartphone access sounds like the best idea of the ones you've posted, but that is something built on the API, not in the API itself.
In the API, you need the usual functions to get account info (balance, transactions, deposit addresses), and to send coins (to addresses or flexcoin names). Also, to enable shopping carts and such you need a way to tell the system to expect payments, and things to do when the payments arrive (callbacks, sweep policies, re-transfers, etc).
Smartphone access sounds like the best idea of the ones you've posted, but that is something built on the API, not in the API itself.
In the API, you need the usual functions to get account info (balance, transactions, deposit addresses), and to send coins (to addresses or flexcoin names). Also, to enable shopping carts and such you need a way to tell the system to expect payments, and things to do when the payments arrive (callbacks, sweep policies, re-transfers, etc).
I appreciate the 1.5 million private messages, but honestly it would make more sense to make those ideas public for further comment.
1 - DRM
2 - iphone / android app development
3 - Voting booth
4 - pgp (taken from below thread)
Were the top ones ... but I really want more published here rather than filling up my inbox... my inbox doesn't help everyone comment you know?
1 - DRM
2 - iphone / android app development
3 - Voting booth
4 - pgp (taken from below thread)
Were the top ones ... but I really want more published here rather than filling up my inbox... my inbox doesn't help everyone comment you know?
ok we're *almost* done with the API ...
I need some feedback or better said a "wish list" of what functionality you want in the API.
I already got some feedback in terms of ease of use to develop mobile apps from it... IE: people want a iphone / android app that doesn't require downloading the whole blockchain, I have some requests to have features built into it to allow for DRM (don't ask... not my idea).
Any other potential uses that you can think of that you would like built into it to allow developers to build what they need...
I need some feedback or better said a "wish list" of what functionality you want in the API.
I already got some feedback in terms of ease of use to develop mobile apps from it... IE: people want a iphone / android app that doesn't require downloading the whole blockchain, I have some requests to have features built into it to allow for DRM (don't ask... not my idea).
Any other potential uses that you can think of that you would like built into it to allow developers to build what they need...
Jump to: