Add option to silence curl errors

[tuxArg]

IMPORTANT

Read and tick the following checkbox after you have created the issue or place an x inside the brackets ;)

• I have read the CONTRIBUTING.md and followed the provided tips
• I accept that the issue will be closed without comment if I do not check here
• I accept that the issue will be closed without comment if I do not fill out all items in the issue template.

Explain the Problem

What problem did you encounter?

I'm getting a lot of warnings/errors server side hen some of the feeds is unreachable like:

{
  "reqId": "*REDACTED*",
  "level": 2,
  "time": "2025-09-03T00:05:09+00:00",
  "remoteAddr": "",
  "user": "--",
  "app": "news",
  "method": "",
  "url": "--",
  "message": "*REDACTED* read error : cURL error 28: Operation timed out after 60001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for *REDACTED*",
  "userAgent": "--",
  "version": "31.0.8.1",
  "data": {
    "app": "news"
  }
}
{
  "reqId": "*REDACTED*",
  "level": 2,
  "time": "2025-09-03T00:05:09+00:00",
  "remoteAddr": "",
  "user": "--",
  "app": "news",
  "method": "",
  "url": "--",
  "message": "Error while parsing feed: *REDACTED* {\"class\":\"FeedIo\\Reader\\ReadErrorException\",\"message\":\"cURL error 28: Operation timed out after 60001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for *REDACTED*\",\"code\":0,\"file\":\"/var/www/nextcloud/apps/news/vendor/php-feed-io/feed-io/src/FeedIo/Reader.php:82\"
  ...
  "userAgent": "--",
  "version": "31.0.8.1",
  "data": {
    "app": "news"
  }
}

This happens for each feed (for each user who subscribed to it?), every time it tries to update (default 60 minutes). That's a lot of logging.

Please add some way to ignore them (or lower them to info level) or to just log as a warning the first time it failed (i.e., record if it failed last time, and don't log consecutive attempts)

System Information

• News app version: 26.1.0
• Nextcloud version: 31.0.8.1
• Cron type: crontab
• PHP version: 8.3
• Database and version: mariadb
• Browser and version:
• OS and version: ubuntu 22.04

[SMillerDev]

I don't think they should be a different level. They are real problems the program is running into. That there's a lot of users on your instance that have unreachable feeds doesn't sound like something that should be solved in the app.

[tuxArg]

That there's a lot of users on your instance that have unreachable feeds doesn't sound like something that should be solved in the app.

I agree. The issue is not about solving bad typed urls or unreachable feeds. It's about logging all that server side. I don't think a user should be able to cause warnings in the logs, that should only be reserved when something went wrong and should be solved. As this isn't something the server admin can solve, there shouldn't be a warning at all (in server logs).