From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists.linuxfoundation.org (Postfix) with ESMTP id 33AA9C002F for ; Fri, 21 Jan 2022 14:36:23 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 2288F416C9 for ; Fri, 21 Jan 2022 14:36:23 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp4.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 90GQUsONrlj5 for ; Fri, 21 Jan 2022 14:36:22 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) by smtp4.osuosl.org (Postfix) with ESMTPS id EDA804164B for ; Fri, 21 Jan 2022 14:36:21 +0000 (UTC) Received: by mail-io1-xd2a.google.com with SMTP id z19so11025917ioj.1 for ; Fri, 21 Jan 2022 06:36:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gIJAKRbJ3lEkaLZGrQYIaQkeVBVtJYCpvTlsuh4+E+Y=; b=KGNR1qn0wr4jlXyOgBS+lq0OLHPx3iVGHfVlA+uXlPVj8JlDpjkyT9d+XdZPHAdmjK Lb8fuGCvphjjboIohwif0J4hiTqHLjTSWDg3yjMXZBbKLm9Cxt8qGgF18XrCls/8MiCz AXQx6xV72+wkl7FJcAVkcev5I+Cn06o075iaPZPLVUGKGKOfhka+nA/F+ezguPjkYEjx rj+mEftoI4o92TfqRjckPrhIkHvMjNhiexEk+uR8IZAQIzjN+skZZ8819zoxaAqlFUEk ZJJ2lL8r530mh9zdQnFJIl29BrublAXw85JLF+aS/txceKEEN+Xrte1rQfRnzuhjcYj0 FazA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gIJAKRbJ3lEkaLZGrQYIaQkeVBVtJYCpvTlsuh4+E+Y=; b=YaaH1B1sJXRoMS6QDLO6E8nsn8UZeHL4xw3H2rzFrcEtC8snPEVizFch+RPgcWxhsa gwzdzp+It9GShNmHvlwOKHoY0+ycqHP8neo6SVFv/3WLRHT7vMdOgPIJ4xE3pX0UF2Ay Ilp3j1GEmpkzMSNXEQcBgq+UfLgXZboUyx6sep4I9yx12nXqu9P1S58HiEwF8zWJ3y0Z Pmmk8nCD1nnfsm+UR6ld3zgTkVOwX2sffgjvC4NaB1ctrp3y68GjH8+3keXatiF/IXbX P1dKgMs8hNtUs3vKUFpEE/rX0ZPAYaNlPuwm1r1/oeG3bcKtdmQYk7vAWZPZbPg08g0v KNLw== X-Gm-Message-State: AOAM531k0f7luhHxpFJL04yPpWEW/6ELaQ71HvAsHCSuqY7NKTGY4/Aq gaWn4qbGLqrIF+E0vjra3K7xGGB6TDD05rIRxAtaD+Fa X-Google-Smtp-Source: ABdhPJztd2KN1pme68URKt9nqQqN7iULS7TKrgrGhH8VMd241tf1vv+YKtLfaCT0BJMufbB/pnDycU0M96X8fO2n78Q= X-Received: by 2002:a02:cc24:: with SMTP id o4mr1745307jap.136.1642775780717; Fri, 21 Jan 2022 06:36:20 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Zac Greenwood Date: Fri, 21 Jan 2022 15:36:10 +0100 Message-ID: To: Bitcoin Protocol Discussion , jack Content-Type: multipart/alternative; boundary="000000000000daf98505d6188a18" X-Mailman-Approved-At: Fri, 21 Jan 2022 15:51:44 +0000 Cc: Prayank , info@bitcoindefensefund.org Subject: Re: [bitcoin-dev] Bitcoin Legal Defense Fund X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2022 14:36:23 -0000 --000000000000daf98505d6188a18 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable The name of the fund should ideally unambiguously clarify its scope, i.e., Bitcoin & development. So maybe =E2=80=9CBitcoin Developers Community LDF= =E2=80=9D. Or perhaps =E2=80=9CBitcoin Technical Community LDF=E2=80=9D which nicely abbr= eviates to BTCLDF. Zac On Thu, 13 Jan 2022 at 19:49, jack via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > Hi Prayank, > > > On 13 Jan 2022, at 10:13, Prayank wrote: > > I had few suggestions and feel free to ignore them if they do not make > sense: > > > > 1.Name of this fund could be anything and 'The Bitcoin Legal Defense > Fund' can be confusing or misleading for newbies. There is nothing offici= al > in Bitcoin however people believe things written in news articles and som= e > of them might consider it as an official bitcoin legal fund. > > Excellent point. Will come up with a better name. > > Open to ideas and suggestions on all. > > jack > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --000000000000daf98505d6188a18 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The name of the fund should ideally unambiguously clarify= its scope, i.e., Bitcoin & development. So maybe =E2=80=9CBitcoin Deve= lopers Community LDF=E2=80=9D. Or perhaps =E2=80=9CBitcoin Technical Commun= ity LDF=E2=80=9D which nicely abbreviates to BTCLDF.

Zac


=
On Thu, 13= Jan 2022 at 19:49, jack via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wr= ote:
Hi Prayank,

> On 13 Jan 2022, at 10:13, Prayank <prayank@tutanota.de> wrote:
> I had few suggestions and feel free to ignore them if they do not make= sense:
>
> 1.Name of this fund could be anything and 'The Bitcoin Legal Defen= se Fund' can be confusing or misleading for newbies. There is nothing o= fficial in Bitcoin however people believe things written in news articles a= nd some of them might consider it as an official bitcoin legal fund.

Excellent point. Will come up with a better name.

Open to ideas and suggestions on all.

jack
_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--000000000000daf98505d6188a18--