Received-SPF: pass (google.com: domain of linux-kernel+bounces-10155-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Date: Fri, 22 Dec 2023 19:42:35 -0500
From: "Theodore Ts'o" <tytso@mit.edu>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Jakub Kicinski <kuba@kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Staging Drivers <linux-staging@lists.linux.dev>
Subject: Re: "Link in bio" instead of Link:/Closes: trailer
Message-ID: <20231223004235.GC325499@mit.edu>
References: <ZYQeZjN_3bPOdKKf@archie.me>
 <2023122112-rigging-january-7618@gregkh>
 <cc276c0e-99bb-4422-9771-d864db4287cb@gmail.com>
 <2023122129-twisty-mumble-c667@gregkh>
 <ZYRIDDD_XR5HdVJu@archie.me>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ZYRIDDD_XR5HdVJu@archie.me>

On Thu, Dec 21, 2023 at 09:13:32PM +0700, Bagas Sanjaya wrote:
> I was scratching my itch whether common social media practices (such as that's
> being discussed here) can be applied to kernel development.

The real problem is that someone's soecial media profile (whether it's
Linkedin, or Facebook, or Threads, or Twitter) is not a stable, fixed
resource.  So at any time in the future, the bug report in the Social
media profile could get modified, or disappear when Elon Musk decides
to take a user's Twitter username[1] away so he can resell the highly
desireable account name to someone he likes better.  The git log is
forever.  So pointing to a transient resource from a permanent log is
a really, Really, REALLY bad idea.

[1] https://slate.com/technology/2023/08/x-twitter-usernames-music-take-away-interview.html

Common social media practices are often quite terrible, and this is a
great example about why they shouldn't be used for this purpose.  The
bug report should be sent to a linux kernel mailing list, so everyone
can see it, and then they can use a lore.kernel.org URL as the stable
resource.

If the bug report is in some other source where the people who run it
understand the importance of stable information at stable URL's ---
for example, bugzilla.kernel.org, bugzilla.redhat.com,
bugs.debian.org, etc. that's also fine.  But a social media profile,
which can be modified at the owner's whim (either of the social media
account, or the social media comapny, or someone who has $44 billion
dollars to carelessly throw around)?  That way lies madness.

Just because something might "common social media pracitce", doesn't
mean that it's a good idea.  In fact, some might argue that much of
what happens on social media has a negative value to society, but
that's a different debate....

Cheers,

					- Ted