-
Notifications
You must be signed in to change notification settings - Fork 20
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
When using more the one account all interactions are redirected to main account (ignore logged-in instances instead) #92
Comments
While I wrote this the behaviour seems to have changed. Now, instead of giving back an error, the post is opened with my main account registered with the plugin. This is close to what the plugin is supposed to do, of course, still it makes it unusable for me, as I have to deal with accounts for other institution at the same time. |
Getting the same issue, clicking on any interact button on the site of -reply, boost, fav, bookmark and ...- from an instance I'm registred on but that isn't the one registred in the extension settings opens the toot in the "primary" instance. |
Yeah this is an rather unfortunate issue of the fact that the addon works "too good" and obviously redirects all instances. |
Perhaps a quick fix could be an option to allow an ingore list to be added to the plugin? This way it would not need to automatically detect if you are logged it, but would simply filter out some domains. |
I guess that would be as hard as implementing automatic detection. |
Same issue here. |
Bug description
I have one account registered with the add on but also use another account on another server. When the add-on is activated, tryting to reply to a post, to boost it or favour leads to an error. When I de-activate the plugin, all works fine. Somebody else noted similar problems and these were resolved when she deactivated the plugin.
Steps to reproduce
Actual behavior
leads to error
Expected behavior
do what the buttons are supposed to to
System
Operating system and version:
Browser and version: 107.0.1
Add-on version: 2.0
The text was updated successfully, but these errors were encountered: