Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature request: Multiple User accounts #122

Open
3 tasks done
9thyear2 opened this issue Sep 9, 2024 · 4 comments
Open
3 tasks done

feature request: Multiple User accounts #122

9thyear2 opened this issue Sep 9, 2024 · 4 comments
Labels
feature request New feature or request not planned This feature is not planned and will not be worked on workaround available

Comments

@9thyear2
Copy link

9thyear2 commented Sep 9, 2024

Checklist

  • I checked that this feature has not been requested before
  • I checked that this feature is not in the "Not planned" list
  • This feature will benefit the majority of users

Problem Description / Use Case

people in the same household having there own anilist account, and can be signed in at once. so what your watching and their watching doesn't get meshed together.

i am also aware that this could take a while to implement, simply due to not knowing what all will break in the process of implementing.

Proposed Solution

  1. when a new device is connecting to the server, it is promoted with the sign in page. then the sign in is remembered per device, rather than network wide

  2. also ability to allow and restrict torrenting per user (so a given user can't just start torrenting wildly and eating all the storage (hypothetical, personally i like managing which torrents are gotten manually, so everyone would be restricted))

@9thyear2 9thyear2 added the feature request New feature or request label Sep 9, 2024
@5rahim
Copy link
Owner

5rahim commented Sep 10, 2024

Thanks for the request but this isn't the scope of the project. Reason is it would require a major rewrite because Seanime wasn't built for multi-user support. One workaround is to run other instances on different ports and point them to the same library, only one instance would need to manage the library.

@5rahim 5rahim added the not planned This feature is not planned and will not be worked on label Sep 10, 2024
@9thyear2
Copy link
Author

i was aware that this would be a complex thing to add, and not easy to implement. but thought i should still leave it here

@5rahim
Copy link
Owner

5rahim commented Sep 10, 2024

Yeah np, I'll leave this open so people can see the workaround.

@dillfrescott
Copy link

Would love to see this but I know it would require a lot of code changes. Thank you for suggesting the workaround!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request not planned This feature is not planned and will not be worked on workaround available
Projects
None yet
Development

No branches or pull requests

3 participants