- Issue created by @kreynen
- 🇧🇪Belgium swentel
More info can be added in ActivityPubUtility::alterNodeInfo
Question is of course: how do we define MAU: unique users who have posted something? That could work for me.
While we're at it: maybe we should change the name of the software and the version too (but not the Drupal version, I don't want to expose any Drupal version which might be vulnerable).
- 🇺🇸United States mradcliffe USA
In my implementation, I am using status = 1, uid > 0, and access comparisons so I can get a quick query.
For activitypub module, I think that joining to the actor table by uid makes sense. I don't think it should include the non-person actors in "users".
Aside, the Drupal activitypub module listing is probably going to disappear again. aleixq's changes got removed in https://github.com/fedidb/communityDB/commit/ce23a1bd1956f0c2788d4755869...
- 🇺🇸United States kreynen
> MAU: unique users who have posted something?
That makes sense to me. When I initial saw the level of federated activity and MAU from WP instances, I was really impressed... but as I dug into the data I realized they were just dumping everything that had been in the site's RSS feed into ActivityPub. WP users not only had no idea they were now discoverable, they had no way to interact with their ActivityPub Inbox within the WP instance.
WP's implementation is FINO (Federation in Name Only).
If I was trying to provide accurate MUA counts in WP or Drupal, I would only count the authors of the posts in the nodeinfo. It would make sense include the author of comments if those were actually federated, but I can't find any instances doing that. So if a Drupal instance has published 10 nodes in the last month, the maximum MUA would be 10.