[communityhome] Remove active users feature #539
No reviewers
Labels
No labels
2018.09
2019.01
2019.03
2019.06
2019.09
2019.12
2020.03
2020.06
2020.09
2020.12
2021.03
2021.07
2021.09
2022.02
2022.06
2022.09
2022.12
2023.04
2023.05
2023.09
2024.03
2024.06
2024.09
2024.12
2025.02
2025.05
dependencies
Hackathon 2021
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: friendica/friendica-addons#539
Loading…
Reference in a new issue
No description provided.
Delete branch "bug/4555-remove-active-users-feature"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes https://github.com/friendica/friendica/issues/4555
Most of the queries in this addon are extremely intense. I suggest rebuilding that addon so that it only shows the community page, not more.
Sure, but not for the 3.6 release though.
I'm unsure. Problem is that the two queries with the likes and the photos are so intense, that they kill every server that is a little bit larger. So it only works on small servers with few users. But there this addon doesn't make sense.
We can retire the addon altogether as well.
Possibly this would be the best. But we should not only set the special comment in the header, but also we should disable the functionality as well.
So we keep this PR and I just add the deprecated header?
I would prefer adding some
return
to the beginning of the functions. This can be done in this PR.I don't see the point, if node admins want to try the addon, they can, and if it's too slow, they can deactivate it. I removed a feature whose query was triggering an error, but the rest is fine, even if it's slow.
I see the problem that people try it when their server is small enough for it. But it will be slower and slower. And since many regular users won't see the front page, they won't recognize the loss of speed.
I also guess that (possibly due to changed indexes?) the queries in that addon will massively slow down the system.
When - eventually - I will do the new stuff with the item table, I will massively remove functionality in that addon anyway :-)
But since it's now unsupported, most node admins won't be able to enable it anyway.
Okay, let's see what will happen.