From: "Jorge Timón" <timon.elviejo@gmail•com>
To: Andreas Schildbach <andreas@schildbach•de>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin Wallet for Android
Date: Mon, 9 Jul 2012 13:34:10 +0200 [thread overview]
Message-ID: <CAGQP0AGG9Wrx0CDQQVwpCovovDV072Cr9rrLhUHuBgb4kNr+XA@mail.gmail.com> (raw)
In-Reply-To: <jtedbo$271$1@dough.gmane.org>
Didn't even know that they were proprietary software bitcoin clients.
Should people trust them? Should the web promote them?
After all, you can't know what they do. What if one of them contains a
back door or something?
I would say it's better not risk to apologize later.
On 7/9/12, Andreas Schildbach <andreas@schildbach•de> wrote:
> I'd suggest adding two links for each client.
>
> One for getting the binary, and one for getting the source. (Obviously,
> source being optional if you allow non-opensource clients.)
>
>
> On 07/09/2012 12:44 PM, Amir Taaki wrote:
>> OK thanks. I just went and made those sections then saw your posts.
>>
>> Anyway we have a section for proprietary clients now. Please tell me if
>> anything looks disagreeable, http://bitcoin.org/clients.html
>>
>> One thing I'm going to do is randomise the positioning order within
>> sections upon refresh.
>>
>>
>>
>> ----- Original Message -----
>> From: "mats@henricson•se" <mats@henricson•se>
>> To: bitcoin-development@lists•sourceforge.net
>> Cc:
>> Sent: Monday, July 9, 2012 11:19 AM
>> Subject: Re: [Bitcoin-development] Bitcoin Wallet for Android
>>
>> Sources are available here:
>>
>> http://code.google.com/p/bitcoin-wallet/
>>
>> Mats
>>
>> Quoting Amir Taaki <zgenjix@yahoo•com>:
>>
>>> Hey,
>>>
>>> I just saw this added to the clients page. One of the conditions we
>>> set for that page was that all the clients must have the entire
>>> sourcecode available for review, and users should be able to run it
>>> from the sourcecode. Is the sourcecode for this client available for
>>> review? I couldn't find it.
>>>
>>> Otherwise, we should make a separate section for non-opensource clients.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond.
>>> Discussions
>>> will include endpoint security, mobile security and the latest in
>>> malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Bitcoin-development mailing list
>>> Bitcoin-development@lists•sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>>
>> will include endpoint security, mobile security and the latest in malware
>>
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists•sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>>
>> will include endpoint security, mobile security and the latest in malware
>>
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--
Jorge Timón
next prev parent reply other threads:[~2012-07-09 11:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 9:21 Amir Taaki
2012-07-09 9:36 ` Harald Schilly
2012-07-09 10:19 ` mats
2012-07-09 10:44 ` Amir Taaki
2012-07-09 10:55 ` Andreas Schildbach
2012-07-09 11:34 ` Jorge Timón [this message]
2012-07-09 13:11 ` slush
2012-07-09 13:46 ` Gregory Maxwell
2012-07-09 14:00 ` Gregory Maxwell
2012-07-09 14:12 ` Ben Reeves
2012-07-09 14:12 ` Gregory Maxwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGQP0AGG9Wrx0CDQQVwpCovovDV072Cr9rrLhUHuBgb4kNr+XA@mail.gmail.com \
--to=timon.elviejo@gmail$(echo .)com \
--cc=andreas@schildbach$(echo .)de \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox