[Bug]: All tagging by app Recognize is logged as 'activity by others'

[rekcodocker]

⚠️ This issue respects the following points: ⚠️

• [X] This is a bug, not a question or a configuration/webserver/proxy issue.
• [X] This issue is not already reported on Github (I've searched it).
• [X] Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• [X] Nextcloud Server is running on 64bit capable CPU, PHP and OS.
• [X] I agree to follow Nextcloud's Code of Conduct.

Bug description

The app 'recognize' automatically tags images with face- and object recognition. However, adding tags is logged under 'activity' as 'activity by others'.

I use this to keep an eye on file downloads. I don't see tagging by an internal Nextcloud app as activity by other people.

Steps to reproduce

1. Install Nextcloud 25 (I use Nextcloud AIO)
2. Install the app 'recognize'
3. In dashboard click on 'activity', then on 'others'

Expected behavior

I expect the tagging-activity of 'recognize' to show up in another log or not at all.

Installation method

Official All-in-One appliance

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.0

Web server

Apache (supported)

Database engine version

PostgreSQL

Is this bug present after an update or on a fresh install?

Updated to a major version (ex. 22.2.3 to 23.0.1)

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• [X] Default user-backend (database)
• [ ] LDAP/ Active Directory
• [ ] SSO - SAML
• [ ] Other

Configuration report

... i really don't think it's relevant, it is probably programmed behaviour not dependend on the configuration...

List of activated Apps

Recognize

Nextcloud Signing status

No errors have been found.

Nextcloud Logs

arning  activity    Failed sending activity email to user 'sanan'.      2023-01-02T21:01:30+0100
Error   activity    Swift_TransportException: Connection could not be established with host 127.0.0.1 :stream_socket_client(): Unable to connect to 127.0.0.1:25 (Connection refused)       2023-01-02T21:01:30+0100
Warning activity    Failed sending activity email to user 'gerben'.     2023-01-02T21:01:30+0100
Error   activity    Swift_TransportException: Connection could not be established with host 127.0.0.1 :stream_socket_client(): Unable to connect to 127.0.0.1:25 (Connection refused)       2023-01-02T21:01:30+0100
Warning activity    Failed sending activity email to user 'sanan'.      2023-01-02T20:56:28+0100
Error   activity    Swift_TransportException: Connection could not be established with host 127.0.0.1 :stream_socket_client(): Unable to connect to 127.0.0.1:25 (Connection refused)       2023-01-02T20:56:28+0100
Warning activity    Failed sending activity email to user 'gerben'.     2023-01-02T20:56:28+0100
Error   activity    Swift_TransportException: Connection could not be established with host 127.0.0.1 :stream_socket_client(): Unable to connect to 127.0.0.1:25 (Connection refused)

Additional info

nope

[marcelklehr]

Mmh, not sure if there is something I can do about that. As far as I'm aware, recognize doesn't set a user session for tagging, so there is no user associated with the tagging event. I understand the predicament in your situation. If we can do something about this, it would be in the activity app, I believe. Can you open an issue there?