All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincas Dargis <vindrg@gmail.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] userspace: audit: ausearch doesn't return entries for AppArmor events that exist in the log
Date: Fri, 29 Apr 2016 19:58:46 +0300	[thread overview]
Message-ID: <572392C6.10302@gmail.com> (raw)
In-Reply-To: <20160429154131.GB18488@madcap2.tricolour.ca>

2016.04.29 18:41, Richard Guy Briggs rašė:
> You are welcome to your rant.  I quite like mailing lists and IRC.  I
> hate most other social media and forums.  What do you suggest instead?

Hi,

I guess it's plain personal preference, but I just get annoyed once I have to deal with lists. That's why:

1. No explicit search function. Yes I know (_now_) that you can use your search engine with site: prefix, but that's too 
"hidden" feature, and one have to "know" that from somewhere. I don't know why Mailman or (whatever that list engine is) 
couldn't have at least search box that redirects to some search engine, if they don't want to incorporate local search 
engine by themselves.

2. No (easy?) way to continue thread if not subscribed earlier. Debian bug tracker, that is based on email, does in fact 
has "mbox" download link for specific post. But that's rarity I guess. In forums you just click "reply" button. In list, 
you have to download .gz archive (which apparently failed in my latest Firefox 46 case) and edit it to make single .mbox 
or whatever? ...

Steve suggested just to start new thread. Yeah, but.. that's kinda cheating, and issue still exists and I guess I am 
(too) picky for these kind of usability "papprecuts", hence, the rant :-) .

3. Once subscribed, you may get lot's of lot's of emails, even if you are interested in only that single topic (or some 
topics, maybe started long time ago), so you can just "lose"/forget/skip relevant reply. Meanwhile, forums have 
notification function you cane enable for topics you are "watching".

4. No formatting options. It's sometimes hard to read code or other technical text embedded inside plain text email. 
Meanwhile, using markdown/bbcode/whatever you can make technical keywords, file paths, or whole code blocks distinct 
from plain text. Makes eyes happy.

Forums also have issues, like.. having gazillion of accounts (that simple email activation in lists makes it much easier 
actually). Also, I imagine getting all list traffic by default might be good for maintainers who want to hear (ok, read) 
all relevant issues. In forums, you should click-through all "highlighted" topics manually? Oh my...

Anyway, this off-topic should be in Mailman list probably :-) . All these are actually small, "bells-and-wistles", 
"pappercut" issues I guess, but that's enough to make me *sigh* when I see I will have to deal with mailing list instead 
of full-fledged bug tracker or at least a forum.

--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit

  reply	other threads:[~2016-04-29 16:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29  7:03 [PATCH] userspace: audit: ausearch doesn't return entries for AppArmor events that exist in the log Vincas Dargis
2016-04-29 13:39 ` Steve Grubb
2016-04-29 16:07   ` Vincas Dargis
2016-04-29 16:30     ` Steve Grubb
2016-05-02 21:18       ` Paul Moore
2016-04-29 15:41 ` Richard Guy Briggs
2016-04-29 16:58   ` Vincas Dargis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-28 22:33 Tony Jones
2014-05-29  8:31 ` Tyler Hicks
2014-05-29 15:01   ` Steve Grubb
2014-05-29 15:15     ` Tyler Hicks
2014-06-03  1:00   ` Tony Jones
2014-06-03 14:47     ` Steve Grubb
2014-06-03 16:34       ` Tony Jones
2014-05-29 15:21 ` Tyler Hicks
2014-05-30 19:53 ` Steve Grubb
2014-05-30 20:16   ` Tyler Hicks
2014-05-30 21:00     ` Steve Grubb
2014-05-31  0:01       ` Tony Jones
2014-06-06 18:46       ` Tyler Hicks
2014-06-06 21:10         ` Tyler Hicks
2014-06-24  0:06           ` Tony Jones
2014-06-24 15:34             ` Eric Paris

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=572392C6.10302@gmail.com \
    --to=vindrg@gmail.com \
    --cc=linux-audit@redhat.com \
    --cc=rgb@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.