I want to prevent RSLight from accepting or storing incoming articles
based on substrings in headers, especially "*google*" in "Path" and
"*G2*" in "User-Agent" headers. I want to refuse, nix, and be sure to
not store or forward anything matching patterns in article headers. What
would be a simple (preferably RSLight-native) way to do this? I want to
avoid industrial-strength tools like cleanfeed and friends if at all
possible.

Bonus gushing praise points shall be awarded for any method to do the
same for the whole spool for articles that have already been
synchronized and stored.

If there is not a simple way would anyone point me to the hard way?

--
SugarBug | https://sybershock.com | NNTP | Usenet | Forum
Fediverse | https://syfershock.com/users/syfershock
NightBulb | https://nightbulb.net | Flip the night switch.

Syber Shock wrote:

> I want to prevent RSLight from accepting or storing incoming articles
> based on substrings in headers, especially "*google*" in "Path" and
> "*G2*" in "User-Agent" headers. I want to refuse, nix, and be sure to
> not store or forward anything matching patterns in article headers. What
> would be a simple (preferably RSLight-native) way to do this? I want to
> avoid industrial-strength tools like cleanfeed and friends if at all
> possible.

That's something I've already started on. I should have something this weekend. I'll let you know when I think it's working. Just finishing up some theme stuff right now.

> Bonus gushing praise points shall be awarded for any method to do the
> same for the whole spool for articles that have already been
> synchronized and stored.

The "easiest" way is using NoCeM. If you are set up for that, I may already have the NoCeM messages you need to get it done.

> If there is not a simple way would anyone point me to the hard way?

The hard way requires a hammer, but it's almost guaranteed to remove anyone's ability to read pretty much anything from your computer.

--
Retro Guy

Retro Guy wrote:

> Syber Shock wrote:

>> I want to prevent RSLight from accepting or storing incoming articles
>> based on substrings in headers, especially "*google*" in "Path" and
>> "*G2*" in "User-Agent" headers. I want to refuse, nix, and be sure to
>> not store or forward anything matching patterns in article headers. What
>> would be a simple (preferably RSLight-native) way to do this? I want to
>> avoid industrial-strength tools like cleanfeed and friends if at all
>> possible.

> That's something I've already started on. I should have something this weekend. I'll let you know when I think it's working. Just finishing up some theme stuff right now.

Seems I have it working now. Simply, there will be a new config file in $config_dir named 'header_filters.conf'. Of course also some code changes (to newsportal.php and spoolnews.php)

For now, you can filter by Path, Message-ID, From and Subject. I can add more later if necessary. Here's a sample of the content of header_filters.conf:

From: /test-user@nospam.example/
Path: /groups.googlegroups.com!not-for-mail/

It should be pretty obvious, but it is the header name 'Path:' or whatever you're using, followed by a regex (including delimiters).

If you want to filter for more than one thing in the same header, add it to the regex as necessary, don't create a new line in the config file.

The above lines are just for my testing. The From: is just because this poster posts like every 3 minutes in alt.test, so it made it convenient for testing.

The second line 'Path: ' will filter any articles originating from google groups. I have a suspicion that this may be your intent :)

The changes to newsportal.php and spoolnews.php may be different, depending on if you have upgraded to the latest commit. Please let me know and we can go from there to get you running.

--
Retro Guy

Retro Guy wrote:

> Retro Guy wrote:

>> Syber Shock wrote:

>>> I want to prevent RSLight from accepting or storing incoming articles
>>> based on substrings in headers, especially "*google*" in "Path" and
>>> "*G2*" in "User-Agent" headers. I want to refuse, nix, and be sure to
>>> not store or forward anything matching patterns in article headers. What
>>> would be a simple (preferably RSLight-native) way to do this? I want to
>>> avoid industrial-strength tools like cleanfeed and friends if at all
>>> possible.

>> That's something I've already started on. I should have something this weekend. I'll let you know when I think it's working. Just finishing up some theme stuff right now.

> Seems I have it working now. Simply, there will be a new config file in $config_dir named 'header_filters.conf'. Of course also some code changes (to newsportal.php and spoolnews.php)

> For now, you can filter by Path, Message-ID, From and Subject. I can add more later if necessary. Here's a sample of the content of header_filters.conf:

> From: /test-user@nospam.example/
> Path: /groups.googlegroups.com!not-for-mail/

The '' to escape characters were stripped above. Don't forget to write a proper regex :)

--
Retro Guy

Retro Guy wrote:

> Retro Guy wrote:

>> Retro Guy wrote:

>>> Syber Shock wrote:

>>>> I want to prevent RSLight from accepting or storing incoming articles
>>>> based on substrings in headers, especially "*google*" in "Path" and
>>>> "*G2*" in "User-Agent" headers. I want to refuse, nix, and be sure to
>>>> not store or forward anything matching patterns in article headers. What
>>>> would be a simple (preferably RSLight-native) way to do this? I want to
>>>> avoid industrial-strength tools like cleanfeed and friends if at all
>>>> possible.

>>> That's something I've already started on. I should have something this weekend. I'll let you know when I think it's working. Just finishing up some theme stuff right now.

>> Seems I have it working now. Simply, there will be a new config file in $config_dir named 'header_filters.conf'. Of course also some code changes (to newsportal.php and spoolnews.php)

>> For now, you can filter by Path, Message-ID, From and Subject. I can add more later if necessary. Here's a sample of the content of header_filters.conf:

>> From: /test-user@nospam.example/
>> Path: /groups.googlegroups.com!not-for-mail/

> The '' to escape characters were stripped above. Don't forget to write a proper regex :)

Lol, I'm an idiot!

--
Retro Guy

On Sat, 16 Sep 2023 15:48:23 +0000
retro.guy@rocksolidbbs.com (Retro Guy) wrote:

> The second line 'Path: ' will filter any articles originating from
> google groups. I have a suspicion that this may be your intent :)

Clouds part; bright sunrays and butterflies and rose petals rain down.

You must have seen the thread I started in news.admin.net-abuse.usenet.

I'm going to get ready to migrate from my old rslight install in a few
days. I will do a fresh install, sync it up with my old server, then
config in your peer and a few others. If the sync rejects the google
spam then witness fist-pumping happy dance.

--
SugarBug | https://sybershock.com | NNTP | Usenet | Forum
Fediverse | https://syfershock.com/users/syfershock
NightBulb | https://nightbulb.net | Flip the night switch.

Syber Shock wrote:

> On Sat, 16 Sep 2023 15:48:23 +0000
> retro.guy@rocksolidbbs.com (Retro Guy) wrote:

>> The second line 'Path: ' will filter any articles originating from
>> google groups. I have a suspicion that this may be your intent :)

> Clouds part; bright sunrays and butterflies and rose petals rain down.

> You must have seen the thread I started in news.admin.net-abuse.usenet.

Yes, I've been following the discussion.

> I'm going to get ready to migrate from my old rslight install in a few
> days. I will do a fresh install, sync it up with my old server, then
> config in your peer and a few others. If the sync rejects the google
> spam then witness fist-pumping happy dance.

Sounds good. Please make sure to back up your theme, so you don't lose it on the install. It's a nice theme, I'd hate to see it disappear.

Again, please make sure to write the regex properly since it's missing the escape chars in my posted example, and that it requires the opening and closing delimiters in the .conf file ('/')

--
Retro Guy

On Sun, 17 Sep 2023 00:04:32 +0000
retro.guy@rocksolidbbs.com (Retro Guy) wrote:

> Sounds good. Please make sure to back up your theme, so you don't
> lose it on the install. It's a nice theme, I'd hate to see it
> disappear.

The theme is attached as a tar.xz archive.

In my version of the theme a few lines of the PHP files of an older
rslight version were modfied to nest the headers view inside the div
rather than as overlay. Other than that everything should be exactly
the same.

When you push out all your most recent changes I'll look at that. I
will try to alter the theme to work with your most recent code as is
without the PHP hacks. Then I'll push that your way.

--
SugarBug | https://sybershock.com | NNTP | Usenet | Forum
Fediverse | https://syfershock.com/users/syfershock
NightBulb | https://nightbulb.net | Flip the night switch.

Syber Shock wrote:

> On Sun, 17 Sep 2023 00:04:32 +0000
> retro.guy@rocksolidbbs.com (Retro Guy) wrote:

>> Sounds good. Please make sure to back up your theme, so you don't
>> lose it on the install. It's a nice theme, I'd hate to see it
>> disappear.

> The theme is attached as a tar.xz archive.

Thanks!

> In my version of the theme a few lines of the PHP files of an older
> rslight version were modfied to nest the headers view inside the div
> rather than as overlay. Other than that everything should be exactly
> the same.

The latest rslight has mods to header.php also.

--
Retro Guy

Syber Shock wrote:

> On Sun, 17 Sep 2023 00:04:32 +0000
> retro.guy@rocksolidbbs.com (Retro Guy) wrote:

>> Sounds good. Please make sure to back up your theme, so you don't
>> lose it on the install. It's a nice theme, I'd hate to see it
>> disappear.

> The theme is attached as a tar.xz archive.

> In my version of the theme a few lines of the PHP files of an older
> rslight version were modfied to nest the headers view inside the div
> rather than as overlay. Other than that everything should be exactly
> the same.

I have added TriMonoBlue theme to my sites, and will add to git soon.

Thanks SS, it's a very nice theme!

Since I'm adding to a newer version of rslight, I tried to match as best
I could, but it's not completely perfect. Groups are not right justified
at the top of the screen, and a few other things.

I'm running it as my default theme on one site so I hopefully will come
across issues myself as I browse.

Note, to change themes you need to log in. Then it's in your comfig. I may
add a drop down in the future that will store it in a cookie, but that doesn't
exist right now.

--
Retro Guy

I think this is my favourite theme right now! :)

--
Retro Guy

On Mon, 16 Oct 2023 18:26:23 +0000
retro.guy@rocksolidbbs.com (Retro Guy) wrote:

> I think this is my favourite theme right now! :)

Yeah, it's laid out like that at ye olde Syber Shock Shanty. We got you
covered like a jimmy hat.

I pushed some new 'latest' buttons so swapping colors is easy. Perhaps a
file selector in the engine or CSS URL property could switch between SVG
and PNG in themes based upon filename? The SVG files scale sharply. PNG
gets fuzzy scaling up if it is not a large image.

Maybe it would make sense to create some CSS3 shapes for the buttons so
the user can just change the colors in the theme CSS file. Then image
files wouldn't even be needed.

repo: https://codeberg.org/sugarbug/Rocksolid-Light-Logos

Here are the new commits with 6 designs and 10 colors:

triangle:
https://codeberg.org/sugarbug/Rocksolid-Light-Logos/commit/0d9d28e3535289c58b9cb8384b6ca42a586a0cab

hashtag.circle:
https://codeberg.org/sugarbug/Rocksolid-Light-Logos/commit/6958e958b920255d22f877fe33364c6356241bea

diamond:
https://codeberg.org/sugarbug/Rocksolid-Light-Logos/commit/626bc35dcc186b056e65e37d938c5d77b89d923b

chevron.right:
https://codeberg.org/sugarbug/Rocksolid-Light-Logos/commit/4cc9d5228f4c24fee6d019c001454c3aee2de3c7

chevron.down:
https://codeberg.org/sugarbug/Rocksolid-Light-Logos/commit/98bb80be307a0d7a395dfe3223f226e88372016c

checker:
https://codeberg.org/sugarbug/Rocksolid-Light-Logos/commit/65bd9fa5d9e79d3d318492f942cfb7e1cb42a8c7

--
3883@sugar.bug | sybershock.com | alt.sources.crypto