Closed GoogleCodeExporter closed 9 years ago
Sorry, I didn't know how to label this as a "feature request" and not a
"defect".
Original comment by Dustin.D...@gmail.com
on 20 Jul 2011 at 2:53
I'd like to see some solution to this problem as well. However, this must be
discussed much more widely (with the Satashi client developers for example). A
standard must be defined. I don't know much about the standard defining process
surrounding Bitcoin, but posting at forum.bitcoin.org may be a good start.
Original comment by andreas....@gmail.com
on 20 Jul 2011 at 3:47
Why not only share the mobile bitcoin address per intent so one can easily post
per mail/twitter/facebook and others
Original comment by lischke@gmail.com
on 26 Jul 2011 at 1:53
sorry i just found out how to do this. Just make a long tap on the address and
you can share it ;)
Original comment by lischke@gmail.com
on 26 Jul 2011 at 1:54
Yes, or press request coins and then press the share button.
Original comment by andreas....@gmail.com
on 26 Jul 2011 at 4:55
Request that you close this topic as it is solved.
Original comment by arcusiul...@gmail.com
on 21 Aug 2011 at 11:32
How is it solved? There still is no PC client available that can read or
generate QR codes, use NFC or even click bitcoin URIs.
Original comment by andreas....@gmail.com
on 22 Aug 2011 at 7:45
Oh... I thought it somehow got solved between 3-5. My bad.
Original comment by arcusiul...@gmail.com
on 25 Aug 2011 at 1:22
There is now a PC client that generates QR codes for its address:
http://multibit.org/
However, the issue of easily requesting coins from a PC client still remains.
Original comment by andreas....@gmail.com
on 13 Sep 2011 at 1:50
Isn't what you're asking for something that would be accomplished not in the
android app but on the PC side and therefore not a relevant post for this
project?
Original comment by voluntar...@gmail.com
on 4 May 2012 at 4:40
Ok, I'll close this for now. Needs to be implemented "other app"-side.
Original comment by andreas....@gmail.com
on 9 Jun 2012 at 8:36
Original issue reported on code.google.com by
Dustin.D...@gmail.com
on 20 Jul 2011 at 2:52