kaiyou

Now that 1.7 is branch, I move this to p1 and believe we should fix it by the next release.

We have, and probably have an already opened issue on the matter, but it is a completely different topic :)

We are observing and investigating similar behavior across multiple Nextcloud instances ran by distinct teams. Here are some details : - we noticed the issue *after* upgrading to 23, although...

After investigating a bit more, and still relating to https://github.com/nextcloud/activity/issues/784, we were able to confirme that at least 90% of the issue is due to logs or activitiy generated by...

Quick update: the issue is actually not fixed with Nextcloud 23, but upgrading to 23 broke cron jobs on our instance; re-enabling crons triggered the issue again. On the bright...

Just as a follow-up from https://github.com/nextcloud/activity/issues/784, the issue there is being fixed by avoiding the misattributed activity from being generated in the first place. This still does not fix this...

It is not currently on the menu, you should open a separate issue for this. I will close this one since the original issue is fixed.

My bad, the original issue is not fixed. But still you should open a separate issue for external DAV service.

Thank you for your feedback and idea. Adding a recovery email address would both bring an interesting feature and solve the problem of migrating at the same time. Nice to...

That would be a neat feature indeed. Should have this per domain or per user maybe?