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

Multiple instances #54

Closed
coolacid opened this issue Apr 4, 2017 · 12 comments
Closed

Multiple instances #54

coolacid opened this issue Apr 4, 2017 · 12 comments
Assignees
Milestone

Comments

@coolacid
Copy link

coolacid commented Apr 4, 2017

Would be nice to have the ability to have multiple instances running, this will probably be a thing sooner rather than later.

@alex73630
Copy link

A multiple account option like the Twitter mobile app would be awesome !

@Vavassor
Copy link
Collaborator

Vavassor commented Apr 7, 2017

This is definitely planned! A lot of folks have been asking for it on Mastodon itself, and a lot of folks have been getting more accounts with the recent proliferation of instances.

@steve31266
Copy link

Related request: ability to browse the details of other instances, perhaps by clicking on someone's profile, or by entering an instance address, or scrolling through a list of instances.

@zet4
Copy link

zet4 commented Sep 11, 2017

It's been few months since this issue was made, has there been any progress?

@connyduck
Copy link
Collaborator

There has not been any progress, but multi account support is one of my personal priorities for Tusky.

@connyduck connyduck added this to the Tusky 1.5.0 milestone Nov 6, 2017
@connyduck
Copy link
Collaborator

Lets prioritize this since I am getting so many requests for multiple account support.

@connyduck connyduck self-assigned this Nov 13, 2017
@connyduck connyduck modified the milestones: Tusky 1.5.0, Tusky 1.4.0 Nov 13, 2017
@charlag
Copy link
Collaborator

charlag commented Nov 13, 2017

Okay, so we need to separate SharedPreferences?
I think we should inject them somehow instead of just requesting them everywhere. Then we can provide screens with the ones they need.
I'm not sure if we should separate drafts between accounts.
Also notifications will need some work.
I think we may have separate preferences (like Settings) for each account, it shouldn't be too bad.

@connyduck
Copy link
Collaborator

I would switch from SharedPreferences to a database table that stores logins. There can always only be one active login. You only get notifications for that one active login. (we can improve that later)

@wakingrufus
Copy link

Nice to have: when retooting, prompt for which account to retoot from

@charlag
Copy link
Collaborator

charlag commented Nov 13, 2017

It would be harder but it would be more correct.
I don't see a problem with fetching notifications for multiple accounts.
I've checked and it seems that preferences are not used too much so migration to DB wouldn't be too painful.
I would make a CurrentUser class which has methods to fetch cached current info.

@charlag
Copy link
Collaborator

charlag commented Nov 13, 2017

@wakingrufus it is a good idea but it would be a little hard to do so it probably should be done later.

@connyduck
Copy link
Collaborator

finally done :) #490

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants