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

Non whitelisted Twitter accounts can still be resolved #143

Open
todoneunl opened this issue Mar 23, 2022 · 1 comment
Open

Non whitelisted Twitter accounts can still be resolved #143

todoneunl opened this issue Mar 23, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@todoneunl
Copy link

I don't know if I described the title correctly, but this happens:

  • I only have a few Twitter accounts whitelisted on my instance.
  • When I search for another Twitter account (not whitelisted) on my BirdsiteLive instance, it finds the account and offers me to follow it on my Mastodon account.
  • I can follow it on my Mastodon account, but when I refresh the page it's actually not followed. Actually it tries to send a follow request, but it isn't accepted (as it should).
  • When I search for this account on my Mastodon server, it shows up.
  • When I look as admin in the accounts section it is indeed there.

This is confusing for people on my Mastodon server, because they think they can follow that account, but actually they can't. It would be better if this non whitelisted account is not resolved after all when searching for it on the BirdsiteLive instance.

@NicolasConstant NicolasConstant added the enhancement New feature or request label Mar 26, 2022
@NicolasConstant
Copy link
Owner

If we disable the resolution of other accounts it will makes all mentions not usable anymore that's why it's enabled even with whitelisting.
But I could add some settings to disable this if the admin wants it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants