User reading over OPDS does not show as active.

[DieselTech]

What happened?

I just saw it in the logs while looking at the last issue that a user on my system is actively reading through OPDS. When I looked at their user account in the admin settings it shows them last active as 5 days ago and they are not listed as "Online". This is misleading and could lead to admins closing down accounts if they think users aren't logging into them. We should have a way to tell if a user is actively fetching pages and consuming server resources.

What did you expect?

The user to be listed as online.

Kavita Version Number - If you don't see your version number listed, please update Kavita and see if your issue still persists.

0.8.5.11 - Stable

What operating system is Kavita being hosted from?

Docker (Dockerhub Container)

If the issue is being seen on Desktop, what OS are you running where you see the issue?

None

If the issue is being seen in the UI, what browsers are you seeing the problem on?

Firefox

If the issue is being seen on Mobile, what OS are you running where you see the issue?

None

If the issue is being seen on the Mobile UI, what browsers are you seeing the problem on?

No response

Relevant log output

Additional Notes

Maybe even a "dumb" timeout. Like if the user requested a page over OPDS recently keep them listed as online for the next 10 minutes. Each page pull could just refresh that time over and over so we are aware someone is there.

[majora2007]

I wouldn't call this a bug, this is a feature request. The Online status is for when people are online and using the web app, not when they are consuming content via opds or the api.

While I'm not against the enhancement, let's transfer this over to a Feature Request instead. I want to keep the Issue section clear of enhancement work (unless in flight) to help me plan bugfixing releases.

[DieselTech]

We can move it to a FR, it is just that isn't the impression the users table in the admin section gives us. It specifically states "Last Active". It doesn't say "Last logged into the web UI". To me this is more a matter of how your wording it in the app. I don't think any reasonable person would see the word "Last Active" and think it only applied only to the web UI when their users could be reading every day using a protocol that the server provides (OPDS).

In my case here I was ready to delete the user for inactivity because I thought he wasn't logging in for long stretches of time. He happened to reach out to me and said he get a new ipad and needed to login again to get the OPDS URL. He was reading constantly, he just doesn't touch the website once OPDS is setup.

[majora2007]

I'm not invalidating your use case, but I do not agree with you. As I asked, a Feature Request will expand upon this feature to expand it's scope more inline with how people are consuming data from Kavita and you are understanding the label.

Expansion has to be carefully done because what you are expecting out of the system is that when users are reading via OPDS/Panels/etc that last active is updated. When Last Active originally was just Last Login and at some point the wording was cleaned up and thus the misunderstanding occurred.

You should be able to convert from the issue and then perform some cleanup on it. Thanks.