Add UserAgent information to activities about activity HOT 6 CLOSED

This will cause a lot of work, but if someone implements this I'd say why not.

The main question is on which level it should be handled. Should it be part of the event (so explicitly stored by the activity app) or part of the content (apps could already do that now)

from activity.

Hmm im not clear what the two Options mean for me as a Enduser. But as the Enduser i think that every change on a Calendar Event, specially a Delete of Single Event, a change or Delete in Event Series Exception and the Mass deletion of Events or the whole calendar should be traceable with the Information of the UserAgent.

Lets assume the following Situation: You have the NextCloud Server on your HomeServer. This HomeServer is reachable by a DynDNS Address. You use this DynDNS Address also on all your Clients in your Homenetwork. In Your Homenetwork you have 3 PC's using this Calendar and 5 Smartphones or Tablets. All of them use the DynDNS Address. From Server View, all have the same IP Address, but since they use different Apps, every App has it's own UserAgent. If now App XYZ freaks out and deletes some Events, you can see which App has done this crazy thing via the Activitys App or the Server Logfiles. So far my thoughts about this. I don't know if this is already possible, i haven't found something which i could use in the Logs. If you know a better or easier way accept the Activity App, please let me know.

from activity.

Well the server's log file should already be able tell you that. It looks the request and the ip+user agent. But yeah that's more for server admins not for real end-users.

from activity.

Well the server's log file should already be able tell you that. It looks the request and the ip+user agent. But yeah that's more for server admins not for real end-users.

I am interested in the feature, for the public sharing use case, as mentioned also in #9923.
I think in that case it is useful for (advanced) end-users, not only admins.

from activity.

We can not save the IP address due to the european data protection law: GDPR

from activity.

We can not save the IP address due to the european data protection law: GDPR

IP address is indeed a personal data, thus to be handled through GDPR.

But GDPR does not say you cannot save personal data.
As any other personal data, it means you need to either propose this as optional to the end user (opt out by default), or explicitly write it is saved and explain why this is mandatory for the use of the service.
In the case of a public link sharing, I think this personal data can be seen as a required field for security purpose (avoid non solicited download for instance).

from activity.