From: Tamas Blummer <tamas.blummer@gmail•com>
To: Gregory Maxwell <greg@xiph•org>
Cc: Jim Posen <jimpo@coinbase•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Interrogating a BIP157 server, BIP158 change proposal
Date: Wed, 6 Feb 2019 19:48:09 +0000 [thread overview]
Message-ID: <CAGc5dgbm0wQKs4bAyN8bPdqq=RbS--TvcvUOmX2_rMTCx0POAg@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgRY-EaPMORjipJuysi-z61VUMivOKmSeO1Rv7vXOPeLKQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
I do not think this ad hominem attack of you on me was justified.
I wrote code, gathered and shared data now and back in 2018. I showed
understanding of non technical issues. Is there an actual action that
defies my observation that a commitment is not yet in sight?
Is there anything technically wrong in what I wrote?
If not you should stop.
Tamas Blummer
On Wed, 6 Feb 2019, 18:17 Gregory Maxwell <greg@xiph•org wrote:
> On Wed, Feb 6, 2019 at 8:10 AM Tamas Blummer <tamas.blummer@gmail•com>
> wrote:
> > I am skeptical that commitment of any filter will come into Core soon.
> [...] A committed filter makes light clients much more reliable and
> attractive, for some taste too much more.
>
> You keep repeating this smear. Please stop.
>
> If you would actually bother reading the threads where this was
> discussed previously you will see that there was significant interest
> from bitcoin developers to eventually commit an output filter, and a
> significant investment of effort in improving the proposal to that
> end. It is really disheartening to see you continue to repeat your
> negative assumptions about other people's wishes when you haven't even
> invested the time required to read their words.
>
[-- Attachment #2: Type: text/html, Size: 1782 bytes --]
next prev parent reply other threads:[~2019-02-06 19:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 11:41 Tamas Blummer
2019-02-04 20:18 ` Jim Posen
2019-02-04 20:59 ` Tamas Blummer
2019-02-05 1:42 ` Olaoluwa Osuntokun
2019-02-05 12:21 ` Matt Corallo
2019-02-06 0:05 ` Olaoluwa Osuntokun
2019-02-05 20:10 ` Tamas Blummer
2019-02-06 0:17 ` Olaoluwa Osuntokun
2019-02-06 8:09 ` Tamas Blummer
2019-02-06 18:17 ` Gregory Maxwell
2019-02-06 19:48 ` Tamas Blummer [this message]
[not found] ` <CAAS2fgQX_02_Uwu0hCu91N_11N4C4Scm2FbAXQ-0YibroeqMYg@mail.gmail.com>
2019-02-06 21:17 ` Tamas Blummer
2019-02-07 20:36 ` Pieter Wuille
2021-10-03 9:53 ` Dustin Dettmer
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='CAGc5dgbm0wQKs4bAyN8bPdqq=RbS--TvcvUOmX2_rMTCx0POAg@mail.gmail.com' \
--to=tamas.blummer@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=greg@xiph$(echo .)org \
--cc=jimpo@coinbase$(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