public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
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
Date: Sun, 24 Dec 2023 15:43:00 +0700	[thread overview]
Message-ID: <ZYfvFAwXOiKBOgw2@archie.me> (raw)
In-Reply-To: <20231223004235.GC325499@mit.edu>

[-- Attachment #1: Type: text/plain, Size: 2073 bytes --]

On Fri, Dec 22, 2023 at 07:42:35PM -0500, Theodore Ts'o wrote:
> 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....

Ted, thanks for the explanation!

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2023-12-24  8:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21 11:15 "Link in bio" instead of Link:/Closes: trailer Bagas Sanjaya
2023-12-21 11:51 ` Greg Kroah-Hartman
2023-12-21 12:57   ` Bagas Sanjaya
2023-12-21 13:10     ` Greg Kroah-Hartman
2023-12-21 14:13       ` Bagas Sanjaya
2023-12-23  0:42         ` Theodore Ts'o
2023-12-24  8:43           ` Bagas Sanjaya [this message]

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=ZYfvFAwXOiKBOgw2@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=tytso@mit.edu \
    /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