Topic: [ANNOUNCE] +Coin Web UI for Bitcoin and its forks. - page 2. (Read 6252 times)
Any news on this?
I'm planning on CC since that allows most things, but I have a new issue... I'm unsure what the licensing issues I'll have if I throw it under CC considering:
- Bootstrap is Apache v2
- and JSONRPC-PHP is GPL v2
Can anyone good with licenses explain to me whether I'm allowed to release my code under Creative Commons, and whatever steps I have to do to ensure I'm not breaking their licenses?
First, please don't release software under Creative Commons. Creative Commons wasn't designed for software (it's designed for content: photos, books, music, etc). See http://wiki.creativecommons.org/Frequently_Asked_Questions#Can_I_apply_a_Creative_Commons_license_to_software.3F
Second, IANAL, but if you use a GPL's library like JSONRPC-PHP and if you choose to distribute your application to others then your code must also be GPL (or public domain, since that means you are relinquishing your copyright altogether). If this isn't something you want to be forced to do, then don't use the JSONRPC-PHP library (JSON RPC is not that complex... you could probably just whip up a couple wrapper functions yourself if you had the desire). Apache v2, on the other hand, is a pretty restriction-less license. In fact, it may be one of the licenses you might want to concider instead of using Creative Commons as it basically says "do whatever you want, just don't blame me, and don't remove my copyright notices, etc").
So... Anyone want to help with my question above ^ so that I can finally release it?
Some quick questions:
Appart from that, cool project even if you use it on your local machine with XAMPP (or linux)
- Does the bitcoind need to run on the same server as the php files?
- Does the wallet need to be in the same place?
Appart from that, cool project even if you use it on your local machine with XAMPP (or linux)
1. No, it uses host/port, it uses the JSONRPC, so it would allow connecting to say yourdomain.com on 8333 if it's forwarded, and identify using its bitcoind username and password.
2. Same as above, it uses the JSONRPC, so the bitcoind server you connect to is responsible for the wallet.
After seeing this, I must say I would really like to have a look at this.
Since parts of the code could even be used as a codebase for other implementations, the less restrictive the license is (within your limits), the most people and projects will be able to reuse it for their own implementations. So Unlicense would fit into that criteria IMHO.
Watching this!
Since parts of the code could even be used as a codebase for other implementations, the less restrictive the license is (within your limits), the most people and projects will be able to reuse it for their own implementations. So Unlicense would fit into that criteria IMHO.
Watching this!
I'm planning on CC since that allows most things, but I have a new issue... I'm unsure what the licensing issues I'll have if I throw it under CC considering:
- Bootstrap is Apache v2
- and JSONRPC-PHP is GPL v2
Can anyone good with licenses explain to me whether I'm allowed to release my code under Creative Commons, and whatever steps I have to do to ensure I'm not breaking their licenses?
Some quick questions:
Appart from that, cool project even if you use it on your local machine with XAMPP (or linux)
- Does the bitcoind need to run on the same server as the php files?
- Does the wallet need to be in the same place?
Appart from that, cool project even if you use it on your local machine with XAMPP (or linux)
After seeing this, I must say I would really like to have a look at this.
Since parts of the code could even be used as a codebase for other implementations, the less restrictive the license is (within your limits), the most people and projects will be able to reuse it for their own implementations. So Unlicense would fit into that criteria IMHO.
Watching this!
Since parts of the code could even be used as a codebase for other implementations, the less restrictive the license is (within your limits), the most people and projects will be able to reuse it for their own implementations. So Unlicense would fit into that criteria IMHO.
Watching this!
good job, do you have any experience with ruby on rails, im about to deploy a beta version of and app today and i would like to have you on the team.
No not really, though I could probably pick up ruby quite easily if I needed to...I'm mostly just PHP.
good job, do you have any experience with ruby on rails, im about to deploy a beta version of and app today and i would like to have you on the team.
uhh, how secure is it?
Not very.Throw on apache Auth-Basic though, and it should be good enough, plus if you hide it in /derpy/derpy/derpy/nobody/will/ever/guess/ on your web server, it's unlikely someone would stumble upon it
If you had fail2ban, auth-basic would be good enough since they get an IP ban after 3 attempts anyway.
uhh, how secure is it?
I've been working on the +Coin webUI for a while, my main purpose was originally for a namecoin management system, though I lacked time and effort for it, eventually I needed a webUI for bitcoind due to bitcoin-qt's instability while using p2pool (0.5.2), so I continued my work on it.
(Psst. If you submit a pull request and accept it, you'll get some BTC if your github is linked to tip4commit)
So far, it currently has the following features working:
OLD VERSION: http://i55.tinypic.com/24mc1go.png
CURRENT VERSION:
Version 0.01 Alpha - Released under UNLICENSE (public domain) and is available on my Github: https://github.com/Someguy123/-Coin
(Psst. If you submit a pull request and accept it, you'll get some BTC if your github is linked to tip4commit)
So far, it currently has the following features working:
- Listing transactions
- Sending coins
- Compatibility with any *coind that uses the bitcoinRPC (inc. Litecoin, Namecoin, Feathercoin)
- In standard PHP, so it's easy to deploy onto a normal webserver (Great for managing coind's on your VPS/Dedi)
- Colour coded send/recieves, and colour coded confirmations
- A really nice bootstrap interface
- The ability to list how much BTC/whatever is in an account, and then to list the addresses contained in the account.
- Able to display confirmed/unconfirmed balance (All transactions are "confirmed" at 6 in +Coin, including generated ones. I haven't bothered to separate it yet.)
OLD VERSION: http://i55.tinypic.com/24mc1go.png
CURRENT VERSION:
Version 0.01 Alpha - Released under UNLICENSE (public domain) and is available on my Github: https://github.com/Someguy123/-Coin
Jump to: