public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Ricardo Filipe <ricardojdfilipe@gmail•com>
To: Kevin <kevinsisco61784@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Okay, time to bring up bitcoin/bitcoin
Date: Wed, 2 Apr 2014 16:45:49 +0100	[thread overview]
Message-ID: <CALC81CN3cWa0OjTWueHKxZUDLZpw5n=qLNLxk8QmiSp4QwQyYA@mail.gmail.com> (raw)
In-Reply-To: <533C2D04.4090900@gmail.com>

Kevin,
the thing is you gave us a bad link... what is the correct URL of your project?

2014-04-02 16:30 GMT+01:00 Kevin <kevinsisco61784@gmail•com>:
> On 4/2/2014 11:13 AM, Laszlo Hanyecz wrote:
>> Maybe this site serves up exploits selectively?  I'm guessing most people are getting the 'domain for sale' but whoever is the target probably gets something special?
>>
>> On Apr 2, 2014, at 2:53 PM, Kevin <kevinsisco61784@gmail•com> wrote:
>>
>>> On 4/2/2014 9:08 AM, Jeff Garzik wrote:
>>>> At first, this is a poor choice of URL.
>>>>
>>>> But it really looks like a phishing attempt that no one should visit.
>>>>
>>>>
>>>> On Tue, Apr 1, 2014 at 4:00 PM, Kevin <kevinsisco61784@gmail•com> wrote:
>>>>> I've sat on this for some time after starting this.  I have forked this
>>>>> from bitcoin core and am working on a secure tax "mode" for bitcoin.  It
>>>>> is written in Autoit.  I know I know, scripting language alert!  I would
>>>>> like people to look at:
>>>>> http://www.githubb.com/bitcoin/bitcoin
>>>>> Look at it, and let's have an open dialog about it.  I want to know the
>>>>> good, the bad, and the ugly!
>>>>>
>>>>> --
>>>>> Kevin
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> _______________________________________________
>>>>> Bitcoin-development mailing list
>>>>> Bitcoin-development@lists•sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>>>
>>> As far as choice of U R L, it may be a poor choice but I did this
>>> because I wanted it connected with the core.  As far as fishing it
>>> certainly is not that!  This is a serious project.
>>>
>>>
>>> --
>>> Kevin
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Bitcoin-development mailing list
>>> Bitcoin-development@lists•sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> I tell you that this is a serious project for bitcoin.  You are free to
> assume the worst.  After all, I did say the good the bad and the ugly
> would come out of this.  I happen to be a big believer in bitcoin and I
> feel this project holds water.  If you disagree, that's fine.
>
>
> --
> Kevin
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development



  parent reply	other threads:[~2014-04-02 15:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 20:00 Kevin
2014-04-02 13:08 ` Jeff Garzik
2014-04-02 14:53   ` Kevin
2014-04-02 15:13     ` Laszlo Hanyecz
2014-04-02 15:30       ` Kevin
2014-04-02 15:41         ` Laszlo Hanyecz
2014-04-02 15:55           ` Justus Ranvier
2014-04-02 15:45         ` Ricardo Filipe [this message]
2014-04-02 15:59           ` Kevin
2014-04-02 16:45             ` Laszlo Hanyecz
2014-04-02 16:54               ` Kevin
2014-04-02 16:55               ` Jud
2014-04-02 16:57                 ` Kevin

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='CALC81CN3cWa0OjTWueHKxZUDLZpw5n=qLNLxk8QmiSp4QwQyYA@mail.gmail.com' \
    --to=ricardojdfilipe@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=kevinsisco61784@gmail$(echo .)com \
    /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