Papers › Survival analysis for user disengagement prediction: question-and-answering communities' case
Survival analysis for user disengagement prediction: question-and-answering communities' case
Hassan Abedi Firouzjaei
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
We used survival analysis to model user disengagement in three distinct questions-and-answering communities in this work. We used the complete historical data of {Politics, Data Science, Computer Science} Stack Exchange communities from their inception until May 2021, which include the information about all users who were members of one of these three communities. Furthermore, formulating the user disengagement prediction as a survival analysis task, we utilised two survival analysis techniques to model and predict the probabilities of members of each community becoming disengaged. Our main finding is that the likelihood of users with even a few contributions staying active is noticeably higher than the users who were making no contributions; this distinction may widen as time passes. Moreover, the results of our experiments indicate that users with more favourable views towards the content shared on the platform may stay engaged longer. Finally, the observed pattern holds for all three communities, regardless of their themes.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections