lore.kernel.org upgrade: Sep 1, 2021

Hi, all:

My tests of the new lore.kernel.org service (currently running on
x-lore.kernel.org) are looking good, so I will be putting that into production
on Wednesday, September 1, 2021.

If you're using b4, there will be a version 0.8.0 released on that date as
well, which works better with upstream lore.k.o. changes. Previous version of
b4 will continue to work, but some functionality may be impacted, so everyone
is encouraged to upgrade to 0.8 once it becomes available.

Best regards,
-Konstantin

On Mon, Aug 30, 2021 at 11:46 AM Konstantin Ryabitsev
[off-list ref] wrote:

Hi, all:

My tests of the new lore.kernel.org service (currently running on
x-lore.kernel.org) are looking good, so I will be putting that into production
on Wednesday, September 1, 2021.

One thing I've noticed doing some searches[1] is I get a bunch of hits
on post-receive-hook mails dominating the results which doesn't seem
too useful. Do those need to be in the 'all' index? The purpose of
them is pretty orthogonal to development patches and discussions. Or
is it possible to have an 'almost-all' index? Or other flavors of
indexes in general? Perhaps a patches only index for example (the best
I found for a query is 'dfn:/', but that has some false positives).

There's also a ton of stable review patches, but that's not a new
thing as those are cross posted. While I can filter both of those
out[2], having to do that doesn't seem like the greatest default
behaviour.

Rob

[1] https://x-lore.kernel.org/all/?q=rseq+arm64+perf
[2] https://x-lore.kernel.org/all/?q=rseq+arm64+perf+-l%3Astable+-f%3Adevnull%40kernel.org

On Mon, Aug 30, 2021 at 12:47:33PM -0500, Rob Herring wrote:

quoted

My tests of the new lore.kernel.org service (currently running on
x-lore.kernel.org) are looking good, so I will be putting that into production
on Wednesday, September 1, 2021.

One thing I've noticed doing some searches[1] is I get a bunch of hits
on post-receive-hook mails dominating the results which doesn't seem
too useful. Do those need to be in the 'all' index? The purpose of
them is pretty orthogonal to development patches and discussions. Or
is it possible to have an 'almost-all' index? Or other flavors of
indexes in general? Perhaps a patches only index for example (the best
I found for a query is 'dfn:/', but that has some false positives).

I do agree that adding the gitolite feed there was a bad choice -- I'll
probably eject it from lore and let it just live on git.kernel.org.

Regarding custom combined indexes, this is something that I will be
working on in the near future. One of the new features in public-inbox is the
"lei" (local email interface) command, which lets you collect email from
multiple sources (your local inbox, lore.kernel.org feeds, nntp group, an imap
connection, etc) based on specific search criteria. I've not yet decided how
we're going to provide this for others, but the goal is to make it easy for
maintainers to define their own custom feeds and share it with co-maintainers
(or anyone else). Once I have a clearer picture on how I want to go ahead,
I'll follow up with others here.

-K

On Mon, Aug 30, 2021 at 12:46:26PM -0400, Konstantin Ryabitsev wrote:

Hi, all:

My tests of the new lore.kernel.org service (currently running on
x-lore.kernel.org) are looking good, so I will be putting that into production
on Wednesday, September 1, 2021.

Any chance I could persuade you to remove the color changes in the CSS
stylesheet?  The text colors on the new x-lore appear washed out to me
due to "color: #333;", which makes it harder to read.

I can hack around all that stylistic choice by adding more rules to my
bespoke browser extension that makes the web readable again for my old
eyes, but I'd prefer the current lore's stylesheet, which uses the user
agent's preferences.

Something like this, perhaps?

--D

css: use the user agent's text colors

Despite the comment for the color scheme claiming that "...bright colors
hurt my eyes", gray text on white strains /my/ old eyes because of the
unnecessarily low contrast.

Just use the user agent's text color, because users know best.

Signed-off-by: Darrick J. Wong <djwong@kernel.org>
---
 contrib/css/216light.css | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/contrib/css/216light.css b/contrib/css/216light.css
index 741214c..9abdd16 100644
--- a/contrib/css/216light.css
+++ b/contrib/css/216light.css

@@ -4,7 +4,7 @@
  * Suitable for print, and blinding people with brightness.
  * Haphazardly thrown together because bright colors hurt my eyes
  */
-* { font-size: 100%; font-family: monospace; background:#fff; color:#333 }
+* { font-size: 100%; font-family: monospace; background:#fff; }
 pre { white-space: pre-wrap }
 
 /*

-- 
2.25.1

On August 31, 2021 6:23:10 PM PDT, "Darrick J. Wong" [off-list ref] wrote:

On Mon, Aug 30, 2021 at 12:46:26PM -0400, Konstantin Ryabitsev wrote:

quoted

Hi, all:

My tests of the new lore.kernel.org service (currently running on
x-lore.kernel.org) are looking good, so I will be putting that into production
on Wednesday, September 1, 2021.

Any chance I could persuade you to remove the color changes in the CSS
stylesheet?  The text colors on the new x-lore appear washed out to me
due to "color: #333;", which makes it harder to read.

I can hack around all that stylistic choice by adding more rules to my
bespoke browser extension that makes the web readable again for my old
eyes, but I'd prefer the current lore's stylesheet, which uses the user
agent's preferences.

Something like this, perhaps?

While I entirely agree about the merits of higher contrast, I think the classic https://www.w3.org/QA/Tips/color (If You Pick One Color, Pick Them All) applies here. If we want to respect the user's color preferences, we shouldn't set the background color either.

It's difficult to both do that and provide color themes though, especially for a static generated site.

On 2021-08-30 12:46:26 [-0400], Konstantin Ryabitsev wrote:

Hi, all:

Hi,

My tests of the new lore.kernel.org service (currently running on
x-lore.kernel.org) are looking good, so I will be putting that into production
on Wednesday, September 1, 2021.

x-lore misses a hostname in its cert:

| This server could not prove that it is lkml.kernel.org; its security
| certificate is from ams.source.kernel.org. This may be caused by a
| misconfiguration or an attacker intercepting your connection.

Best regards,
-Konstantin

Sebastian

On Wed, Sep 01, 2021 at 03:12:59PM +0200, Sebastian Andrzej Siewior wrote:

On 2021-08-30 12:46:26 [-0400], Konstantin Ryabitsev wrote:

quoted

Hi, all:

Hi,

quoted

My tests of the new lore.kernel.org service (currently running on
x-lore.kernel.org) are looking good, so I will be putting that into production
on Wednesday, September 1, 2021.

x-lore misses a hostname in its cert:

| This server could not prove that it is lkml.kernel.org; its security
| certificate is from ams.source.kernel.org. This may be caused by a
| misconfiguration or an attacker intercepting your connection.

Thank you for the alert -- looks like my deploy missed a step. It should fix
itself once DNS entries propagate to you.

-K

On Tue, Aug 31, 2021 at 06:23:10PM -0700, Darrick J. Wong wrote:

On Mon, Aug 30, 2021 at 12:46:26PM -0400, Konstantin Ryabitsev wrote:

quoted

Hi, all:

My tests of the new lore.kernel.org service (currently running on
x-lore.kernel.org) are looking good, so I will be putting that into production
on Wednesday, September 1, 2021.

Any chance I could persuade you to remove the color changes in the CSS
stylesheet?  The text colors on the new x-lore appear washed out to me
due to "color: #333;", which makes it harder to read.

Folks, I am just using upstream CSS choices. We cannot both provide diff
colours and not offer some kind of base foreground/background colour defaults,
because this is how we'll end up with dark blue on black.

There are multiple ways to tweak how the site looks -- both via a custom css
stylesheet (see the "color" link) and the "reader view" in Firefox, which is
my preferred go-to.

-K

On Mon, Aug 30, 2021 at 12:46:26PM -0400, Konstantin Ryabitsev wrote:

Hi, all:

My tests of the new lore.kernel.org service (currently running on
x-lore.kernel.org) are looking good, so I will be putting that into production
on Wednesday, September 1, 2021.

It appears that lore.kernel.org/patchwork is gone. Is that on purpose,
and/or is there a new link ?

Thanks,
Guenter

On Thu, Sep 02, 2021 at 11:45:43AM -0700, Guenter Roeck wrote:

quoted

My tests of the new lore.kernel.org service (currently running on
x-lore.kernel.org) are looking good, so I will be putting that into production
on Wednesday, September 1, 2021.

It appears that lore.kernel.org/patchwork is gone. Is that on purpose,
and/or is there a new link ?

It's gone forever, see this PSA, which was also sent to this list.
https://lore.kernel.org/all/20210820171633.43xhblvzuk4swxln@nitro.local/

-K

On 9/2/21 11:56 AM, Konstantin Ryabitsev wrote:

On Thu, Sep 02, 2021 at 11:45:43AM -0700, Guenter Roeck wrote:

quoted

quoted

My tests of the new lore.kernel.org service (currently running on
x-lore.kernel.org) are looking good, so I will be putting that into production
on Wednesday, September 1, 2021.

It appears that lore.kernel.org/patchwork is gone. Is that on purpose,
and/or is there a new link ?

It's gone forever, see this PSA, which was also sent to this list.
https://lore.kernel.org/all/20210820171633.43xhblvzuk4swxln@nitro.local/

Yes, I noticed later. Sorry for the noise.

Thanks,
Guenter

Hi Konstantin,

Would it be possible to get a search box on the front page into which you can
just drop a message ID and have it jump to the message, if present, kind of
like lore.kernel.org/r/<msg-id> does?

Thanks,
David

On Thu, Sep 09, 2021 at 10:58:52AM +0100, David Howells wrote:

Would it be possible to get a search box on the front page into which you can
just drop a message ID and have it jump to the message, if present, kind of
like lore.kernel.org/r/<msg-id> does?

You can make it even easier.

In Firefox:

    * open bookmarks pane (Ctrl-b)
    * right-click->add bookmark
    * Name: lore mid, URL: https://lore.kernel.org/%s, Keyword: lore -> Save

In Chrome:

    * Go to chrome://settings/searchEngines
    * Click "Add" next to "Other search engines"
    * Search engine: lore mid, Keyword: lore, URL: https://lore.kernel.org/%s -> Add

Now you can type "lore <message-id>" in the toolbar.

-K

On Thu, 9 Sep 2021 08:31:50 -0400
Konstantin Ryabitsev [off-list ref] wrote:

On Thu, Sep 09, 2021 at 10:58:52AM +0100, David Howells wrote:

quoted

Would it be possible to get a search box on the front page into which you can
just drop a message ID and have it jump to the message, if present, kind of
like lore.kernel.org/r/<msg-id> does?  

You can make it even easier.

In Firefox:

    * open bookmarks pane (Ctrl-b)
    * right-click->add bookmark
    * Name: lore mid, URL: https://lore.kernel.org/%s, Keyword: lore -> Save

In Chrome:

    * Go to chrome://settings/searchEngines
    * Click "Add" next to "Other search engines"
    * Search engine: lore mid, Keyword: lore, URL: https://lore.kernel.org/%s -> Add

Now you can type "lore <message-id>" in the toolbar.

Thanks for the tip! I'll add this.

I also make all my email clients show Message-ID by default.

-- Steve

Hi Konstantin,

On Thu, Sep 9, 2021 at 2:31 PM Konstantin Ryabitsev
[off-list ref] wrote:

On Thu, Sep 09, 2021 at 10:58:52AM +0100, David Howells wrote:

quoted

Would it be possible to get a search box on the front page into which you can
just drop a message ID and have it jump to the message, if present, kind of
like lore.kernel.org/r/<msg-id> does?

You can make it even easier.

In Chrome:

    * Go to chrome://settings/searchEngines
    * Click "Add" next to "Other search engines"
    * Search engine: lore mid, Keyword: lore, URL: https://lore.kernel.org/%s -> Add

Now you can type "lore <message-id>" in the toolbar.

Neat, thanks a lot!

And if you make it the default search engine, you can select "Show
original" in Gmail, select the Message-ID, and right-click to
search. No more copy-and-paste needed.

Unfortunately that means right-click to search for other topics doesn't
work anymore. Perhaps lore can redirect to Google if no results were
found? ;-)

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Konstantin Ryabitsev [off-list ref] wrote:

You can make it even easier.

In Firefox:

    * open bookmarks pane (Ctrl-b)
    * right-click->add bookmark
    * Name: lore mid, URL: https://lore.kernel.org/%s, Keyword: lore -> Save

In Chrome:

    * Go to chrome://settings/searchEngines
    * Click "Add" next to "Other search engines"
    * Search engine: lore mid, Keyword: lore, URL: https://lore.kernel.org/%s -> Add

Now you can type "lore <message-id>" in the toolbar.

Cute... but IMO, that's not actually easier than just clicking on the lore
item in the bookmark strip, then pasting the message ID in the box and hitting
go.  Is it possible to add a separate lore-search box, I wonder?  I search
lore a lot.

You also have to strip the <...> yourself rather than lore doing it as it does
when you paste into the search box on the per-archive pages.

Actually, I guess I can just click on the "all" archive and do it there.

Btw, is there some ordering on the list of archives on the front page?  I'm
guessing it's in order of most recent addition.  Wouldn't alphabetic order be
more useful?

David

On Thu, Sep 09, 2021 at 02:54:08PM +0100, David Howells wrote:

Cute... but IMO, that's not actually easier than just clicking on the lore
item in the bookmark strip, then pasting the message ID in the box and hitting
go.  Is it possible to add a separate lore-search box, I wonder?  I search
lore a lot.

You can just bookmark https://lore.kernel.org/all/ and add it to your bookmark
bar for quick access.

Btw, is there some ordering on the list of archives on the front page?  I'm
guessing it's in order of most recent addition.  Wouldn't alphabetic order be
more useful?

I don't have an option to control this order right now -- this is just what
public-inbox chooses to do. I'm not sure alphabetic ordering would do much
difference, honestly. Just ctrl-f and start typing to find the link you want.

-K

On Thu, Sep 09, 2021 at 03:21:52PM +0200, Geert Uytterhoeven wrote:

And if you make it the default search engine, you can select "Show
original" in Gmail, select the Message-ID, and right-click to
search. No more copy-and-paste needed.

Unfortunately that means right-click to search for other topics doesn't
work anymore. Perhaps lore can redirect to Google if no results were
found? ;-)

That would mean that lore would have access to a large part of your
search stream.  Some might consider it to be privacy concern, unless
the LF wants to introduce a privacy policy promising they won't try to
monetize that as an income stream?  :-)

						- Ted

On Thu, Sep 09, 2021 at 10:33:30AM -0400, Theodore Ts'o wrote:

That would mean that lore would have access to a large part of your
search stream.  Some might consider it to be privacy concern, unless
the LF wants to introduce a privacy policy promising they won't try to
monetize that as an income stream?  :-)

!! Hot Seattle plumbers are eager to webcam with you, Ted !!

(literally true, sue me)

-K

On 2021-09-01 09:25:19 [-0400], Konstantin Ryabitsev wrote:

Thank you for the alert -- looks like my deploy missed a step. It should fix
itself once DNS entries propagate to you.

Thanks.
I've been just pointed to this behaviour:
  https://lore.kernel.org/netdev/

has a search field at the top. But if you use
  https://lkml.kernel.org/netdev/

then there is the archive with no search field. A redirect to lore would
be nice.

-K

Sebastian

On Wed, Sep 15, 2021 at 02:05:55PM +0200, Sebastian Andrzej Siewior wrote:

Thanks.
I've been just pointed to this behaviour:
  https://lore.kernel.org/netdev/

has a search field at the top. But if you use
  https://lkml.kernel.org/netdev/

then there is the archive with no search field. A redirect to lore would
be nice.

This distinction is intentional -- lkml.kernel.org is the primary system from
where lore.kernel.org nodes replicate. Being able to access lkml.kernel.org
without a redirect is a feature, so I can't easily fix this.

-K

On 2021-09-15 08:15:21 [-0400], Konstantin Ryabitsev wrote:

This distinction is intentional -- lkml.kernel.org is the primary system from
where lore.kernel.org nodes replicate. Being able to access lkml.kernel.org
without a redirect is a feature, so I can't easily fix this.

ah okay. Don't worry then. I assumed its purporse a redirect to lore.
Do you plan to point lkml.k.o to geo.source.k.o with a cert?

-K

Sebastian

On Wed, Sep 15, 2021 at 03:00:06PM +0200, Sebastian Andrzej Siewior wrote:

On 2021-09-15 08:15:21 [-0400], Konstantin Ryabitsev wrote:

quoted

This distinction is intentional -- lkml.kernel.org is the primary system from
where lore.kernel.org nodes replicate. Being able to access lkml.kernel.org
without a redirect is a feature, so I can't easily fix this.

ah okay. Don't worry then. I assumed its purporse a redirect to lore.
Do you plan to point lkml.k.o to geo.source.k.o with a cert?

No, the final configuration is in place. The only thing lkml.kernel.org should
really be used for is the lkml.kernel.org/r/<msgid> legacy redirect.
Otherwise, nobody should be using that hostname for any purpose.

-K