[bug] Can't find @[email protected] to follow

[mbirth]

Describe the bug with a clear and concise description of what the bug is.

As per the Bridgy Fed documentation, to bridge a Mastodon account into BlueSky, you're supposed to follow @[email protected].

However, when searching for that user using Ice Cubes and my GtS setup, the search indicator doesn't stop spinning and thus doesn't return the account so I can follow it. Using Mona, the search stops after a second with "No Users Found".

What's your GoToSocial Version?

GoToSocial 0.15.0+git-15733cd

GoToSocial Arch

arm64 Docker

What happened?

When searching for @[email protected], depending on the client, the search never finishes or finishes without any result.

What you expected to happen?

It should find the user @[email protected] and allow me to follow it.

How to reproduce it?

Search for @[email protected] first, notice how there's a proper result. Then try searching for @[email protected].

Anything else we need to know?

This is tracked at Bridgy here: snarfed/bridgy-fed#1033 and seems to be related to #1820 and/or #2082.

[tsmethurst]

Indeed looks like it's related to that URL constraint, we'll fix that when time permits.

[Tamschi]

@mbirth We recently implemented a workaround for this issue in Bridgy Fed: snarfed/bridgy-fed#1445
Instances that couldn't resolve @[email protected] before should be able to do so now.

It would be great if you could try again and let us know of any issues you encounter.

---

Instances that can't resolve @[email protected], which is also causing the initial follow of the other account to fail, will have to refresh the @[email protected] account to update its url property before they can use the bridge.
(I'm not sure we have the data to send that out as Update proactively to affected instances.)

If there's a pending follow-request already, just cancel it and retry once both accounts can be found.