From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Wang Jian <larkwang@gmail.com>
Cc: "Dmitry Vyukov" <dvyukov@google.com>,
"WireGuard mailing list" <wireguard@lists.zx2c4.com>,
"Marek Küthe" <m.k@mk16.de>
Subject: Re: WireGuard Mailling List
Date: Sun, 23 Jul 2023 18:00:00 +0200 [thread overview]
Message-ID: <CAHmME9rzmyZzAETFGm7NGZ9FBhgSueskgmUD7Q17SOSe=zXtzA@mail.gmail.com> (raw)
In-Reply-To: <CAF75rJA4ev7f9L4qm4LgKAe2xS5vyb7z=vrDq0RN_WXbOX_0kw@mail.gmail.com>
On 7/23/23, Wang Jian <larkwang@gmail.com> wrote:
> Hi,
>
> I don't know the origin of the Wireguard logo, but it seems to be a 蛟
> (Jiao, pronounced j-ee-au), not a 龙 (Long)
>
> The differences between Long (know as Chinese dragon) and Jiao is
> * Jiao has 2 small straight horns or no horn at all while Long has 2 bigger
> and forky horns
> * Long has beard while Jiao has no beard
> * Jiao has snake like tail while Long has fish like tail (with round fin)
> * Long has 4 claws while Jiao has only 2 claws (foreclaws), but this
> feature
> is usually misused.
>
> Generally, Jiao is upgraded/developed snake living in rivers; Long is
> upgraded/developed Jiao living in the sea, and Long can fly into the sky.
>
> Of course you can call the logo wireguard dragon as you wish.
It is absolutely none of those things at all. Please stop speculating
and keep discussions on this here technical.
next prev parent reply other threads:[~2023-07-23 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230719091342.789107a9@parrot>
2023-07-19 7:18 ` Fwd: " Dmitry Vyukov
2023-07-23 15:31 ` Wang Jian
2023-07-23 16:00 ` Jason A. Donenfeld [this message]
2023-07-23 16:27 ` Laura Smith
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='CAHmME9rzmyZzAETFGm7NGZ9FBhgSueskgmUD7Q17SOSe=zXtzA@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=dvyukov@google.com \
--cc=larkwang@gmail.com \
--cc=m.k@mk16.de \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).