This project is looking for maintainers!

[Bouke]

This project is run by community efforts coordinated through Jazzband. I've you'd like to help out, register yourself on the Jazzband website and come help out!

[WhyNotHugo]

I'd be happy to help with some basic maintenance here -- not specifically new features, but mostly making sure things build on a current Django version and pushing out releases.

[DmytroLitvinov]

I guess it would be nice to have 2 maintainers like @WhyNotHugo and me to help maintain that project :)

[blag]

I've been doing a fair bit of work on this and I'm already in Jazzband. Happy to assist maintaining it if you're still looking for help. It's not the first or only thing I maintain.

[WhyNotHugo]

https://github.com/QueraTeam/django-qsessions is actively maintained and works as a drop-in replacement.

[WhyNotHugo]

After some initial experimentation, I ended up not using this project.

Right now it does two things:

• It ships a Django model which can be the target of ForeignKey fields and which can be used as regular django sessions.
• It keeps track of details for those sessions, including IP addresses and a few other details of users.

The second feature turned out to be a problem. Storing sensitive user PII (which realistically we don't need) requires explicit user consent. Adding a consent dialogue or modifying the privacy policy to cover data which we don't need isn't a path that I wanted to take, and eventually the feature branch migrating to this library was never fully deployed.

I considered it viable to modify django-user-sessions and make this second feature optional, but honestly never got around to implementing that. There's already a lot of complexity here, and this would add even more.

I won't be contributing further to this project; I simply don't have the time or energy for it. Best of luck to other involved.

[mbeijen]

I guess it strongly depends on your use case. Most apps also store other data of a user, such as their name and email address, so they would need the user consent anyway. And also storing their IP address so the user can see that they have a session open where they are logged in from Connecticut or whatever is useful.

Thanks for your support on the project; I guess either we should put a release out of this package or it should be archived and point to django-qsessions as its replacement. Currently the last release of this package made in 2022 by @WhyNotHugo but a new release now of the main branch should already get some nice fixes in the users hands!